new datacenter ping test

[Punk_FAS]

2 less hops for me for "67.228.53.218", and about the same ping as "tastyspleen.net" via tracert

[soh]

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

I was just on right now with [BTF]IOU. My ping was 48 ms. On the regular servers I am on 43 ms. If you want, I cant still do the tracert on the command line ???

[Sgt. Dick]

Thanks for the help Derv and Vae.

I was on earlier, the ping was a little higher but the connection was good.

[QuakeDuke]

Appears to be about the same for me.... I can't play worth a hoot on either one    Maybe one day when I grow up  I'll learn how to use a mouse....

QD

[VaeVictis]

Appears to be about the same for me.... I can't play worth a hoot on either one    Maybe one day when I grow up  I'll learn how to use a mouse....

QD

you still play keyboard only? xD nice... lol

only way to learn is to use it nice tip for using a mouse to aim, lower your sensitivity is the less accurate you have to be with your actual physical movements, just keep it high enough that your arm wont get tired and you can still flick for a 180 turn

[[BTF] Reflex]

....young whipper snapper.


QuakeDuke predates mice.

Come to think about it,  I do too 

[QwazyWabbit]

From Los Angeles area.

Pinging 67.228.53.218 with 32 bytes of data:
Reply from 67.228.53.218: bytes=32 time=47ms TTL=251
Reply from 67.228.53.218: bytes=32 time=50ms TTL=251
Reply from 67.228.53.218: bytes=32 time=48ms TTL=251
Reply from 67.228.53.218: bytes=32 time=46ms TTL=251
Reply from 67.228.53.218: bytes=32 time=47ms TTL=251
Reply from 67.228.53.218: bytes=32 time=49ms TTL=251
Reply from 67.228.53.218: bytes=32 time=50ms TTL=251
Reply from 67.228.53.218: bytes=32 time=48ms TTL=251
Reply from 67.228.53.218: bytes=32 time=46ms TTL=251
Reply from 67.228.53.218: bytes=32 time=49ms TTL=251
Reply from 67.228.53.218: bytes=32 time=49ms TTL=251
Reply from 67.228.53.218: bytes=32 time=47ms TTL=251
Reply from 67.228.53.218: bytes=32 time=46ms TTL=251
Reply from 67.228.53.218: bytes=32 time=47ms TTL=251
Reply from 67.228.53.218: bytes=32 time=45ms TTL=251
Reply from 67.228.53.218: bytes=32 time=50ms TTL=251
Reply from 67.228.53.218: bytes=32 time=51ms TTL=251
Reply from 67.228.53.218: bytes=32 time=47ms TTL=251
Reply from 67.228.53.218: bytes=32 time=47ms TTL=251
Reply from 67.228.53.218: bytes=32 time=50ms TTL=251
Reply from 67.228.53.218: bytes=32 time=48ms TTL=251
Reply from 67.228.53.218: bytes=32 time=46ms TTL=251

Ping statistics for 67.228.53.218:
    Packets: Sent = 22, Received = 22, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 45ms, Maximum = 51ms, Average = 47ms


Pinging 74.54.186.226 with 32 bytes of data:
Reply from 74.54.186.226: bytes=32 time=44ms TTL=251
Reply from 74.54.186.226: bytes=32 time=45ms TTL=251
Reply from 74.54.186.226: bytes=32 time=43ms TTL=251
Reply from 74.54.186.226: bytes=32 time=45ms TTL=251
Reply from 74.54.186.226: bytes=32 time=45ms TTL=251
Reply from 74.54.186.226: bytes=32 time=46ms TTL=251
Reply from 74.54.186.226: bytes=32 time=44ms TTL=251
Reply from 74.54.186.226: bytes=32 time=45ms TTL=251
Reply from 74.54.186.226: bytes=32 time=45ms TTL=251
Reply from 74.54.186.226: bytes=32 time=43ms TTL=251
Reply from 74.54.186.226: bytes=32 time=44ms TTL=251
Reply from 74.54.186.226: bytes=32 time=44ms TTL=251
Reply from 74.54.186.226: bytes=32 time=45ms TTL=251
Reply from 74.54.186.226: bytes=32 time=44ms TTL=251
Reply from 74.54.186.226: bytes=32 time=45ms TTL=251
Reply from 74.54.186.226: bytes=32 time=43ms TTL=251
Reply from 74.54.186.226: bytes=32 time=43ms TTL=251
Reply from 74.54.186.226: bytes=32 time=44ms TTL=251
Reply from 74.54.186.226: bytes=32 time=43ms TTL=251
Reply from 74.54.186.226: bytes=32 time=44ms TTL=251
Reply from 74.54.186.226: bytes=32 time=44ms TTL=251
Reply from 74.54.186.226: bytes=32 time=44ms TTL=251
Reply from 74.54.186.226: bytes=32 time=43ms TTL=251
Reply from 74.54.186.226: bytes=32 time=45ms TTL=251
Reply from 74.54.186.226: bytes=32 time=44ms TTL=251
Reply from 74.54.186.226: bytes=32 time=43ms TTL=251

