[outages] Cogent /ATT and Verizon Peering alternatives

Lee ler762 at gmail.com
Mon Feb 10 20:41:48 EST 2014


On 2/10/14, 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


If it helps any - traceroute from Verizon home FIOS to you & to your destination
C:\>tracert 38.104.130.89

Tracing route to gi3-11.ccr01.sfo02.atlas.cogentco.com [38.104.130.89]
over a maximum of 30 hops:

    [.. snip ..]
  5    10 ms     7 ms     7 ms  G1-6-0-6.WASHDC-LCR-21.verizon-gni.net
[130.81.217.150]
  6     9 ms     8 ms     7 ms
so-12-1-0-0.RES-BB-RTR1.verizon-gni.net [130.81.151.230]
  7    10 ms     9 ms     9 ms  0.xe-9-0-0.BR2.IAD8.ALTER.NET [152.63.38.133]
  8     *       85 ms     *
te0-1-0-14.ccr41.iad02.atlas.cogentco.com [154.54.12.45]
  9    83 ms    82 ms    82 ms  be2113.mpd21.dca01.atlas.cogentco.com
[154.54.6.170]
 10    89 ms    89 ms    92 ms  be2154.mpd21.ord01.atlas.cogentco.com
[154.54.30.198]
 11    90 ms    89 ms    90 ms  be2158.mpd21.mci01.atlas.cogentco.com
[154.54.7.129]
 12   126 ms   120 ms   119 ms  be2256.ccr21.sfo01.atlas.cogentco.com
[154.54.6.89]
 13    91 ms    87 ms    87 ms  gi3-11.ccr01.sfo02.atlas.cogentco.com
[38.104.130.89]

Trace complete.

C:\>tracert 71.252.251.1

Tracing route to L100.DLLSTX-VFTTP-64.verizon-gni.net [71.252.251.1]
over a maximum of 30 hops:

    [.. snip ..]
  5     9 ms     7 ms    10 ms  G1-6-0-5.WASHDC-LCR-21.verizon-gni.net
[130.81.217.148]
  6    54 ms     7 ms     7 ms  ae4-0.RES-BB-RTR1.verizon-gni.net
[130.81.199.122]
  7    47 ms    47 ms    47 ms
xe-4-0-3-0.DFW9-BB-RTR1.verizon-gni.net [130.81.23.217]
  8    53 ms    49 ms    47 ms  P0-8-0-0.DLLSTX-LCR-21.verizon-gni.net
[130.81.199.35]
  9     *        *        *     Request timed out.
 10    51 ms    49 ms    51 ms  L100.DLLSTX-VFTTP-64.verizon-gni.net
[71.252.251.1]

Trace complete.


Regards,
Lee



More information about the Outages mailing list