- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
How do you report a routing issue in the FiOS backbone, Since 11AM ET today phpala cannot access microsoft azure east us 2 datacenter.
It never leaves the FIOS network.
I can get there just fine on T-mobile.
I can find no way to report such an issue and using the assistant is an ai disaster, and asking for a callback got me nothing today at all.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Please DM me the affected IP address ranges, thanks. I will channel to wireline operations.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi. Do you still have access to report issues like this? Verizon has removed their IPv6 routes to AS3352 (Movistar Spain) for almost 22 hours now (since 8:04pm EST on 12/18). The routes typically disappear for a few hours every few weeks, and this has been ongoing for at least 9 months. But this is the longest that it's been down. I've tried reporting it through the normal channels and can't get anywhere (agents stop responding or I get disconnected). It seems to affect both fios and wireless. Movistar IPv4 is unaffected.
When I try to ping an IP in that range from Verizon (such as 2a02:9003:a4:52bf:2e0:67ff:fe2b:9924), the first hop router returns no route to host. From AS3352, traceroutes stop as soon as it hits Verizon's network. During a previous outage, I used Verizon's looking glass utility (https://www.verizon.com/business/why-verizon/looking-glass/ which is not functioning at the moment), and it showed no route to AS3352. Once it recovered, looking glass correctly showed the route. I have no trouble reaching AS3352 from multiple other ISPs.