new datacenter ping test

[console]

Howdy,

tastyspleen.net may be getting a hardware upgrade, but this also means its IP would change.

It will still be in Dallas, TX - just a different datacenter.

Here's a sample IP from that datacenter: 67.228.53.218  (was: 66.228.118.51)

If everyone could please run pings and traceroutes to this IP, and also pings and traceroutes to the current tastyspleen.net, and if you're seeing anything significantly worse on the new IP, please post here.

UPDATE: There's a Q2 server now running on 67.228.53.218:27910 for ping testing - please try it out.

Thanks for your help!

quadz

[[BTF]Jehar]

Code: [Select]

PING tastyspleen.net (74.54.186.226) 56(84) bytes of data.
64 bytes from tastyspleen.net (74.54.186.226): icmp_req=1 ttl=49 time=62.5 ms
64 bytes from tastyspleen.net (74.54.186.226): icmp_req=2 ttl=49 time=61.4 ms
64 bytes from tastyspleen.net (74.54.186.226): icmp_req=3 ttl=49 time=65.4 ms
64 bytes from tastyspleen.net (74.54.186.226): icmp_req=4 ttl=49 time=60.9 ms
64 bytes from tastyspleen.net (74.54.186.226): icmp_req=5 ttl=49 time=61.6 ms
64 bytes from tastyspleen.net (74.54.186.226): icmp_req=6 ttl=49 time=62.2 ms
^C^C
--- tastyspleen.net ping statistics ---
6 packets transmitted, 6 received, 0% packet loss, time 5004ms
rtt min/avg/max/mdev = 60.949/62.392/65.431/1.493 ms



Code: [Select]

jehar@fragbox:~/.quake2$ ping 66.228.118.51
PING 66.228.118.51 (66.228.118.51) 56(84) bytes of data.
64 bytes from 66.228.118.51: icmp_req=1 ttl=242 time=77.1 ms
64 bytes from 66.228.118.51: icmp_req=2 ttl=242 time=75.3 ms
64 bytes from 66.228.118.51: icmp_req=3 ttl=242 time=76.0 ms
64 bytes from 66.228.118.51: icmp_req=4 ttl=242 time=79.5 ms
64 bytes from 66.228.118.51: icmp_req=5 ttl=242 time=75.4 ms
64 bytes from 66.228.118.51: icmp_req=6 ttl=242 time=76.2 ms
^C
--- 66.228.118.51 ping statistics ---
6 packets transmitted, 6 received, 0% packet loss, time 5006ms
rtt min/avg/max/mdev = 75.336/76.624/79.532/1.453 ms
Looks like an avg 12ms increase.

[console]

Looks like an avg 12ms increase.

G*d damn it, always something.   (In my case, I get a better route with the new IP.)


For curiosity's sake, could you post the traceroutes?


Thanks,

quadz

[Zeppelin]

A enviar para tastyspleen.net [74.54.186.226] com 32 bytes de dados:

Resposta de 74.54.186.226: bytes=32 tempo=186ms TTL=48
Resposta de 74.54.186.226: bytes=32 tempo=172ms TTL=48
Resposta de 74.54.186.226: bytes=32 tempo=188ms TTL=48
Resposta de 74.54.186.226: bytes=32 tempo=184ms TTL=48


Estat¡sticas de ping para 74.54.186.226:
    Pacotes: Enviados = 4, Recebidos = 4, Perdidos = 0 (perda: 0%),
Tempo aproximado de ida e volta em milissegundos:
    M¡nimo = 172ms, M ximo = 188ms, M‚dia = 182ms

-------------------------------------------------------------

A enviar para 66.228.118.51 com 32 bytes de dados:


Resposta de 66.228.118.51: bytes=32 tempo=168ms TTL=239
Resposta de 66.228.118.51: bytes=32 tempo=193ms TTL=239
Resposta de 66.228.118.51: bytes=32 tempo=180ms TTL=239
Resposta de 66.228.118.51: bytes=32 tempo=182ms TTL=239


Estat¡sticas de ping para 66.228.118.51:
    Pacotes: Enviados = 4, Recebidos = 4, Perdidos = 0 (perda: 0%),
