[outages] Cogeco - Toronto outage?

Mike Dresser mikedresser at gmail.com
Wed May 16 12:39:25 EDT 2018


Appears they're having some bigger issues, I couldn't reach www.esasafe.com
from a Cogeco business fiber line, but could from a connection that is
based off cogeco's cable network(start.ca).  MTR got completely lost on the
fiber link(stops two hops past burl-ts1.cgocable.net, with heavy(8-10%)
packet loss from that point on), but made it to Rogers (the hoster of
esasafe.com) from the home connection just fine.

Just retested after typing the above up and it appears to work again, so
they're having some issues.

On Wed, May 16, 2018 at 9:20 AM, Nick Pron via Outages <outages at outages.org>
wrote:

> LAN type. That’s what it seems like.
>
>
>
> We did notice that a customer we have on ICA we can’t reach them as one of
> the hops goes through Cogeco
>
>
>
> *From:* Paul Stewart [mailto:paul at paulstewart.org]
> *Sent:* Wednesday, May 16, 2018 8:57 AM
> *To:* Nick Pron <Nick.Pron at xbase.com>; outages at outages.org List <
> outages at outages.org>
> *Subject:* Re: [outages] Cogeco - Toronto outage?
>
>
>
> Is the NNI with them for LAN type services or is it TPIA?  We have both
> and are not experiencing any issues so sounds like possibly the demarcation
> switch you are connected to possibly ….
>
>
>
> Paul
>
>
>
> *From: *Outages <outages-bounces at outages.org> on behalf of Nick Pron via
> Outages <outages at outages.org>
> *Reply-To: *Nick Pron <Nick.Pron at xbase.com>
> *Date: *Wednesday, May 16, 2018 at 8:54 AM
> *To: *"outages at outages.org List" <outages at outages.org>
> *Subject: *[outages] Cogeco - Toronto outage?
>
>
>
> Anyone have info about this? We’ve been having issues with our NNI since
> Monday with our customers (down, packet loss, etc)
>
>
>
> Cogeco’s master tickets 718506 and 719701 claim they’ve swapped line cards
> in a core switch, upgraded IOS and still working with Cisco.
>
> Our rep seems to hint at that there’s more at play here than the tickets
> are saying..
>
>
>
> Last update from them was 7:35 AM EDT
>
> Unfortunately, we have seen further instability on the affected network
> device and are continuing to work with our Cisco partner to isolate the
> issue and implement a restoration plan.
>
> We are still unable to provide an estimated time to restore but we will
> provide further updates as soon as more information becomes available.
>
> Once again we apologize for any disruption to your services that this may
> be causing.
>
>
>
>
>
> _______________________________________________ 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/20180516/e15bdb56/attachment.htm>


More information about the Outages mailing list