<div dir="ltr"><div>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.</div><div><br>
</div><div><div> mtr 71.252.251.1</div></div><div><div> Host Loss% Snt Last Avg Best Wrst StDev</div><div> 1. - 0.0% 42 0.4 0.7 0.3 7.2 1.1</div><div> 2. gi1-3.ccr01 4.8% 42 0.9 3.1 0.7 32.6 6.5</div>
<div> 3. te0-4-1-5.c 0.0% 42 1.4 1.6 1.2 5.4 0.8</div><div> 4. be2333.mpd2 2.4% 41 14.3 13.4 12.8 18.3 1.0</div><div> 5. be2178.ccr2 0.0% 41 13.9 14.7 13.8 19.9 1.3</div><div> 6. uunet.lax05 7.3% 41 53.6 55.0 52.1 73.7 4.1</div>
<div> 7. P0-0-0-0.DL 9.8% 41 84.9 84.4 81.6 91.6 1.9</div><div> 8. ???</div><div> 9. L100.DLLSTX 9.8% 41 83.5 84.1 82.1 87.4 0.9</div></div><div><br></div><div><br></div><div>traceroute to 71.252.251.1 (71.252.251.1), 30 hops max, 60 byte packets</div>
<div> 1 - 2.799 ms 2.583 ms 3.022 ms</div><div> 2 <a href="http://gi1-3.ccr01.phx05.atlas.cogentco.com">gi1-3.ccr01.phx05.atlas.cogentco.com</a> (38.122.88.65) 3.014 ms 3.006 ms 2.999 ms</div><div> 3 <a href="http://te0-4-0-5.ccr21.phx02.atlas.cogentco.com">te0-4-0-5.ccr21.phx02.atlas.cogentco.com</a> (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</div>
<div> 4 <a href="http://be2333.mpd22.lax01.atlas.cogentco.com">be2333.mpd22.lax01.atlas.cogentco.com</a> (154.54.41.249) 15.542 ms <a href="http://be2330.ccr21.lax01.atlas.cogentco.com">be2330.ccr21.lax01.atlas.cogentco.com</a> (154.54.30.189) 14.962 ms <a href="http://be2333.mpd22.lax01.atlas.cogentco.com">be2333.mpd22.lax01.atlas.cogentco.com</a> (154.54.41.249) 15.032 ms</div>
<div> 5 <a href="http://be2180.ccr23.lax05.atlas.cogentco.com">be2180.ccr23.lax05.atlas.cogentco.com</a> (154.54.41.58) 16.159 ms <a href="http://be2181.ccr23.lax05.atlas.cogentco.com">be2181.ccr23.lax05.atlas.cogentco.com</a> (154.54.41.114) 15.435 ms 14.948 ms</div>
<div> 6 <a href="http://uunet.lax05.atlas.cogentco.com">uunet.lax05.atlas.cogentco.com</a> (154.54.13.86) 65.357 ms 62.954 ms 95.462 ms</div><div> 7 <a href="http://P0-8-0-0.DLLSTX-LCR-22.verizon-gni.net">P0-8-0-0.DLLSTX-LCR-22.verizon-gni.net</a> (130.81.199.37) 83.373 ms <a href="http://P0-0-0-0.DLLSTX-LCR-21.verizon-gni.net">P0-0-0-0.DLLSTX-LCR-21.verizon-gni.net</a> (130.81.151.243) 82.127 ms 86.080 ms</div>
<div> 8 * * *</div><div> 9 <a href="http://L100.DLLSTX-VFTTP-64.verizon-gni.net">L100.DLLSTX-VFTTP-64.verizon-gni.net</a> (71.252.251.1) 84.306 ms 84.674 ms 85.160 ms</div><div><br></div></div><div class="gmail_extra">
<br><br><div class="gmail_quote">On Mon, Feb 10, 2014 at 6:02 PM, Rusty Hodge <span dir="ltr"><<a href="mailto:rusty@hodge.com" target="_blank">rusty@hodge.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
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.<br>
<br>
Right now, I'm seeing 43% packet loss<br>
<br>
Cogent is blaming ATT/Verizon and says there is nothing they can do about it. We're the collateral damage.<br>
<br>
Who else is having the same issue?<br>
<br>
I threaten to cancel my service, Cogent says, "sorry to lose you as a customer", and go on their merry way.<br>
<br>
Are other transit providers having issues peering / getting to ATT/Verizon? I need to know who to avoid.<br>
<br>
<br>
<br>
traceroute to 71.252.251.1 (71.252.251.1), 30 hops max, 60 byte packets<br>
1 <a href="http://gi3-11.ccr01.sfo02.atlas.cogentco.com" target="_blank">gi3-11.ccr01.sfo02.atlas.cogentco.com</a> (38.104.130.89) 0.982 ms 0.985 ms 1.195 ms<br>
2 <a href="http://te0-0-0-28.ccr22.sfo01.atlas.cogentco.com" target="_blank">te0-0-0-28.ccr22.sfo01.atlas.cogentco.com</a> (154.54.3.129) 0.531 ms <a href="http://te0-0-0-28.ccr21.sfo01.atlas.cogentco.com" target="_blank">te0-0-0-28.ccr21.sfo01.atlas.cogentco.com</a> (154.54.3.121) 0.604 ms 0.636 ms<br>
3 <a href="http://be2165.ccr22.sjc01.atlas.cogentco.com" target="_blank">be2165.ccr22.sjc01.atlas.cogentco.com</a> (154.54.28.66) 2.277 ms <a href="http://be2164.ccr21.sjc01.atlas.cogentco.com" target="_blank">be2164.ccr21.sjc01.atlas.cogentco.com</a> (154.54.28.34) 1.806 ms 2.449 ms<br>
4 <a href="http://be2000.ccr21.sjc03.atlas.cogentco.com" target="_blank">be2000.ccr21.sjc03.atlas.cogentco.com</a> (154.54.6.106) 3.824 ms 2.504 ms 2.596 ms<br>
5 * * <a href="http://verizon.sjc03.atlas.cogentco.com" target="_blank">verizon.sjc03.atlas.cogentco.com</a> (154.54.12.170) 94.373 ms<br>
6 * * *<br>
7 * * *<br>
8 <a href="http://L100.DLLSTX-VFTTP-64.verizon-gni.net" target="_blank">L100.DLLSTX-VFTTP-64.verizon-gni.net</a> (71.252.251.1) 135.242 ms 86.272 ms 86.231 ms<br>
<br>
<br>
_______________________________________________<br>
Outages mailing list<br>
<a href="mailto:Outages@outages.org">Outages@outages.org</a><br>
<a href="https://puck.nether.net/mailman/listinfo/outages" target="_blank">https://puck.nether.net/mailman/listinfo/outages</a><br>
</blockquote></div><br></div>