Tempo aproximado de ida e volta em milissegundos:
    M¡nimo = 168ms, Maximo = 193ms, M‚dia = 180ms


seems better here, but i rarely ping 170, as it says.
my ping is normally 155, 160

[haunted]

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Administrator>ping tastyspleen.net

Pinging tastyspleen.net [74.54.186.226] with 32 bytes of data:

Reply from 74.54.186.226: bytes=32 time=77ms TTL=52
Reply from 74.54.186.226: bytes=32 time=76ms TTL=52
Reply from 74.54.186.226: bytes=32 time=78ms TTL=52
Reply from 74.54.186.226: bytes=32 time=77ms TTL=52

Ping statistics for 74.54.186.226:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 76ms, Maximum = 78ms, Average = 77ms

C:\Documents and Settings\Administrator>ping 66.228.118.51

Pinging 66.228.118.51 with 32 bytes of data:

Reply from 66.228.118.51: bytes=32 time=74ms TTL=243
Reply from 66.228.118.51: bytes=32 time=73ms TTL=243
Reply from 66.228.118.51: bytes=32 time=70ms TTL=243
Reply from 66.228.118.51: bytes=32 time=73ms TTL=243

Ping statistics for 66.228.118.51:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 70ms, Maximum = 74ms, Average = 72ms



Mine wen't down 5ms... even if it were to go up 20ms I was going to say switch it if it will be more cost-efficient!

[RailWolf]

Code: [Select]

C:\Users\RailWolf>ping -n 25 66.228.118.51

Pinging 66.228.118.51 with 32 bytes of data:
Reply from 66.228.118.51: bytes=32 time=44ms TTL=236
Reply from 66.228.118.51: bytes=32 time=38ms TTL=236
Reply from 66.228.118.51: bytes=32 time=79ms TTL=236
Reply from 66.228.118.51: bytes=32 time=35ms TTL=236
Reply from 66.228.118.51: bytes=32 time=113ms TTL=236
Reply from 66.228.118.51: bytes=32 time=38ms TTL=236
Reply from 66.228.118.51: bytes=32 time=37ms TTL=236
Reply from 66.228.118.51: bytes=32 time=37ms TTL=236
Reply from 66.228.118.51: bytes=32 time=38ms TTL=236
Reply from 66.228.118.51: bytes=32 time=43ms TTL=236
Reply from 66.228.118.51: bytes=32 time=38ms TTL=236
Reply from 66.228.118.51: bytes=32 time=128ms TTL=236
Reply from 66.228.118.51: bytes=32 time=37ms TTL=236
Reply from 66.228.118.51: bytes=32 time=38ms TTL=236
Reply from 66.228.118.51: bytes=32 time=156ms TTL=236
Reply from 66.228.118.51: bytes=32 time=46ms TTL=236
Reply from 66.228.118.51: bytes=32 time=63ms TTL=236
Reply from 66.228.118.51: bytes=32 time=74ms TTL=236
Reply from 66.228.118.51: bytes=32 time=38ms TTL=236
Reply from 66.228.118.51: bytes=32 time=37ms TTL=236
Reply from 66.228.118.51: bytes=32 time=36ms TTL=236
Reply from 66.228.118.51: bytes=32 time=101ms TTL=236
Reply from 66.228.118.51: bytes=32 time=49ms TTL=236
Reply from 66.228.118.51: bytes=32 time=78ms TTL=236
Reply from 66.228.118.51: bytes=32 time=64ms TTL=236

Ping statistics for 66.228.118.51:
    Packets: Sent = 25, Received = 25, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 35ms, Maximum = 156ms, Average = 59ms


C:\Users\RailWolf>ping -n 25 ts