Ping statistics for 74.54.186.226:
    Packets: Sent = 26, Received = 26, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 43ms, Maximum = 46ms, Average = 44ms

Tracing route to 67.228.53.218-static.reverse.softlayer.com [67.228.53.218]
over a maximum of 30 hops:

  1     1 ms     1 ms    <1 ms  192.168.1.1
  2     4 ms     4 ms     4 ms  10.35.107.146
  3     7 ms     7 ms     7 ms  G11-0-7-1748.LSANCA-LCR-07.verizon-gni.net [130.81.140.118]
  4     6 ms     7 ms     7 ms  so-5-1-0-0.LAX01-BB-RTR1.verizon-gni.net [130.81.29.140]
  5    10 ms     9 ms     9 ms  0.so-6-3-0.XT1.LAX9.ALTER.NET [152.63.10.153]
  6    48 ms    46 ms    46 ms  0.ge-4-0-0.XL3.DFW7.ALTER.NET [152.63.103.53]
  7    46 ms    46 ms    81 ms  TenGigE0-6-4-0.GW4.DFW13.ALTER.NET [152.63.101.21]
  8    46 ms    46 ms    47 ms  internapGIGE1-gw.customer.alter.net [65.208.15.230]
  9    49 ms    49 ms    49 ms  border3.tge3-1-bbnet1.ext1.dal.pnap.net [216.52.191.22]
 10    46 ms    46 ms    46 ms  te1-2.cer01.sr01.dal01.networklayer.com [216.52.189.30]
 11    48 ms    49 ms    49 ms  po1.fcr03.sr04.dal01.networklayer.com [66.228.118.186]
 12    46 ms    46 ms    49 ms  67.228.53.218-static.reverse.softlayer.com [67.228.53.218]

Trace complete.

Tracing route to tastyspleen.net [74.54.186.226]
over a maximum of 30 hops:

  1     1 ms     1 ms     1 ms  192.168.1.1
  2     3 ms     4 ms     4 ms  10.35.107.146
  3     7 ms     6 ms     6 ms  G11-0-7-1748.LSANCA-LCR-07.verizon-gni.net [130.81.140.118]
  4     8 ms     7 ms     6 ms  so-5-1-0-0.LAX01-BB-RTR1.verizon-gni.net [130.81.29.140]
  5     7 ms     7 ms     6 ms  0.so-6-3-0.XL3.LAX15.ALTER.NET [152.63.113.241]
  6     6 ms     6 ms     7 ms  0.xe-10-0-0.BR1.LAX15.ALTER.NET [152.63.115.90]
  7    10 ms     9 ms     9 ms  4.68.62.169
  8    20 ms    17 ms    17 ms  ae-82-80.ebr2.LosAngeles1.Level3.net [4.69.144.179]
  9    43 ms    49 ms    54 ms  ae-3-3.ebr3.Dallas1.Level3.net [4.69.132.78]
 10    45 ms    44 ms   129 ms  ae-1-60.edge4.Dallas3.Level3.net [4.69.145.13]
 11    44 ms    46 ms    44 ms  THE-PLANET.edge4.Dallas3.Level3.net [4.59.32.30]
 12    47 ms    44 ms    44 ms  te9-2.dsr02.dllstx3.networklayer.com [70.87.253.30]
 13    47 ms    44 ms    46 ms  te2-4.dsr02.dllstx2.networklayer.com [70.87.255.126]
 14    56 ms    43 ms    44 ms  te1-2.car06.dllstx6.networklayer.com [70.87.254.182]
 15    43 ms    44 ms    44 ms  tastyspleen.net [74.54.186.226]

Trace complete.

If you could arrange to put the new server on the alternet backbone...

[astral]

Here are my results:

New IP tracert

