[outages] Cogent /ATT and Verizon Peering alternatives

[Stephen Wilcox]

On 11 February 2014 01:56, Charles Sprickman <spork at bway.net> wrote:

>
> On Feb 10, 2014, at 8:02 PM, Rusty Hodge 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.
>
> Isn't this the result of VZ/Comcast/ATT and others refusing peering with
> Netflix and Netflix purchasing transit via Cogent to reach them?
>

Its more complicated than that - Netflix pays CDNs, transits etc for
delivery of much of its content.

The original email as I understood was a user seeing packet loss between
their business Internet service with Verizon and either a server hosted
within Cogent or another Internet access service. ie an end user trying to
connect with another end user/host. As such I don't think its about
Netflix, but this end user who is paying two providers neither of which are
delivering.

I would complain to both. I'd also try moving - preferably at both sides.


Steve


> That standoff has been going on for some time, and I would guess with the
> recent court ruling regarding "net neutrality", it's not going to get
> better until Netflix pays VZ and other large eyeball networks to carry
> their traffic (or pays twice, depending on your perspective).
>
> Charles
>
> timely news item:
>
>
> http://arstechnica.com/information-technology/2014/02/netflix-performance-on-verizon-and-comcast-has-been-dropping-for-months/
>
> >
> > 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
>
>
> _______________________________________________
> 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/20140211/f78c3a5a/attachment.htm>