<div dir="ltr">I have been told from people within Cogent that they keep hounding upper management, but they are doing nothing about the problems. I can see how dealing with Verizon or ATT could be difficult, but if you are in the business of providing a service, fixing the problem is your responsibility. Hence why we have moved away from Cogent.<div>
<br></div><div>Erich</div><div>AirLogic</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Feb 11, 2014 at 7:44 PM, <span dir="ltr"><<a href="mailto:SRonan@eexchange.com" target="_blank">SRonan@eexchange.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Wešve gotten a similar response as well.<br>
<br>
Dear Cogent Customer,<br>
<br>
The latency and/or packet loss that you are experiencing to this<br>
destination is due to occasional high traffic with Verizon. We have<br>
repeatedly requested augments to these congestion points and hope Verizon<br>
will comply soon. While this has been escalated internally to the CEO<br>
level, we encourage you to also contact Verizon customer support with your<br>
concerns and complaints. Their delay is a major impediment to internet<br>
traffic overall and contrary to net neutrality requirements. Our peering<br>
engineers will continue to address this on a daily basis until resolved.<br>
<br>
<br>
<br>
Shane Ronan, Vice President Technology Architect<br>
State Street Global Exchange | 1230 Avenue of the Americas, 18th Fl | New<br>
York, NY 10020<br>
P <a href="tel:%28212%29%20259-3023" value="+12122593023">(212) 259-3023</a> | M <a href="tel:%28347%29%20413-4503" value="+13474134503">(347) 413-4503</a><br>
<a href="mailto:sronan@eexchange.com">sronan@eexchange.com</a><br>
<br>
<br>
<br>
<br>
<br>
<br>
On 2/11/14, 5:56 PM, "Joseph Jackson" <<a href="mailto:jjackson@aninetworks.net">jjackson@aninetworks.net</a>> wrote:<br>
<br>
>This is why we don't buy from cogent.<br>
><br>
><br>
><br>
>-----Original Message-----<br>
>From: Outages [mailto:<a href="mailto:outages-bounces@outages.org">outages-bounces@outages.org</a>] On Behalf Of Chris<br>
>Stone<br>
>Sent: Tuesday, February 11, 2014 4:51 PM<br>
>To: <a href="mailto:outages@outages.org">outages@outages.org</a><br>
>Subject: Re: [outages] Cogent /ATT and Verizon Peering alternatives<br>
><br>
>And here's what they say about Qwest/CenturyLink - note this is verbatim<br>
>from a response received today - missing words and all:<br>
><br>
>Dear Cogent Customer,<br>
><br>
> The latency and/or packet loss that you are experiencing to this<br>
>destination is due to high traffic with Qwest.<br>
><br>
> The peering connection between Cogent and has been escalated within<br>
>our Senior Management. Our Peering department is actively working with<br>
>to add more capacity as quickly as possible. While Cogent is prepared to<br>
>commit additional capacity, we are still pending to complete their<br>
>planning and provisioning process under the free peering agreement. Due<br>
>to the nature of this process, we cannot determine an estimated time for<br>
>this to be completed.<br>
><br>
><br>
><br>
>On 02/11/2014 03:45 PM, Robert Glover wrote:<br>
>> On 2/11/2014 1:59 PM, Geoff Brozny wrote:<br>
>>> On , Rusty Hodge wrote:<br>
>>>> FYI- This is the form letter that Cogent is sending to anyone who<br>
>>>> opens a ticket about the issues with Verizon. I'm starting to get a<br>
>>>> collection of them.<br>
>>>><br>
>>>><br>
>>>><br>
>>>> Dear Cogent Customer,<br>
>>>><br>
>>>> The latency and/or packet loss that you are experiencing to this<br>
>>>> destination is due to high traffic from one of our peers with Verizon.<br>
>>>> We have reached out to Verizon to request assistance resolving the<br>
>>>> amount of traffic they are sending on this peer and are awaiting<br>
>>>> their response. We will continue to reach out to them until they<br>
>>>>respond.<br>
>>>><br>
>>>> If you have any further questions please feel free to contact us by<br>
>>>> e-mail at <a href="mailto:support@cogentco.com">support@cogentco.com</a> or by phone at 877-7COGENT<br>
>>>> <a href="tel:%28877-726-4368" value="+18777264368">(877-726-4368</a>).<br>
>>>><br>
>>>> Thank You,<br>
>>>><br>
>>>> Cogent Communications<br>
>>>> T <a href="tel:877.726.4368" value="+18777264368">877.726.4368</a>, option 2<br>
>>>> F <a href="tel:202.295.9061" value="+12022959061">202.295.9061</a><br>
>>>> E <a href="mailto:support@cogentco.com">support@cogentco.com</a><br>
>>>><br>
>>>><br>
>>><br>
>>><br>
>>> This is what they are sending when you open a ticket about att:<br>
>>><br>
>>> Dear Cogent Customer,<br>
>>><br>
>>> The latency and/or packet loss that you are experiencing to this<br>
>>> destination is due to occasional high traffic with ATT. We have<br>
>>> repeatedly requested augments to these congestion points and hope ATT<br>
>>> will comply soon. While this has been escalated internally to the<br>
>>> CEO level, we encourage you to also contact ATT customer support with<br>
>>> your concerns and complaints. Their delay is a major impediment to<br>
>>> internet traffic overall and contrary to net neutrality requirements.<br>
>>> Our peering engineers will continue to address this on a daily basis<br>
>>>until resolved.<br>
>>><br>
>>> If you have any further questions please feel free to contact us by<br>
>>> e-mail at <a href="mailto:support@cogentco.com">support@cogentco.com</a> or by phone at 877-7COGENT<br>
>>><a href="tel:%28877-726-4368" value="+18777264368">(877-726-4368</a>).<br>
>>><br>
>>> Thank You,<br>
>>><br>
>>> Cogent Communications<br>
>>> T <a href="tel:877.726.4368" value="+18777264368">877.726.4368</a>, option 2<br>
>>> F <a href="tel:202.295.9061" value="+12022959061">202.295.9061</a><br>
>>><br>
>>><br>
>>><br>
>>> Also there were issues between level3 and att, we managed to get<br>
>>> Level3 to shuffle around the traffic a bit, as the peering<br>
>>> connections were running at 100%+ as well, this made things better,<br>
>>> but supposedly things are still pretty much full though.<br>
>>><br>
>>> geoff<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>
>>><br>
>> Here's another response re: Verizon:<br>
>><br>
>> The issue on this peer involves a high amount of traffic being sent to<br>
>> Cogent from the Verizon network. In order to resolve the congestion on<br>
>> that peer, Verizon needs to engineer thier routing to another peering<br>
>> point with Cogent that has more available space for the traffic. We<br>
>> have reached out to Verizon for assistance and are still awaiting a<br>
>> response from their peering engineers. We will continue to reach out<br>
>> to them until they respond.<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>
><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>
><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>
<br>
<br>
________________________________<br>
<br>
<a href="http://www.statestreet.com/emaildisclaimer/" target="_blank">http://www.statestreet.com/emaildisclaimer/</a><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></div>