Code: [Select]

C:\Documents and Settings\astral>tracert 67.228.53.218

Tracing route to 67.228.53.218-static.reverse.softlayer.com [67.228.53.218]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2     4 ms     3 ms     3 ms  cpe-70-112-20-156.austin.res.rr.com [70.112.20.1
56]
  3     *        *        *     Request timed out.
  4    11 ms    13 ms    12 ms  te1-5.austtxg-rtr2.austin.rr.com [66.68.1.181]
  5    14 ms    13 ms    14 ms  Gi0-2-2-4.austtxrdcsc-rtr2.austin.rr.com [24.27.
12.146]
  6    18 ms    16 ms    21 ms  gig5-3-0.dllatxl3-rtr1.texas.rr.com [72.179.205.
20]
  7    19 ms    17 ms    17 ms  ae-4-0.cr0.dfw10.tbone.rr.com [66.109.6.88]
  8    24 ms    18 ms    18 ms  66.109.6.209
  9    19 ms    19 ms    17 ms  po21.bbr02.eq01.dal01.networklayer.com [66.109.9
.222]
 10    23 ms    20 ms    18 ms  po6.dar01.sr01.dal01.networklayer.com [173.192.1
8.211]
 11    26 ms    24 ms    17 ms  po1.fcr03.sr04.dal01.networklayer.com [66.228.11
8.186]
 12    21 ms    20 ms    21 ms  67.228.53.218-static.reverse.softlayer.com [67.2
28.53.218]

Trace complete.
New IP Ping

Code: [Select]

C:\Documents and Settings\astral>ping 67.228.53.218

Pinging 67.228.53.218 with 32 bytes of data:

Reply from 67.228.53.218: bytes=32 time=21ms TTL=53
Reply from 67.228.53.218: bytes=32 time=20ms TTL=53
Reply from 67.228.53.218: bytes=32 time=21ms TTL=53
Reply from 67.228.53.218: bytes=32 time=21ms TTL=53

Ping statistics for 67.228.53.218:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 20ms, Maximum = 21ms, Average = 20ms
Old IP tracert

Code: [Select]

C:\Documents and Settings\astral>tracert tastyspleen.net

Tracing route to tastyspleen.net [74.54.186.226]
over a maximum of 30 hops:

  1     7 ms     1 ms    <1 ms  192.168.1.1
  2     3 ms     6 ms     6 ms  cpe-70-112-20-156.austin.res.rr.com [70.112.20.1
56]
  3     *        *        *     Request timed out.
  4    25 ms    12 ms    11 ms  te1-5.austtxg-rtr2.austin.rr.com [66.68.1.181]
  5    17 ms    15 ms    17 ms  Gi0-2-2-7.austtxrdcsc-rtr2.austin.rr.com [24.27.
13.201]
  6    18 ms    19 ms    17 ms  gig5-3-0.dllatxl3-rtr1.texas.rr.com [72.179.205.
20]
  7    20 ms    19 ms    20 ms  ae-4-0.cr0.dfw10.tbone.rr.com [66.109.6.88]
  8    20 ms    19 ms    20 ms  ae-1-0.pr0.dfw10.tbone.rr.com [66.109.6.179]
  9    19 ms    19 ms    20 ms  66.109.11.22
 10    28 ms    23 ms    19 ms  xe-0-0-0.er1.dfw2.us.above.net [64.125.26.205]
 11    20 ms    19 ms    19 ms  64.125.199.94.t366.above.net [64.125.199.94]
 12    20 ms    20 ms    21 ms  te7-1.dsr02.dllstx3.networklayer.com [70.87.253.
18]
 13     *        *        *     Request timed out.
 14    25 ms    19 ms    21 ms  te1-2.car06.dllstx6.networklayer.com [70.87.254.
182]
 15    21 ms    22 ms    21 ms  tastyspleen.net [74.54.186.226]

Trace complete.

Old IP Ping

Code: [Select]

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

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

Reply from 74.54.186.226: bytes=32 time=22ms TTL=50
Reply from 74.54.186.226: bytes=32 time=26ms TTL=50
Reply from 74.54.186.226: bytes=32 time=22ms TTL=50
Reply from 74.54.186.226: bytes=32 time=22ms TTL=50

Ping statistics for 74.54.186.226:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 22ms, Maximum = 26ms, Average = 23ms
Not much change on my end a few less hops.

[SquiSHeR]

