| Problem on verizon's network? I am no longer able to connect to some servers/services this morning and after doing a tracert this is what I see;
G1-5-3-3.WASHDC-LCR-21.verizon-gni.net [130.81.217.66] Destination host unreachable.
Any thoughts? |
|
Reviews:
 ·Verizon FiOS
| said by SoulForge :I am no longer able to connect to some servers/services this morning and after doing a tracert this is what I see;
G1-5-3-3.WASHDC-LCR-21.verizon-gni.net [130.81.217.66] Destination host unreachable.
Any thoughts?
There are some major routing problems on Verizon's network currently. Other people are seeing the same thing for the last few weeks and it's not limited to just a CO or state. |
|
| reply to SoulForge
Yeah, I'm also seeing serious routing issues here in new jersey. It only started today. |
|
mloebl
join:2003-01-03
Tyngsboro, MA | I was working from home the other day and connecting via SSH to work (also on Verizon via their business services.) I watched during the day connection, which was *screaming* earlier just flake out, and traced it out to somewhere in NYC. Flaked like that for 20mins (to the point SSH was unusable with very high pings), then all of a sudden just started to speed up again as if someone hit a switch (or I switched gateways). They definitely are having issues. Unfortunately between the Quantum Speed upgrades and Hurricane Sandy, I suspect it really caused a bunch of problems with them.
I've also noticed since Sandy any of my speed tests, "local" to me in Boston typically show only 8 - 40mbs now (MUCH slower than before.) However NYC shows full speed (85 down / 38up) quite often. I wish I had thought to check my routing before the Hurricane as I see all my traffic quickly leaves Boston, goes to NYC, then back to Boston again for any of the speed test (and most other traffic). Most of the pings are lower there too (i.e. 8 - 12ms to NYC while 20 - 45ms to Boston.) When downloading now I have to fight the urge to pick local and pick NYC or NJ mirrors.
-Mike |
|
| reply to SoulForge
I called tech support today after having problems starting around 1:30PM. Spent an hour or more on the phone and after having the tech reboot the ONT, router and reset the router to factory default, I was still having issues. He now plans to send me a replacement router, which should get here on Friday.
What's interesting is, it appears to be working fine now. The symptoms I had is that a web page would load but new tabs would not (on multiple computers in the house),clicking on links from the loaded page would time out constantly.
My iPhone also drained its battery trying to connect to the Internet via wi-fi and trying to grab my corporate emails via Activesync. Also my smart TV would not connect to the hub. Basically, all devices connected fine to the router but could not get out to the Internet.
Network burp??? |
|
| reply to SoulForge
Similar problem here in Southern California, it comes and goes. However lately it seems to occur more at night. |
|
|
|
| Appears the routing issue has been fixed. |
|
 RolteC0h
join:2001-05-20
Fresh Meadows, NY
kudos:1
1 edit | 
Another night, another post about the SAME thing |
said by SoulForge :Appears the routing issue has been fixed.
Wrong.
What you should say is:
Appears the routing issue is gone for tonight everyone. Check back again tomorrow night for a new edition of packet loss and slow speeds! |
|
Reviews:
·Verizon FiOS
| reply to SoulForge
said by RolteC:Appears the routing issue is gone for tonight everyone. Check back again tomorrow night for a new edition of packet loss and slow speeds!
Will do! /as if I have a choice 
I may ask a friend or relative on TimeWarnerCable to do a tracert/pingtest/speedtest tonight on the same set of sites or content servers at the same time in the evening and compare the results. Sure, latency will probably be a tad higher on cable vs FIOS but I bet he'll clear a lot more successful pageloads than I will  |
|
| reply to RolteC
What I should have said is;
The issue preventing me from accessing the server I was attempting to has been corrected. |
|
