[outages] Cogent packet loss and jitter

[Ethan Katz-Bassett]

The latency at hop 6 isn't necessarily related to the end-to-end problem
(as pointed out in the slides Jeremy sent)- it's not carrying through to
any later hops, so it could just be a bad asymmetric reverse path from that
particular router or that router being slow on traceroute responses. That
hop is perfectly responsive when I ping it from a variety of locations,
even if the responses are sometimes slow.

The latency to hop 10 (after Cogent) is about the same as the latency to
hop 5 (inside Cogent), and the latency doesn't really go up until the hop
in Denver (when suddenly you have a much longer path). None of my comments
say anything about the loss, however.

On Wed, Oct 10, 2012 at 6:30 PM, Carlos Alvarez <carlos at televolve.com>wrote:

> On Wed, Oct 10, 2012 at 6:23 PM, Brent Jones <brent at brentrjones.com>wrote:
>
>> (even to other Cogent on-net POPs)
>
>
> This right here is frustrating, since they are in the same city and same
> network:
>
>  5  vl3810.mag02.phx02.atlas.cogentco.com (66.28.64.209)  12.983 ms
>  12.979 ms  12.964 ms
>  6  * te7-4.ccr01.phx02.atlas.cogentco.com (154.54.85.85)  195.832 ms *
>
> As you might imagine, we have a lot of complaints.
>
> --
> Carlos Alvarez
> TelEvolve
> 602-889-3003
>
>
>
> _______________________________________________
> Outages mailing list
> Outages at outages.org
> https://puck.nether.net/mailman/listinfo/outages
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/outages/attachments/20121010/f77cef66/attachment.htm>