- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
I'm having severe routing issues with almost all locations within the US. Normally I ping 16ms to NYC, but currently its at 162ms. I did a "traceroute" and apparently I'm going to Kansas THEN to the NYC host. What gives?
Also, it seems like I go to Kansas no matter where I try and connect to (NY, VA, GA, etc.).
Are you guys playing a joke on me or what? This has been going on for days now.
edit: I appreciate any help/info given 🙂
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
might be a bad IP block - try to get a new ip address.
if you do it on your own you have to leave your modem off for four hours because the lease time on the ip addresses is four hours.
if you do chat support, they may be able to break your dhcp lease remotely and then make sure to turn off your modem while they do it, and don't trust or listen to them when they say immediately turn on your modem, leave it off for 3-5 minutes before you turn it back on. if you turn it on too fast after they release the ip then you run the risk of getting the same one which you don't want.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
That didn't fix it 😞
Any other ideas? I really don't want to call their support line and be told to DELETE COOKIES, CHECK TCP/IP SETTINGS, REBOOT 😄. Do any Verizon tech support guys read these forums?
Thanks for any help!
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Why don't you post an actual tracert? It might generate some ideas on why you're having the problem.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Tracing route to 69.12.108.138 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 5 ms 6 ms 7 ms L100.NWRKNJ-VFTTP-134.verizon-gni.net [173.70.26
.1]
3 7 ms 7 ms 7 ms G14-0-4-1534.NWRKNJ-LCR-05.verizon-gni.net [130.
81.60.76]
4 10 ms 9 ms 10 ms so-6-0-2-0.NWRK-BB-RTR1.verizon-gni.net [130.81.
28.148]
5 15 ms 14 ms 29 ms so-12-0-0-0.NY325-BB-RTR1.verizon-gni.net [130.8
1.17.6]
6 11 ms 47 ms 11 ms 0.ae3.BR2.NYC4.ALTER.NET [152.63.3.110]
7 11 ms 12 ms 12 ms 204.255.173.54
8 11 ms 12 ms 12 ms vlan52.ebr2.NewYork2.Level3.net [4.69.138.254]
9 14 ms 14 ms 14 ms ae-6-6.ebr2.NewYork1.Level3.net [4.69.141.21]
10 22 ms 16 ms 16 ms ae-62-62.csw1.NewYork1.Level3.net [4.69.148.34]
11 13 ms 12 ms 12 ms ge-7-0.ipcolo2.NewYork1.Level3.net [4.68.97.14]
12 87 ms 96 ms 87 ms 166.90.136.34
13 87 ms 87 ms 88 ms 69.12.108.138
Trace complete.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
So what's the problem?
I get almost identical results to that same IP address from here on Long Island. There's some latency (but not horrible) after the trace leaves the Level3 backbone. I don't see any issue...especially not one that's FiOS related.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The issue is: why am I being routed to Kansas right before I reach my final destination in New York.
If it wasn't a big deal I wouldn't be asking about it. Every area I try and connect to I am being thrown to Kansas as a 'last stop' before I reach my final destination. This has never happened before.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
What do you get if you tracert dslreports.com?
Tracing route to dslreports.com [209.123.109.175]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.0.1
2 7 ms 7 ms 9 ms L100.NYCMNY-VFTTP-119.verizon-gni.net [71.241.15
3.1]
3 6 ms 7 ms 7 ms G2-0-3-1119.NYCMNY-LCR-11.verizon-gni.net [130.8
1.107.162]
4 8 ms 9 ms 9 ms so-2-1-0-0.NY325-BB-RTR1.verizon-gni.net [130.81
.29.12]
5 11 ms 12 ms 9 ms 0.so-0-0-0.XL3.NYC4.ALTER.NET [152.63.1.41]
6 9 ms 10 ms 9 ms GigabitEthernet6-0-0.GW1.NYC4.ALTER.NET [152.63.
20.49]
7 11 ms 10 ms 9 ms teliasonera-gw.customer.alter.net [157.130.60.14
]
8 8 ms 10 ms 9 ms nyk-bb1-link.telia.net [80.91.248.149]
9 11 ms 9 ms 10 ms nyk-b3-link.telia.net [80.91.248.174]
10 9 ms 12 ms 12 ms netaccess-tic-133837-nyk-b3.c.telia.net [213.248
.99.90]
11 12 ms 10 ms 9 ms 0.e1-4.tbr1.mmu.nac.net [209.123.10.101]
12 12 ms 12 ms 12 ms 0.e1-1.tbr1.oct.nac.net [209.123.10.17]
13 12 ms 12 ms 12 ms vlan804.esd1.oct.nac.net [209.123.10.2]
14 12 ms 9 ms 12 ms www.dslreports.com [209.123.109.175]
Trace complete.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
@hyper wrote:The issue is: why am I being routed to Kansas right before I reach my final destination in New York.
If it wasn't a big deal I wouldn't be asking about it. Every area I try and connect to I am being thrown to Kansas as a 'last stop' before I reach my final destination. This has never happened before.
the way the internet routes information is in two different ways.
Shortest path
and
open path
sometimes even though a route may be closer in state, it may be congested, and so traffic is routed to more open paths.
its normal for it to go all over the place in my opinion, depending on local network traffic in the area. kansas may have less crowded pipes and be able to deliver faster because of that.
I wouldn't bother calling verizon on that, - the latency is too low for them to look at it as a serious problem, and they don't do re-routes on individual case basis.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
@hyper wrote:Tracing route to 69.12.108.138 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 5 ms 6 ms 7 ms L100.NWRKNJ-VFTTP-134.verizon-gni.net [173.70.26.1]
3 7 ms 7 ms 7 ms G14-0-4-1534.NWRKNJ-LCR-05.verizon-gni.net [130.81.60.76]
4 10 ms 9 ms 10 ms so-6-0-2-0.NWRK-BB-RTR1.verizon-gni.net [130.81.28.148]
5 15 ms 14 ms 29 ms so-12-0-0-0.NY325-BB-RTR1.verizon-gni.net [130.81.17.6]
6 11 ms 47 ms 11 ms 0.ae3.BR2.NYC4.ALTER.NET [152.63.3.110]
7 11 ms 12 ms 12 ms 204.255.173.54
8 11 ms 12 ms 12 ms vlan52.ebr2.NewYork2.Level3.net [4.69.138.254]
9 14 ms 14 ms 14 ms ae-6-6.ebr2.NewYork1.Level3.net [4.69.141.21]
10 22 ms 16 ms 16 ms ae-62-62.csw1.NewYork1.Level3.net [4.69.148.34]
11 13 ms 12 ms 12 ms ge-7-0.ipcolo2.NewYork1.Level3.net [4.68.97.14]
12 87 ms 96 ms 87 ms 166.90.136.34
13 87 ms 87 ms 88 ms 69.12.108.138
There's nothing in that traceroute that indicates you're being routed through Kansas.
69.12.108.138 is a New York ISP (MY INTERNET SERVICES)