Dat Ping

[Sahji]

[11:33] <Utu> Current Players: 2 of 40 Maximum | Ping: 657 ms

[Peregrinus]

I've been noticing this all week. This is also not just between Utu and the server. I ran a ping test of 100 packets from my location:

Code: Select all

Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.

C:\>ping -t 173.74.165.247

Pinging 173.74.165.247 with 32 bytes of data:
Reply from 173.74.165.247: bytes=32 time=755ms TTL=49
Reply from 173.74.165.247: bytes=32 time=893ms TTL=49
Reply from 173.74.165.247: bytes=32 time=999ms TTL=49
Reply from 173.74.165.247: bytes=32 time=687ms TTL=49
Reply from 173.74.165.247: bytes=32 time=807ms TTL=49
Reply from 173.74.165.247: bytes=32 time=859ms TTL=49
Reply from 173.74.165.247: bytes=32 time=1013ms TTL=49
Reply from 173.74.165.247: bytes=32 time=932ms TTL=49
Reply from 173.74.165.247: bytes=32 time=919ms TTL=49
Reply from 173.74.165.247: bytes=32 time=976ms TTL=49
Reply from 173.74.165.247: bytes=32 time=594ms TTL=49
Reply from 173.74.165.247: bytes=32 time=1064ms TTL=49
Reply from 173.74.165.247: bytes=32 time=1007ms TTL=49
Reply from 173.74.165.247: bytes=32 time=830ms TTL=49
Reply from 173.74.165.247: bytes=32 time=1055ms TTL=49
Reply from 173.74.165.247: bytes=32 time=623ms TTL=49
Reply from 173.74.165.247: bytes=32 time=460ms TTL=49
Reply from 173.74.165.247: bytes=32 time=627ms TTL=49
Reply from 173.74.165.247: bytes=32 time=554ms TTL=49
Reply from 173.74.165.247: bytes=32 time=539ms TTL=49
Reply from 173.74.165.247: bytes=32 time=662ms TTL=49
Reply from 173.74.165.247: bytes=32 time=692ms TTL=49
Reply from 173.74.165.247: bytes=32 time=392ms TTL=49
Reply from 173.74.165.247: bytes=32 time=418ms TTL=49
Reply from 173.74.165.247: bytes=32 time=403ms TTL=49
Reply from 173.74.165.247: bytes=32 time=486ms TTL=49
Reply from 173.74.165.247: bytes=32 time=495ms TTL=49
Reply from 173.74.165.247: bytes=32 time=494ms TTL=49
Reply from 173.74.165.247: bytes=32 time=543ms TTL=49
Reply from 173.74.165.247: bytes=32 time=397ms TTL=49
Reply from 173.74.165.247: bytes=32 time=440ms TTL=49
Reply from 173.74.165.247: bytes=32 time=492ms TTL=49
Reply from 173.74.165.247: bytes=32 time=592ms TTL=49
Reply from 173.74.165.247: bytes=32 time=494ms TTL=49
Reply from 173.74.165.247: bytes=32 time=501ms TTL=49
Reply from 173.74.165.247: bytes=32 time=591ms TTL=49
Reply from 173.74.165.247: bytes=32 time=556ms TTL=49
Reply from 173.74.165.247: bytes=32 time=581ms TTL=49
Reply from 173.74.165.247: bytes=32 time=590ms TTL=49
Reply from 173.74.165.247: bytes=32 time=564ms TTL=49
Reply from 173.74.165.247: bytes=32 time=469ms TTL=49
Reply from 173.74.165.247: bytes=32 time=350ms TTL=49
Reply from 173.74.165.247: bytes=32 time=345ms TTL=49
Reply from 173.74.165.247: bytes=32 time=388ms TTL=49
Reply from 173.74.165.247: bytes=32 time=430ms TTL=49
Reply from 173.74.165.247: bytes=32 time=441ms TTL=49
Reply from 173.74.165.247: bytes=32 time=470ms TTL=49
Reply from 173.74.165.247: bytes=32 time=406ms TTL=49
Reply from 173.74.165.247: bytes=32 time=489ms TTL=49
Reply from 173.74.165.247: bytes=32 time=485ms TTL=49
Reply from 173.74.165.247: bytes=32 time=477ms TTL=49
Reply from 173.74.165.247: bytes=32 time=529ms TTL=49
Reply from 173.74.165.247: bytes=32 time=553ms TTL=49
Reply from 173.74.165.247: bytes=32 time=570ms TTL=49
Reply from 173.74.165.247: bytes=32 time=531ms TTL=49
Reply from 173.74.165.247: bytes=32 time=537ms TTL=49
Reply from 173.74.165.247: bytes=32 time=489ms TTL=49
Reply from 173.74.165.247: bytes=32 time=435ms TTL=49
Reply from 173.74.165.247: bytes=32 time=439ms TTL=49
Reply from 173.74.165.247: bytes=32 time=490ms TTL=49
Reply from 173.74.165.247: bytes=32 time=592ms TTL=49
Reply from 173.74.165.247: bytes=32 time=604ms TTL=49
Reply from 173.74.165.247: bytes=32 time=494ms TTL=49
Reply from 173.74.165.247: bytes=32 time=593ms TTL=49
Reply from 173.74.165.247: bytes=32 time=626ms TTL=49
Reply from 173.74.165.247: bytes=32 time=465ms TTL=49
Reply from 173.74.165.247: bytes=32 time=481ms TTL=49
Reply from 173.74.165.247: bytes=32 time=556ms TTL=49
Reply from 173.74.165.247: bytes=32 time=550ms TTL=49
Reply from 173.74.165.247: bytes=32 time=527ms TTL=49
Reply from 173.74.165.247: bytes=32 time=576ms TTL=49
Reply from 173.74.165.247: bytes=32 time=632ms TTL=49
Reply from 173.74.165.247: bytes=32 time=517ms TTL=49
Reply from 173.74.165.247: bytes=32 time=504ms TTL=49
Reply from 173.74.165.247: bytes=32 time=559ms TTL=49
Reply from 173.74.165.247: bytes=32 time=647ms TTL=49
Reply from 173.74.165.247: bytes=32 time=610ms TTL=49
Reply from 173.74.165.247: bytes=32 time=605ms TTL=49
Reply from 173.74.165.247: bytes=32 time=543ms TTL=49
Reply from 173.74.165.247: bytes=32 time=632ms TTL=49
Reply from 173.74.165.247: bytes=32 time=682ms TTL=49
Reply from 173.74.165.247: bytes=32 time=651ms TTL=49
Reply from 173.74.165.247: bytes=32 time=523ms TTL=49
Reply from 173.74.165.247: bytes=32 time=563ms TTL=49
Reply from 173.74.165.247: bytes=32 time=730ms TTL=49
Reply from 173.74.165.247: bytes=32 time=137ms TTL=49
Reply from 173.74.165.247: bytes=32 time=485ms TTL=49
Reply from 173.74.165.247: bytes=32 time=526ms TTL=49
Reply from 173.74.165.247: bytes=32 time=539ms TTL=49
Reply from 173.74.165.247: bytes=32 time=423ms TTL=49
Reply from 173.74.165.247: bytes=32 time=689ms TTL=49
Reply from 173.74.165.247: bytes=32 time=615ms TTL=49
Reply from 173.74.165.247: bytes=32 time=619ms TTL=49
Reply from 173.74.165.247: bytes=32 time=724ms TTL=49
Reply from 173.74.165.247: bytes=32 time=859ms TTL=49
Reply from 173.74.165.247: bytes=32 time=688ms TTL=49
Reply from 173.74.165.247: bytes=32 time=734ms TTL=49
Reply from 173.74.165.247: bytes=32 time=659ms TTL=49
Reply from 173.74.165.247: bytes=32 time=775ms TTL=49
Reply from 173.74.165.247: bytes=32 time=868ms TTL=49
Reply from 173.74.165.247: bytes=32 time=763ms TTL=49
Reply from 173.74.165.247: bytes=32 time=603ms TTL=49
Reply from 173.74.165.247: bytes=32 time=759ms TTL=49
Reply from 173.74.165.247: bytes=32 time=802ms TTL=49
Reply from 173.74.165.247: bytes=32 time=912ms TTL=49
Reply from 173.74.165.247: bytes=32 time=669ms TTL=49

