- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Recently I have had slow connections to most web sites. Once connection is made, things seem OK. I dod a trace route to verizon.net and appears there is a bad router. Anybody else having slow web site connections ? How can we report this to Verizon ?
Tracing route to verizon.net [206.46.232.39] over a maximum of 30 hops:
1 319 ms <1 ms <1 ms myrouter.home [192.168.1.1]
2 7 ms 6 ms 7 ms L100.LSANCA-VFTTP-142.verizon-gni.net [173.55.53.1]
3 10 ms 6 ms 9 ms G0-3-3-3.LSANCA-LCR-22.verizon-gni.net [130.81.180.176]
4 * * * Request timed out.
5 66 ms 46 ms 45 ms ge-3-1-0-0.DFW01-BB-RTR1.verizon-gni.net [130.81.17.68]
6 48 ms 46 ms 47 ms so-1-0-0-0.DFW03-CORE-RTR1.verizon-gni.net [130.81.20.157]
7 44 ms 46 ms 44 ms po1.ctn-border1.vzlink.com [206.46.225.85]
8 46 ms 44 ms 44 ms po121.ctn-core1.vzlink.com [206.46.225.18]
9 46 ms 45 ms 46 ms 206.46.228.130
10 46 ms 46 ms 46 ms 206.46.232.39
Trace complete.
This trace is 100% repeatable.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
For traveling from Los Angeles to the Dallas/Fort Worth area, the latency is acceptable. Did the router at Hop 4 respond in the past before this problem started to occur? Have you tried other DNS servers to ensure the delay isn't actually related to slow DNS Lookups?
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks for the reply. I am not upset with the LAX to DFW times, just the inop router. Normally, the link to verizon is about 5 hops. It appears a router is down and the 'system' reroutes the connection once the router (4) times out.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
@chinorider wrote:Thanks for the reply. I am not upset with the LAX to DFW times, just the inop router. Normally, the link to verizon is about 5 hops. It appears a router is down and the 'system' reroutes the connection once the router (4) times out.
That is a natural behavior of the internet. It routes traffic based on shortest path/fastest path. So if it thinks the shortest/fastest is a different route, then it will take it.
Also If the 4th router is configured not to respond to pings, it will appear as a timeout.
That does not mean that is where the problem is. Your ping times to the 5th router are normal, so there is nothing wrong with the 4th router.