High Ping at Night

[smithj1]

i have posted the traceroutes on the previous page, can someone please take a look at them

[Hubrisnxs]

to be quite frank, the pings look fine to me.  Nothing over 70 if I am not mistaken, which doesn't match the ping times on your server, which leads me to believe that it couldn't be anything on the network, and instead is a problem that resides at the server.

there isn't any actionable information about your ping times.  they are not magnificent, you have a few that are a tad or a notch high, but nothing that would explain the game server ping times in my opinion. 

[spacedebris]

---

@smithj1 wrote:

OK, here is my traceroute to the game's server, my ping right now on the game is 75. I have friends who live in florida that have half my ping, but I live in the same city where the server is being hosted.

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

Tracing route to li134-24.members.linode.com [69.164.219.24]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  Wireless_Broadband_Router.home [192.168.1.1]
  2     5 ms     5 ms     4 ms  L100.NWRKNJ-VFTTP-136.verizon-gni.net [hidden]
  3     6 ms     6 ms     6 ms  G14-0-2-1336.NWRKNJ-LCR-03.verizon-gni.net [130.
81.140.230]
  4     6 ms     5 ms     5 ms  so-6-0-1-0.NWRK-BB-RTR1.verizon-gni.net [130.81.
29.192]
  5     6 ms     5 ms     6 ms  0.so-7-1-0.XL3.EWR6.ALTER.NET [152.63.17.141]
  6     8 ms     8 ms     8 ms  0.xe-6-1-0.XL3.NYC4.ALTER.NET [152.63.3.105]
  7     8 ms     6 ms     9 ms  GigabitEthernet6-0-0.GW1.NYC4.ALTER.NET [152.63.
20.49]
  8     9 ms     8 ms    11 ms  teliasonera-gw.customer.alter.net [157.130.60.14
]
  9    10 ms     9 ms    10 ms  nyk-bb1-link.telia.net [80.91.253.101]
 10     7 ms     7 ms     6 ms  nyk-b3-link.telia.net [80.91.248.174]
 11    72 ms    69 ms    70 ms  netaccess-tic-133837-nyk-b3.c.telia.net [213.248
.99.90]
 12    11 ms    10 ms    10 ms  0.e1-4.tbr1.mmu.nac.net [209.123.10.101]
 13     9 ms    10 ms     8 ms  vlan803.esd2.mmu.nac.net [209.123.10.30]
 14    74 ms    76 ms    77 ms  207.99.53.46
 15     8 ms     9 ms     8 ms  li134-24.members.linode.com [69.164.219.24]

Trace complete.

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

Here's a tracerout to dsl reports.

Tracing route to dslreports.com [209.123.109.175]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  Wireless_Broadband_Router.home [192.168.1.1]
  2     5 ms     4 ms     7 ms  L100.NWRKNJ-VFTTP-136.verizon-gni.net [hidden]
  3     6 ms     4 ms     5 ms  G14-0-2-1436.NWRKNJ-LCR-04.verizon-gni.net [130.
81.146.66]
  4     7 ms    52 ms     6 ms  so-6-1-0-0.NWRK-BB-RTR2.verizon-gni.net [130.81.
29.194]
  5     6 ms     6 ms     6 ms  0.so-7-0-0.XL4.EWR6.ALTER.NET [152.63.20.13]
  6     6 ms     7 ms     6 ms  0.so-1-0-3.XL4.NYC4.ALTER.NET [152.63.17.110]
  7     8 ms     9 ms     9 ms  GigabitEthernet5-0-0.GW1.NYC4.ALTER.NET [152.63.
20.101]
  8     9 ms     8 ms     8 ms  teliasonera-gw.customer.alter.net [157.130.60.14
]
  9     7 ms     7 ms     8 ms  nyk-bb2-link.telia.net [80.91.253.105]
 10     8 ms     8 ms     7 ms  nyk-b3-link.telia.net [80.91.245.82]
 11    77 ms    76 ms    74 ms  netaccess-tic-133837-nyk-b3.c.telia.net [213.248
.99.90]
 12     9 ms     9 ms     9 ms  0.e1-1.tbr1.ewr.nac.net [209.123.10.129]
 13    10 ms     9 ms    10 ms  0.e1-4.tbr1.oct.nac.net [209.123.10.122]
 14    70 ms    71 ms    70 ms  vlan804.esd1.oct.nac.net [209.123.10.2]
 15    75 ms    76 ms    75 ms  www.dslreports.com [209.123.109.175]

Trace complete.

---

Well from the looks of these tracert's, there is definatly nothing wrong with your or Verizon's systems. Looks like the entire problem is with hop 11. On both tracerts. Those are ATT servers. And ATT has been spotted capping speeds recently. So your link to both DSLreports and your game server are being routed through ATT.

To be honest, your not likely to get any results on this. Most providers will look at that and say it is perfectly acceptible. They likely will not even consider rebooting those routers for anything under 100ms. So this really looks like a problem on the other end rather than yours

[lasagna]

Beg to differ, but these traceroutes are inconclusive.

Traceroutes are point in time round-trip times to a specific hop in the network path.   Any "hop" which has a high RTT simply means that the particular node in question OR any node prior to it in the chain is experiencing latency.   If a subsequent hop exhibits a significantly lower RTT, then obviously the high RTT from the previous hop is not necessarily the cause since RTT's should be additive.

If you hit a hop in the path with a high RTT and then every hop AFTER that hop also exhibits and increasingly high RTT, then that is a good indicator of where the bottleneck is.

Otherwise such as in cases like this, you need to pick the node which first seemed to exhibit the problem and setup a ping measuring RTT to it and then another ping running simulataneously to the hop immediately before it to see if one node stays low and the other stays high at the same time.   If so, then you know where the bottleneck is ... if not, then you need to change your test points and try again until you find two adjacent nodes -- one with a high RTT and one with a low RTT immediately before it.

Regardless ... while 70ms isn't great ... in the land of Internet with traffic crossing more than one ISP, it's not "bad" and as spacedbris indicated, unlikely to garner anyone's attention.  The internet is the internet ... best effort delivery of packets.

[smithj1]

so even if this has been happening consistently for like the past half year, there's nothing I can do about it...? i still don't understand why it only occurs for exactly 4 hours EVERYDAY.