Pinging ts [74.54.186.226] with 32 bytes of data:
Reply from 74.54.186.226: bytes=32 time=35ms TTL=46
Reply from 74.54.186.226: bytes=32 time=36ms TTL=46
Reply from 74.54.186.226: bytes=32 time=36ms TTL=46
Reply from 74.54.186.226: bytes=32 time=75ms TTL=46
Reply from 74.54.186.226: bytes=32 time=70ms TTL=46
Reply from 74.54.186.226: bytes=32 time=94ms TTL=46
Reply from 74.54.186.226: bytes=32 time=74ms TTL=46
Reply from 74.54.186.226: bytes=32 time=75ms TTL=46
Reply from 74.54.186.226: bytes=32 time=36ms TTL=46
Reply from 74.54.186.226: bytes=32 time=71ms TTL=46
Reply from 74.54.186.226: bytes=32 time=70ms TTL=46
Reply from 74.54.186.226: bytes=32 time=39ms TTL=46
Reply from 74.54.186.226: bytes=32 time=41ms TTL=46
Reply from 74.54.186.226: bytes=32 time=50ms TTL=46
Reply from 74.54.186.226: bytes=32 time=37ms TTL=46
Reply from 74.54.186.226: bytes=32 time=36ms TTL=46
Reply from 74.54.186.226: bytes=32 time=36ms TTL=46
Reply from 74.54.186.226: bytes=32 time=37ms TTL=46
Reply from 74.54.186.226: bytes=32 time=69ms TTL=46
Reply from 74.54.186.226: bytes=32 time=49ms TTL=46
Reply from 74.54.186.226: bytes=32 time=35ms TTL=46
Reply from 74.54.186.226: bytes=32 time=38ms TTL=46
Reply from 74.54.186.226: bytes=32 time=63ms TTL=46
Reply from 74.54.186.226: bytes=32 time=89ms TTL=46
Reply from 74.54.186.226: bytes=32 time=83ms TTL=46

Ping statistics for 74.54.186.226:
    Packets: Sent = 25, Received = 25, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 35ms, Maximum = 94ms, Average = 54ms


[console]

I was going to say switch it if it will be more cost-efficient!

Yes, it would be a significantly faster CPU, and bigger hard drives -- for less money.

* console prays to the ping gods

[Whirlingdervish]

Code: [Select]

1,   64.60.*.*, 4ms, 64-60-*-*.static-ip.telepacific.net,----
2,   208.57.150.81, 4ms, lax-static-208.57.150.81.mpowercom.net,----
3,   198.172.90.33, 5ms, xe-2-2.r00.lsanca03.us.bb.gin.ntt.net,----
4,   129.250.5.249, 7ms, ae-1.r21.lsanca03.us.bb.gin.ntt.net,----
5,   129.250.3.33, 6ms, ae-0.r20.lsanca03.us.bb.gin.ntt.net,----
6,   129.250.2.169, 55ms, ae-4.r20.dllstx09.us.bb.gin.ntt.net,----
7,   129.250.3.26, 38ms, ae-1.r07.dllstx09.us.bb.gin.ntt.net,----
8,   157.238.224.226, 37ms, ae2.bbr01.eq01.dal03.networklayer.com,----
9,   173.192.18.211, 38ms, po6.dar01.sr01.dal01.networklayer.com,----
10, 66.228.118.138, 36ms, po1.slr01.sr01.dal01.networklayer.com,----
11, 66.228.118.51, 37ms, www.softlayer.com,----



seems to be about 5-7ms faster for me from the LA area

[[BTF]adam]

Bad news for britain!

Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Users\Adam>ping 66.228.118.51

Pinging 66.228.118.51 with 32 bytes of data:
Reply from 66.228.118.51: bytes=32 time=148ms TTL=238
Reply from 66.228.118.51: bytes=32 time=146ms TTL=238
Reply from 66.228.118.51: bytes=32 time=145ms TTL=238
Reply from 66.228.118.51: bytes=32 time=147ms TTL=238

Ping statistics for 66.228.118.51:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 145ms, Maximum = 148ms, Average = 146ms

C:\Users\Adam>

[console]

Bad news for britain!

How does that compare to the current IP?

[[BTF]adam]

until last time I played (my net was on the skitch tho), I was getting 125's consistently

[Tailgunner]

These are my results

Pings:
New

Code: [Select]

