[outages] Cogent /ATT and Verizon Peering alternatives

[Anthony Kosednar]

I'm seeing anywhere from 7-33% packet loss on cognet n phoenix to your
destination.  It averages around 9% though, Most of the packet loss happens
on the last run before it hits verizon.

 mtr 71.252.251.1
 Host           Loss%   Snt   Last   Avg  Best  Wrst StDev
 1. -   0.0%    42    0.4   0.7   0.3   7.2   1.1
 2. gi1-3.ccr01  4.8%    42    0.9   3.1   0.7  32.6   6.5
 3. te0-4-1-5.c  0.0%    42    1.4   1.6   1.2   5.4   0.8
 4. be2333.mpd2  2.4%    41   14.3  13.4  12.8  18.3   1.0
 5. be2178.ccr2  0.0%    41   13.9  14.7  13.8  19.9   1.3
 6. uunet.lax05  7.3%    41   53.6  55.0  52.1  73.7   4.1
 7. P0-0-0-0.DL  9.8%    41   84.9  84.4  81.6  91.6   1.9
 8. ???
 9. L100.DLLSTX  9.8%    41   83.5  84.1  82.1  87.4   0.9


traceroute to 71.252.251.1 (71.252.251.1), 30 hops max, 60 byte packets
 1  -  2.799 ms  2.583 ms  3.022 ms
 2  gi1-3.ccr01.phx05.atlas.cogentco.com (38.122.88.65)  3.014 ms  3.006 ms
 2.999 ms
 3  te0-4-0-5.ccr21.phx02.atlas.cogentco.com (154.54.84.221)  3.488 ms
154.54.89.109 (154.54.89.109)  4.160 ms 154.54.89.105 (154.54.89.105)
 3.468 ms
 4  be2333.mpd22.lax01.atlas.cogentco.com (154.54.41.249)  15.542 ms
be2330.ccr21.lax01.atlas.cogentco.com (154.54.30.189)  14.962 ms
be2333.mpd22.lax01.atlas.cogentco.com (154.54.41.249)  15.032 ms
 5  be2180.ccr23.lax05.atlas.cogentco.com (154.54.41.58)  16.159 ms
be2181.ccr23.lax05.atlas.cogentco.com (154.54.41.114)  15.435 ms  14.948 ms
 6  uunet.lax05.atlas.cogentco.com (154.54.13.86)  65.357 ms  62.954 ms
 95.462 ms
 7  P0-8-0-0.DLLSTX-LCR-22.verizon-gni.net (130.81.199.37)  83.373 ms
P0-0-0-0.DLLSTX-LCR-21.verizon-gni.net (130.81.151.243)  82.127 ms  86.080
ms
 8  * * *
 9  L100.DLLSTX-VFTTP-64.verizon-gni.net (71.252.251.1)  84.306 ms  84.674
ms  85.160 ms



On Mon, Feb 10, 2014 at 6:02 PM, Rusty Hodge <rusty at hodge.com> wrote:

> We are seeing lots of problems with our audio streaming traffic dropping
> lots of packets where our transit provider Cogent hands off to ATT &
> Verizon.
>
> Right now, I'm seeing  43% packet loss
>
> Cogent is blaming ATT/Verizon and says there is nothing they can do about
> it. We're the collateral damage.
>
> Who else is having the same issue?
>
> I threaten to cancel my service, Cogent says, "sorry to lose you as a
> customer", and go on their merry way.
>
> Are other transit providers having issues peering / getting to
> ATT/Verizon? I need to know who to avoid.
>
>
>
> traceroute to 71.252.251.1 (71.252.251.1), 30 hops max, 60 byte packets
>  1  gi3-11.ccr01.sfo02.atlas.cogentco.com (38.104.130.89)  0.982 ms
>  0.985 ms  1.195 ms
>  2  te0-0-0-28.ccr22.sfo01.atlas.cogentco.com (154.54.3.129)  0.531 ms
> te0-0-0-28.ccr21.sfo01.atlas.cogentco.com (154.54.3.121)  0.604 ms  0.636
> ms
>  3  be2165.ccr22.sjc01.atlas.cogentco.com (154.54.28.66)  2.277 ms
> be2164.ccr21.sjc01.atlas.cogentco.com (154.54.28.34)  1.806 ms  2.449 ms
>  4  be2000.ccr21.sjc03.atlas.cogentco.com (154.54.6.106)  3.824 ms  2.504
> ms  2.596 ms
>  5  * * verizon.sjc03.atlas.cogentco.com (154.54.12.170)  94.373 ms
>  6  * * *
>  7  * * *
>  8  L100.DLLSTX-VFTTP-64.verizon-gni.net (71.252.251.1)  135.242 ms
>  86.272 ms  86.231 ms
>
>
> _______________________________________________
> 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/20140210/3db5db33/attachment.htm>