my ping got worse 2 ms

PING 74.54.186.226 (74.54.186.226): 56 data bytes
64 bytes from 74.54.186.226: icmp_seq=0 ttl=46 time=132.299 ms
64 bytes from 74.54.186.226: icmp_seq=1 ttl=46 time=132.324 ms
64 bytes from 74.54.186.226: icmp_seq=2 ttl=46 time=132.204 ms
64 bytes from 74.54.186.226: icmp_seq=3 ttl=46 time=132.124 ms
64 bytes from 74.54.186.226: icmp_seq=4 ttl=46 time=132.255 ms
64 bytes from 74.54.186.226: icmp_seq=5 ttl=46 time=132.369 ms
^C
--- 74.54.186.226 ping statistics ---
6 packets transmitted, 6 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 132.124/132.263/132.369/0.081 ms

PING 67.228.53.218 (67.228.53.218): 56 data bytes
64 bytes from 67.228.53.218: icmp_seq=0 ttl=49 time=134.240 ms
64 bytes from 67.228.53.218: icmp_seq=1 ttl=49 time=134.337 ms
64 bytes from 67.228.53.218: icmp_seq=2 ttl=49 time=134.464 ms
64 bytes from 67.228.53.218: icmp_seq=3 ttl=49 time=134.598 ms
64 bytes from 67.228.53.218: icmp_seq=4 ttl=50 time=135.948 ms
64 bytes from 67.228.53.218: icmp_seq=5 ttl=49 time=134.157 ms
^C
--- 67.228.53.218 ping statistics ---
6 packets transmitted, 6 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 134.157/134.624/135.948/0.609 ms

[Krlll Mule]

Appears to be about the same for me.... I can't play worth a hoot on either one    Maybe one day when I grow up  I'll learn how to use a mouse....

QD

Wow, I thought I was the only one.  Nice to see you around again Duke.   

[QuakeDuke]

Appears to be about the same for me.... I can't play worth a hoot on either one    Maybe one day when I grow up  I'll learn how to use a mouse....

QD

Wow, I thought I was the only one.  Nice to see you around again Duke.   

Same to you Mule. Maybe you can frag me on the servers sometime

 

QD

[Cheaters-r-Scum]

Happy New Year to everybody!

