Over the last few days I’ve had slow upload speeds to non-Verizon servers. Uploads to Verizon’s own speed test servers are fine and match my provisioned rate. Downloads are unaffected.
mtr tests from a wired connection directly to my ONT show persistent packet loss beginning at Verizon’s upstream peering points, with the loss persisting downstream. This happens across multiple destinations, so not a single-host routing issue?
1. _gateway 0% loss
2. lo0-100.NYCMNY-VFTTP-339.verizon-gni.net 0% loss
3. B3339.NYCMNY-LCR-21.verizon-gni.net 0% loss
5. ewr-b13-link.ip.twelve99.net 80% loss <--- First hop with real loss
6. nyk-bb5-link.ip.twelve99.net 30% loss
...
25. a23-206-56-116.deploy.static.akamaitechnologies.com 0% loss but degraded throughput 1. _gateway 0% loss
2. lo0-100.NYCMNY-VFTTP-339.verizon-gni.net 0% loss
3. B3339.NYCMNY-LCR-21.verizon-gni.net 0% loss
4. lag-3.NYCMNYAA-PPR01-CC.ALTER.NET 90% loss
5. ALTER.NET.customer.alter.net 20% loss
6. ae2.3609.edge6.Miami1.net.lumen.tech 50% loss
...
19. ae17.r02.ewr01.icn.netarch.akamai.com 80% loss
20. ae2.r02.ewr01.ien.netarch.akamai.com 77.8% lossIs this something that a Verizon network engineer could investigate? This appears to be a transit/peering congestion issue outside the customer premises but within Verizon’s upstream routing?