General Discussion
In reply to the discussion: Verizon ALREADY throttling Netflix, Amazon [View all]Egnever
(21,506 posts)but his traceroutes prove him wrong
Here is his home trace
Tracing route to iscanonline.com [23.21.158.115]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.1.1
2 7 ms 7 ms 8 ms L100.DLLSTX-VFTTP-65.verizon-gni.net [173.74.57.1]
3 10 ms 6 ms 9 ms G0-5-2-0.DLLSTX-LCR-21.verizon-gni.net [130.81.190.204]
4 16 ms 9 ms 10 ms so-5-0-0-0.DFW9-BB-RTR1.verizon-gni.net [130.81.199.34]
5 10 ms 9 ms 9 ms 0.xe-3-3-0.BR2.DFW13.ALTER.NET [152.63.100.5]
6 9 ms 10 ms 9 ms 204.255.168.158
7 10 ms 9 ms 10 ms ae-1.r08.dllstx09.us.bb.gin.ntt.net [129.250.3.27]
each line is a hop along the path to the destination the numbers with ms behind them indicate the time it takes for the signal to go from his computer to each step in the path along the way and back. He left off the first step of both patch that would be his own compter probably to hide his home IP adress. But the first jump listed is 192.168.1.1 whis is a very common default adress for a router. Notice at home when he takes that first step the response times from the router before he ever gets to verizon is <1 ms that is a good response and what you would expect to see. All of the hops continuing down the path have decent response times notice #2 that is where he first hits Verizons network and the times there are also normal in a system that is running properly.
When you look at his business though we see something completely different.
1 192.168.1.1 (192.168.1.1) 18.036 ms 1.326 ms 2.318 ms
2 l100.dllstx-vfttp-93.verizon-gni.net (71.244.30.1) 5.870 ms 5.211 ms 5.193 ms
3 g0-5-0-2.dllstx-lcr-21.verizon-gni.net (130.81.138.12) 7.400 ms 67.679 ms 10.605 ms
4 so-5-0-0-0.dfw9-bb-rtr1.verizon-gni.net (130.81.199.34) 12.062 ms 6.652 ms 17.799 ms
5 0.xe-3-3-0.br2.dfw13.alter.net (152.63.100.5) 7.207 ms 7.858 ms 9.616 ms
6 204.255.168.158 (204.255.168.158) 7.435 ms 7.256 ms 10.366 ms
7 ae-1.r08.dllstx09.us.bb.gin.ntt.net (129.250.3.27) 7.365 ms 10.160 ms 9.083 ms
Notice the first step again with the default router adress 192.168.1.1
This time the response times are in the thousands of ms (miliseconds) anything after that is going to be screwed regardless because the router itself is broken. His problem at work starts before he ever hits the verizon network.
If he unplugged the router from verizon and just pinged the router itself he would still have horrible response times because the router is malfunctioning.