- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello,
Recently there has been lot of packet loss between NTT and Verizon Fios.
mtr -rn 108.51.80.12x HOST: localhost Loss% Snt Last Avg Best Wrst StDev 1.|-- 77.247.178.xxx 0.0% 10 0.4 0.4 0.3 1.2 0.3 2.|-- 85.159.239.6 0.0% 10 0.5 0.5 0.4 0.5 0.0 3.|-- 85.159.239.29 0.0% 10 0.9 0.9 0.6 2.4 0.5 4.|-- 81.20.64.113 0.0% 10 1.2 1.1 1.0 1.2 0.1 5.|-- 129.250.2.146 0.0% 10 1.3 1.3 0.8 3.9 1.0 6.|-- 129.250.2.144 0.0% 10 96.0 97.5 96.0 108.8 4.0 7.|-- 129.250.4.207 0.0% 10 92.6 92.7 92.5 93.0 0.1 8.|-- 129.250.8.38 0.0% 10 144.8 148.0 142.2 164.0 7.1 | `|-- 129.250.8.34 9.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0 10.|-- 108.51.80.12x 10.0% 10 142.5 143.9 141.2 146.7 2.2
Anyone else having same issues? I tried contacting support but problem happens offten at night time and is fixed within 6 to 8 hours.
Thanks
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi, wondering if you were ever able to resolve this or get any additional info from Verizon on it?
I have some customers on FIOS reporting problems to our ec2 servers. After some a couple nights of debugging I found your post and I have a set of remarkably similar mtr output (also have a similar trace to a 108.x.x.x FIOS endpoint):
HOST: ip-10-45-5-2xx Loss% Snt Last Avg Best Wrst StDev 1.|-- 100.104.104.1xx 0.0% 10 0.7 1.3 0.7 6.3 1.8 2.|-- 100.74.169.9 0.0% 10 0.4 0.5 0.4 0.7 0.1 3.|-- 100.74.169.24 0.0% 10 0.4 0.5 0.4 0.6 0.1 4.|-- 100.66.98.4 0.0% 10 0.4 0.4 0.3 0.5 0.0 5.|-- 100.66.3.190 0.0% 10 1.3 1.3 0.9 1.7 0.2 6.|-- 100.64.226.55 0.0% 10 1.0 1.4 0.9 2.2 0.4 7.|-- 100.64.225.182 0.0% 10 1.5 1.3 0.9 2.6 0.5 8.|-- 100.64.58.100 0.0% 10 0.4 1.2 0.3 5.6 1.8 9.|-- 100.64.13.89 0.0% 10 1.0 1.3 0.9 2.3 0.4 10.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0 11.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0 12.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0 13.|-- 100.64.16.1 0.0% 10 0.5 1.4 0.4 7.6 2.2 14.|-- 205.251.245.43 0.0% 10 6.6 9.8 0.4 66.4 20.4 15.|-- 205.251.245.46 0.0% 10 0.7 0.9 0.7 1.1 0.1 16.|-- 205.251.245.0 0.0% 10 1.2 1.1 0.8 1.2 0.1 17.|-- 168.143.228.37 0.0% 10 1.4 1.4 1.4 1.5 0.0 18.|-- 129.250.8.38 0.0% 10 46.4 49.8 46.4 52.6 2.2 | `|-- 129.250.8.34 19.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0 20.|-- 173.79.220.xxx 10.0% 10 63.1 59.8 53.7 63.1 2.9
Wondering how to proceed with Verizon, as you mention this only seems to occur during night-time hours, so it's a tricky issue to get support on. For us it means very slow (1mbps or less) transfer speeds between our servers and the FIOS customer, which is unacceptable.
-Tom
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Have you tried reaching out on the NANOG mailing list? No support staff here is even close to capable of helping you with a more technical issue like this...
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
In FiOS Tampa here on a 75/35 line and was having trouble with streaming Crunchyroll the last couple of nights. The stream was struggling to reach 1Mbs. Following their troubleshooting with a tracert to cp150757.edgefcs.net showed the issue was in the ntt.net part of the route. About an hour later it cleared up and a tracert showed no NTT in the route. Matches what Tom said.