A bit late for this thread, but anyway, I would like to report a ping worsening :-(


(1) old servers:

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=46 time=132 ms
64 bytes from tastyspleen.net (74.54.186.226): icmp_req=2 ttl=46 time=133 ms
64 bytes from tastyspleen.net (74.54.186.226): icmp_req=3 ttl=46 time=133 ms
64 bytes from tastyspleen.net (74.54.186.226): icmp_req=4 ttl=46 time=132 ms
64 bytes from tastyspleen.net (74.54.186.226): icmp_req=5 ttl=46 time=132 ms
64 bytes from tastyspleen.net (74.54.186.226): icmp_req=6 ttl=46 time=132 ms
64 bytes from tastyspleen.net (74.54.186.226): icmp_req=7 ttl=46 time=132 ms
64 bytes from tastyspleen.net (74.54.186.226): icmp_req=8 ttl=46 time=132 ms
64 bytes from tastyspleen.net (74.54.186.226): icmp_req=9 ttl=46 time=132 ms
^C
--- tastyspleen.net ping statistics ---
9 packets transmitted, 9 received, 0% packet loss, time 8010ms
rtt min/avg/max/mdev = 132.046/132.616/133.575/0.504 ms


 3  145.254.0.237  9.199 ms  9.414 ms  9.181 ms
 4  92.79.213.122  12.466 ms  9.838 ms  9.716 ms
 5  xe-1-2-0.mpr1.fra4.de.above.net (80.81.194.26)  10.708 ms  11.593 ms  11.235 ms
 6  xe-1-1-0.mpr1.cdg12.fr.above.net (64.125.24.6)  20.968 ms  20.079 ms  20.026 ms
 7  xe-4-0-0.mpr1.lhr3.uk.above.net (64.125.31.249)  27.521 ms  26.748 ms  27.485 ms
 8  so-0-0-0.mpr1.lhr2.uk.above.net (64.125.27.225)  28.607 ms  28.276 ms  28.438 ms
 9  so-1-1-0.mpr1.dca2.us.above.net (64.125.31.186)  100.835 ms  110.036 ms  101.189 ms
10  xe-0-3-0.cr1.dca2.us.above.net (64.125.29.17)  100.017 ms  100.479 ms  102.295 ms
11  xe-0-2-0.cr1.iah1.us.above.net (64.125.25.114)  131.856 ms  127.602 ms  127.362 ms
12  xe-2-1-0.cr1.dfw2.us.above.net (64.125.30.58)  131.870 ms  132.213 ms  131.644 ms
13  xe-1-1-0.er1.dfw2.us.above.net (64.125.26.210)  132.109 ms  131.188 ms  131.424 ms
14  64.125.199.94.t366.above.net (64.125.199.94)  131.573 ms  131.383 ms  131.349 ms
15  te7-1.dsr01.dllstx3.networklayer.com (70.87.253.2)  314.935 ms  132.653 ms  133.225 ms
16  * * *
17  * * *
18  tastyspleen.net (74.54.186.226) [open]  132.339 ms  133.130 ms  133.174 ms




(2) new servers

PING tastyspleen.net (67.228.69.114) 56(84) bytes of data.
64 bytes from tastyspleen.net (67.228.69.114): icmp_req=1 ttl=56 time=148 ms
64 bytes from tastyspleen.net (67.228.69.114): icmp_req=2 ttl=56 time=148 ms
64 bytes from tastyspleen.net (67.228.69.114): icmp_req=3 ttl=56 time=148 ms
64 bytes from tastyspleen.net (67.228.69.114): icmp_req=4 ttl=56 time=148 ms
64 bytes from tastyspleen.net (67.228.69.114): icmp_req=5 ttl=56 time=148 ms
64 bytes from tastyspleen.net (67.228.69.114): icmp_req=6 ttl=56 time=147 ms
64 bytes from tastyspleen.net (67.228.69.114): icmp_req=7 ttl=56 time=148 ms
64 bytes from tastyspleen.net (67.228.69.114): icmp_req=8 ttl=56 time=148 ms
64 bytes from tastyspleen.net (67.228.69.114): icmp_req=9 ttl=56 time=148 ms
64 bytes from tastyspleen.net (67.228.69.114): icmp_req=10 ttl=56 time=148 ms

--- tastyspleen.net ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9002ms
rtt min/avg/max/mdev = 147.782/148.306/148.913/0.540 ms


 3  145.254.0.237  9.831 ms  9.005 ms  9.029 ms
 4  ash-145-254-13-142.arcor-ip.net (145.254.13.142)  121.913 ms  120.862 ms  121.121 ms
 5  * te3-5.bbr01.eq01.wdc01.networklayer.com (206.223.115.185) 113.101 ms  113.052 ms
 6  po3.bbr02.tl01.atl01.networklayer.com (173.192.18.153)  128.039 ms  128.126 ms  128.250 ms
 7  po7.bbr02.eq01.dal01.networklayer.com (173.192.18.134)  148.236 ms  148.568 ms  148.980 ms
 8  po5.dar02.sr01.dal01.networklayer.com (173.192.18.203)  149.354 ms  149.317 ms  149.214 ms
 9  po2.fcr03.sr04.dal01.networklayer.com (66.228.118.190)  145.519 ms  145.752 ms  145.825 ms
10  tastyspleen.net (67.228.69.114) [open]  147.406 ms  148.642 ms  148.998 ms

During the day, the new ping even rises to values beyond 155 ms. So yes, it is a deterioration, sadly... But of course, I don't complain, considering that we all get a great service for free.


Regards, CRS

[yahoo]

i dont mind my ping that grew from 260 to 300+. I can still manage to frag by strategy. What i noticed is that there seem to be more lag spikes in my part. Anyway im still game.

[no_life]

I noticed some of the lag at first too. My ping is exactly what it was before - but there seemed to be increased choppiness/dry fires. Seems to happen the most on the rails server. It always was a little laggy the more players that were on it - but now it seems like it does it with even less players. Always thought it was something to do with that specific mod since in dm/vanilla there can be 16+ players and it runs perfectly smooth.
Just on rail it seems to lag considerably more as the amount of players increases. Was going to make a thread about it when I first tried the new IPs but figured it would be better to wait and play there some more to see what it was like overall. Hasn't really been that bad overall. Just specific times the lag will make it almost unplayable. An hour later it can be back to running smooth. Shrug.

[VaeVictis]

i was freezing quite a bit on rails last night as well :/ those HUGE spikes on the netgraph where you get the phone jack and just freeze midair...