debian01:~# ping -c 6 -s 64 66.228.118.51
PING 66.228.118.51 (66.228.118.51) 64(92) bytes of data.
72 bytes from 66.228.118.51: icmp_req=1 ttl=237 time=166 ms
72 bytes from 66.228.118.51: icmp_req=2 ttl=237 time=165 ms
72 bytes from 66.228.118.51: icmp_req=3 ttl=237 time=165 ms
72 bytes from 66.228.118.51: icmp_req=4 ttl=237 time=166 ms
72 bytes from 66.228.118.51: icmp_req=5 ttl=237 time=164 ms
72 bytes from 66.228.118.51: icmp_req=6 ttl=237 time=164 ms

--- 66.228.118.51 ping statistics ---
6 packets transmitted, 6 received, 0% packet loss, time 5020ms
rtt min/avg/max/mdev = 164.235/165.186/166.141/0.699 ms

Old:

Code: [Select]

debian01:~# ping -c 6 -s 64 74.54.186.226
PING 74.54.186.226 (74.54.186.226) 64(92) bytes of data.
72 bytes from 74.54.186.226: icmp_req=1 ttl=56 time=155 ms
72 bytes from 74.54.186.226: icmp_req=2 ttl=56 time=154 ms
72 bytes from 74.54.186.226: icmp_req=3 ttl=56 time=155 ms
72 bytes from 74.54.186.226: icmp_req=4 ttl=56 time=155 ms
72 bytes from 74.54.186.226: icmp_req=5 ttl=56 time=155 ms
72 bytes from 74.54.186.226: icmp_req=6 ttl=56 time=154 ms

--- 74.54.186.226 ping statistics ---
6 packets transmitted, 6 received, 0% packet loss, time 5019ms
rtt min/avg/max/mdev = 154.382/155.266/155.831/0.731 ms

Traceroute:
New:

Code: [Select]

debian01:~# traceroute  -I 66.228.118.51
traceroute to 66.228.118.51 (66.228.118.51), 30 hops max, 60 byte packets
 1  ip-39-105.sn1.eutelia.it (62.94.39.105)  12.120 ms  12.616 ms  13.240 ms
 2  ip-42-1.sn1.eutelia.it (62.94.42.1)  77.967 ms  78.902 ms  79.429 ms
 3  ip-1-6.sn-212-90.eutelia.it (212.90.1.6)  50.382 ms  52.604 ms  56.665 ms
 4  if-0-0-0.core1.RCT-Rome.as6453.net (195.219.163.9)  58.348 ms  58.420 ms  60.021 ms
 5  if-8-2-1-0.tcore1.PYE-Paris.as6453.net (80.231.154.41)  165.283 ms  160.097 ms  160.889 ms
 6  if-10-0-0.core1.PYE-Paris.as6453.net (80.231.154.38)  144.287 ms  125.114 ms  127.157 ms
 7  if-9-0-0-1815.mcore5.NYY-NewYork.as6453.net (64.86.71.53)  224.654 ms  201.641 ms  199.996 ms
 8  if-1-0.core2.NTO-NewYork.as6453.net (216.6.97.41)  142.222 ms  141.318 ms  142.155 ms
 9  Vlan475.icore1.NTO-NewYork.as6453.net (216.6.97.90)  147.479 ms * *
10  Vlan546.icore1.NTO-NewYork.as6453.net (209.58.26.58)  137.196 ms  143.574 ms  144.580 ms
11  pos-0-15-0-0-cr01.newyork.ny.ibone.comcast.net (68.86.87.169)  118.727 ms  119.742 ms  119.799 ms
12  pos-0-10-0-0-cr01.ashburn.va.ibone.comcast.net (68.86.85.9)  131.953 ms  132.164 ms  135.162 ms
13  pos-1-2-0-0-cr01.atlanta.ga.ibone.comcast.net (68.86.87.66)  140.321 ms  138.520 ms  137.745 ms
14  pos-1-14-0-0-cr01.dallas.tx.ibone.comcast.net (68.86.85.153)  158.776 ms  159.946 ms  158.482 ms
15  pos-0-2-0-0-pe01.1950stemmons.tx.ibone.comcast.net (68.86.86.150)  177.404 ms  182.843 ms  183.733 ms
16  softlayer-cr01.dallas.tx.ibone.comcast.net (75.149.228.34)  165.193 ms  164.281 ms  163.008 ms
17  po6.dar01.sr01.dal01.networklayer.com (173.192.18.211)  341.358 ms  338.731 ms  331.998 ms
18  po1.slr01.sr01.dal01.networklayer.com (66.228.118.138)  165.673 ms  164.474 ms  165.466 ms
19  www.softlayer.com (66.228.118.51)  165.978 ms  164.305 ms  163.699 ms