Ping statistics for 173.74.165.247:
    Packets: Sent = 106, Received = 106, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 137ms, Maximum = 1064ms, Average = 605ms
Control-C
^C
C:\>

Average ping for 100 packets was 605ms, to give some idea from my experience, that's 6 times the ping I would have expected while working as the NOC to see between Virginia and Japan. That said, there's no dropped packets, which is a good thing, but also makes it harder to figure out. My guess is something is throttling the speed of the server at its location. Given that it's not dropping packets, it's likely not due to a circuit being overloaded. More likely it is something like a Firewall or WAN Accelerator slowing things down in the response time.

EDIT:

Further details from a tracert:

Code: Select all

Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.

C:\>tracert 173.74.165.247

Tracing route to pool-173-74-165-247.dllstx.fios.verizon.net [173.74.165.247]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2     1 ms     1 ms    <1 ms  172.16.12.1
  3    36 ms    21 ms    39 ms  c-76-111-80-1.hsd1.va.comcast.net [76.111.80.1]
  4    10 ms     9 ms    30 ms  xe-2-0-0-32767-sur01.lakeridge.va.bad.comcast.net [68.85.147.193]
  5    19 ms    11 ms    14 ms  xe-6-0-2-0-ar04.capitolhghts.md.bad.comcast.net[68.85.114.65]
  6    12 ms    16 ms    14 ms  he-5-3-0-0-10-cr01.ashburn.va.ibone.comcast.net[68.86.93.141]
  7    13 ms    15 ms    12 ms  he-0-12-0-1-pe07.ashburn.va.ibone.comcast.net [68.86.83.86]
  8    19 ms    12 ms    13 ms  n-a.GW12.IAD8.ALTER.NET [152.179.50.205]
  9    63 ms    55 ms    55 ms  T0-6-0-10.DLLSTX-LCR-22.verizon-gni.net [130.81.162.161]
 10     *        *        *     Request timed out.
 11   760 ms   757 ms   902 ms  pool-173-74-165-247.dllstx.fios.verizon.net [173.74.165.247]

Trace complete.

C:\>

This seems to confirm my theory that it's something within the server's LAN. Between hops 1 and 9 I'm seeing typical response times. Hop 10 times out (this is normal for a boundary) and then the server itself gives a response time of 757 ms. As indicated, from my computer up to the server's network, I'm getting normal ping times, it's not until we get inside the server's network that was see the high ping times begin.

[Wired]

Is this still a thing?

I'm getting 50-60ms.

[Peregrinus]

It seems to have cleared up sometime yesterday, but, as you can see from the graph Sahji linked, these high pings have been reoccurring with some frequency. It's something to keep an eye on and if it happens again I'll try and post information.