So last week we had a storm knock out our cable box, modem and TV. They came and replaced the modem, box, splitter/coupler outside and had to run a new drop to the house. Ever since they were here our interwebs has issues...Here is a tracert to the servers IP...Not sure what it means other than one of the hops has crazy high ping..I am getting all sorts of ping spikes and connection issues while in game...How do i tell my provider that their stuff is still messed up..? How exactly do i word it to them...?
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\fluffykitten>tracert 8.12.64.130
Tracing route to 8.12.64.130 over a maximum of 30 hops
1 7 ms <1 ms 1 ms Cisco77123 [10.105.43.123]
2 * * * Request timed out.
3 12 ms 9 ms 18 ms crr21ftwotx-tge-0-3-1-3.ftwo.tx.charter.com [96.
34.114.77]
4 17 ms 21 ms 17 ms crr02ftwotx-bue-4.ftwo.tx.charter.com [96.34.112
.70]
5 21 ms 15 ms 15 ms bbr02dllstx-bue-1.dlls.tx.charter.com [96.34.2.3
4]
6 13 ms 15 ms 12 ms 207.86.210.73
7 19 ms 14 ms 21 ms 207.88.14.182.ptr.us.xo.net [207.88.14.182]
8 25 ms 17 ms 30 ms 207.88.14.189.ptr.us.xo.net [207.88.14.189]
9 14 ms 297 ms 438 ms ae15.dal33.ip4.gtt.net [199.168.63.249]
10 59 ms 18 ms 14 ms gtt-gw.ip4.gtt.net [173.241.130.138]
11 18 ms 12 ms 19 ms as20473.xe-5-1-2.cr1.dfw1.us.as4436.gtt.net [69.
31.63.238]
12 18 ms 13 ms 13 ms 8.12.64.130
Trace complete.
C:\Users\fluffykitten>
interwebs problem
Re: interwebs problem
I think I would keep running traceroute a few more times and see if and where the problem consistently stays. Agree that in this current trace the 297ms and 438ms to ae15.dal33.ip4.gtt.net is an issue, as is probably the 59ms time on gtt-gw.ip4.gtt.net.
But all of the "bad" times are immediately adjacent: The first ping to ae15.dal33.ip4.gtt.net was actually 14ms, but then the next two were poor, and the first ping to the next router was poor, and then everything is "back to normal."
I kind of doubt that is "an issue with ae15.dal33.ip4.gtt.net" or "an issue with gtt-gw.ip4.gtt.net". Seems just as probable that something about your ISP connection was just suddenly "poor" during that period of time, and it may not have mattered WHICH router you were in the midst of attempting to ping, it would have come back slow regardless because the connection performance overall is just suddenly slow.
So run traceroute multiple times, at least when you know the problem is happening in-game, and see if the poor ping times "move around" to different routers because it's not really a problem with the routers at all. Or are the poor pings consistently with ae15.dal33.ip4.gtt.net and gtt-gw.ip4.gtt.net, because they actually are the problem.
-Trench
But all of the "bad" times are immediately adjacent: The first ping to ae15.dal33.ip4.gtt.net was actually 14ms, but then the next two were poor, and the first ping to the next router was poor, and then everything is "back to normal."
I kind of doubt that is "an issue with ae15.dal33.ip4.gtt.net" or "an issue with gtt-gw.ip4.gtt.net". Seems just as probable that something about your ISP connection was just suddenly "poor" during that period of time, and it may not have mattered WHICH router you were in the midst of attempting to ping, it would have come back slow regardless because the connection performance overall is just suddenly slow.
So run traceroute multiple times, at least when you know the problem is happening in-game, and see if the poor ping times "move around" to different routers because it's not really a problem with the routers at all. Or are the poor pings consistently with ae15.dal33.ip4.gtt.net and gtt-gw.ip4.gtt.net, because they actually are the problem.
-Trench