Old:

Code: [Select]

debian01:~# traceroute  -I 74.54.186.226
traceroute to 74.54.186.226 (74.54.186.226), 30 hops max, 60 byte packets
 1  ip-39-105.sn1.eutelia.it (62.94.39.105)  2.821 ms  12.644 ms  13.289 ms
 2  ip-42-1.sn1.eutelia.it (62.94.42.1)  84.627 ms  85.200 ms  86.926 ms
 3  ip-1-6.sn-212-90.eutelia.it (212.90.1.6)  44.429 ms  46.104 ms  52.359 ms
 4  gi9-5.ccr01.rom01.atlas.cogentco.com (149.6.22.49)  77.236 ms  78.068 ms  80.443 ms
 5  te1-4.ccr01.goa01.atlas.cogentco.com (130.117.3.233)  55.647 ms  59.792 ms  61.425 ms
 6  te3-1.ccr01.mil01.atlas.cogentco.com (130.117.48.6)  66.077 ms * *
 7  te2-2.ccr01.str01.atlas.cogentco.com (130.117.3.17)  56.051 ms  53.502 ms  53.625 ms
 8  te0-0-0-2.ccr22.fra03.atlas.cogentco.com (130.117.49.129)  52.230 ms  48.879 ms  45.674 ms
 9  te3-2.mpd01.fra03.atlas.cogentco.com (130.117.51.110)  72.415 ms  68.560 ms  62.158 ms
10  abovenet.fra03.atlas.cogentco.com (130.117.15.106)  47.121 ms  50.286 ms  52.167 ms
11  xe-1-1-0.mpr1.cdg12.fr.above.net (64.125.24.6)  54.868 ms  55.306 ms  53.490 ms
12  xe-4-0-0.mpr1.lhr3.uk.above.net (64.125.31.249)  62.255 ms  67.691 ms  70.207 ms
13  so-1-0-0.mpr1.lhr2.uk.above.net (64.125.28.38)  69.201 ms  71.411 ms  72.102 ms
14  so-1-1-0.mpr1.dca2.us.above.net (64.125.31.186)  149.626 ms  153.261 ms  156.385 ms
15  xe-1-3-0.cr1.dca2.us.above.net (64.125.29.21)  156.101 ms  159.796 ms  162.920 ms
16  xe-2-2-0.cr1.iah1.us.above.net (64.125.29.37)  186.351 ms  163.392 ms  176.510 ms
17  xe-1-2-0.cr1.dfw2.us.above.net (64.125.26.129)  176.306 ms  174.505 ms  176.000 ms
18  xe-1-1-0.er1.dfw2.us.above.net (64.125.26.210)  202.671 ms  200.503 ms  189.454 ms
19  64.125.199.94.t366.above.net (64.125.199.94)  161.762 ms  166.666 ms  167.350 ms
20  te9-1.dsr01.dllstx3.networklayer.com (70.87.253.6)  168.249 ms  166.775 ms  168.475 ms
21  * * *
22  te1-1.car06.dllstx6.networklayer.com (70.87.254.178)  160.762 ms  158.922 ms  156.207 ms
23  tastyspleen.net (74.54.186.226)  154.511 ms  155.957 ms  153.133 ms

Pings seems to be 10 ms higher, but trace is shorter (19 hops instead of 23).
Could be useful setting up a test q2 server at the new site if possible? Just to see how it is in game  (for example to see if there is packet loss, if connections are stable and so on...)
TG

[reaper]

Both 45ms letting it run for a few minutes, a few hundred ping replies, no drops on either

