nanog: Packet Loss through Level 3 in Southern California?
Jun 13, 2016 Anyone else seeing network routing issues or packet loss Looking at this, the responses are inconsistent and it would appear to be packet loss. Any ideas? I've been simply downloading my selections as zip files and uploading to SAB, but that's annoying. EDIT: I did a traceroute from my server to dog (removed the good responses that ID my server location). High Latency - TCPShield There is packet loss between you and our network, which could result from: Link saturation at any point in the route between us and you. The backend resides on an unstable network (i.e. residential) 6. be3025.ccr41.lax04.atlas.cogentco.com 0.0% 24 148.5 151.8 146.3 180.7 6.7.
Comcast routing my busniess static IP a bad path c
Oct 01, 2015 How to: MTR - Understanding and Troubleshooting Network Dec 24, 2015 Problems with packet loss in certain matches?
How to: MTR - Understanding and Troubleshooting Network
Downstream Routing Issue a) How to really trace Jan 28, 2017 Mailing List Archive: Cogent NOC > mtr packet loss column has no scientific precision and should not be considered. It is not mtr fault but forwarding routers have a low priority to respond to ICMP requests. The only way you can prove there is a problem is a end to end ping, the regular ping command, not mtr. nanog: Packet Loss through Level 3 in Southern California? Our data (see below) seem to show packet loss through Level 3 with associated slow TCP based data transfers. Is anyone else seeing packet loss and consequent slow TCP based transfers when going through Level 3 in (LosAngeles1) Southern California? 1.023 ms 0.823 ms te0-0-0-3.agr12.san01.atlas.cogentco.com (154.24.32.65) 1.359 ms 7 te0-0-1-3