Cogent found the problem today. It took them 4 days to do a ‘show conf’ and
see that an outbound access-list was applied to my interface by mistake during
a ‘normal maintenance window at 8AM EST on Friday’
4 days of jumping through hoops to prove that the problem wasn’t on my network.
grum
Possibly related to their mass outage last night around 5:12am CST
(ticket number HD005596458). We're connected at their 427 S La
Salle POP in Chicago.
brandon
On Sat, Dec 7, 2013 at 6:58 PM, Matthew Crocker
wrote:
>
> On Dec 7, 2013, at 3:40 PM, Jason Canady wrote:
>
>> Unfortunately Cogen
On Dec 7, 2013, at 3:40 PM, Jason Canady wrote:
> Unfortunately Cogent has a lot of peering issues. We use them in our network
> blend and we have been having lots of problems with traffic outbound to
> Comcast. It looks like from South Bend, Indiana on Cogent to Chicago / Level
> 3 we are
Honestly from the Internet Health Report, I've noticed connections between
Level3 and Cogent are red quite a bit.
http://www.internethealthreport.com/
Bad samples or peering issues could be the cause either way, but it's been
ongoing for awhile.
Sincerely,
Eric Tykwinski
TrueNet, Inc.
P: 610-4
Unfortunately Cogent has a lot of peering issues. We use them in our
network blend and we have been having lots of problems with traffic
outbound to Comcast. It looks like from South Bend, Indiana on Cogent
to Chicago / Level 3 we are getting a very tiny amount of packet loss
and a higher tha
Anyone seeing issues between Cogent & Level3 in NYC?
I have Sprint & Cogent for bandwidth. Everything has been humming along for a
couple years just fine. Yesterday around 8:00AM my BGP session with Cogent
flapped. Now, when my Cogent BGP is up I get 100% packet loss in level3 land.
When
6 matches
Mail list logo