[R1CH]

Code: [Select]

C:\>ftrace -c tastyspleen.net

Tracing route to tastyspleen.net [74.54.186.226] with TTL of 32:

 1  0ms    0ms    0ms    192.168.88.1
 2   *      *      *     Request timed out.
 3  7ms    6ms    6ms    gig-4-2-nycmnyw-rtr1.nyc.rr.com [24.29.98.141]
 4  7ms    6ms    6ms    gig-5-0-nycmnyw-rtr1.nyc.rr.com [24.29.104.118]
 5  7ms    6ms    7ms    tenge-4-2-0-nwrknjmd-rtr1.nyc.rr.com [24.29.97.18]
 6  7ms    6ms    6ms    ae-4-0.cr0.nyc30.tbone.rr.com [66.109.6.78]
 7  7ms    6ms    7ms    ae-1-0.pr0.nyc30.tbone.rr.com [66.109.6.161]
 8  9ms    7ms    7ms    xe-9-3-0.edge2.newark1.level3.net [4.79.190.169]
 9  15ms   8ms    8ms    ae-31-51.ebr1.Newark1.Level3.net [4.68.99.30]
10  8ms    8ms    8ms    ae-2-2.ebr1.NewYork1.Level3.net [4.69.132.97]
11  19ms   10ms   23ms   ae-81-81.csw3.newyork1.level3.net [4.69.134.74]
12  9ms    10ms   9ms    ae-82-82.ebr2.newyork1.level3.net [4.69.148.41]
13  45ms   45ms   57ms   ae-3-3.ebr2.dallas1.level3.net [4.69.137.121]
14  45ms   44ms   44ms   ae-3-80.edge4.dallas3.level3.net [4.69.145.141]
15  50ms   44ms   43ms   the-planet.edge4.dallas3.level3.net [4.59.32.30]
16  45ms   45ms   45ms   te9-2.dsr02.dllstx3.networklayer.com [70.87.253.30]
17  46ms   46ms   45ms   te3-1.dsr02.dllstx2.networklayer.com [70.87.255.130]
18  45ms   45ms   45ms   te1-2.car06.dllstx6.networklayer.com [70.87.254.182]
19  45ms   45ms   43ms   tastyspleen.net [74.54.186.226]

Traceroute complete.

C:\>ftrace -c 66.228.118.51

Tracing route to www.softlayer.com [66.228.118.51] with TTL of 32:

 1  0ms    0ms    0ms    192.168.88.1
 2   *      *      *     Request timed out.
 3  7ms    6ms    6ms    gig-4-2-nycmnyw-rtr1.nyc.rr.com [24.29.98.141]
 4  6ms    6ms    7ms    pos-6-2-nycmnyrdc-rtr1.nyc.rr.com [24.29.119.29]
 5  7ms    6ms    8ms    tenge-4-2-0-nwrknjmd-rtr1.nyc.rr.com [24.29.97.18]
 6  6ms    6ms    6ms    ae-4-0.cr0.nyc30.tbone.rr.com [66.109.6.78]
 7  7ms    8ms    6ms    ae-1-0.pr0.nyc20.tbone.rr.com [66.109.6.163]
 8  7ms    7ms    7ms    66.109.11.126
 9  46ms   46ms   45ms   po3.bbr01.eq01.dal01.networklayer.com [173.192.18.136]
10  47ms   46ms   46ms   po5.dar01.sr01.dal01.networklayer.com [173.192.18.191]
11  48ms   47ms   47ms   po1.slr01.sr01.dal01.networklayer.com [66.228.118.138]
12  48ms   47ms   46ms   www.softlayer.com [66.228.118.51]

Traceroute complete.

[console]

Could be useful setting up a test q2 server at the new site if possible? Just to see how it is in game  (for example to see if there is packet loss, if connections are stable and so on...)

Agreed - but unfortunately that IP is just provided for pings to the datacenter ( https://www.softlayer.com/facilities/dallas-details/ ).

I wouldn't be able to set up a Q2 server until I've actually ordered & paid for & configured a new server.


Regards,

quadz