Shaw Outage

[ZenOps]

I don't think it was just a server issue, because Teksavvy went down for an hour as well.

Would not be surprised if a disgruntled former employee decided to flip a switch.

[Xtrema]

Originally posted by rage2
Oddly enough, my Shaw never went down. Wonder what's different about my setup.

It will be interesting to know the scope. Our Shaw line here never went down either and my alarm and cameras at homes never freaked out.

[rage2]

Originally posted by Xtrema
It will be interesting to know the scope. Our Shaw line here never went down either and my alarm and cameras at homes never freaked out.

Wonder if it was a DNS issue since most people by default use Shaw's DNS servers. Their DNS servers used to be wildly unreliable, but it's gotten better over the years. Would explain all the home phones not being able to find where to connect to as well.

I run my own DNS servers so reliability is on me, and I get better routes doing so as well.

[killramos]

My security cameras showed an hour of downtime yesterday. I'm just happy it all came back online on its own because the new shaw modems do a shit job of reconnecting and I usually have to do it manually.

[adam c]

This was the Shaw response for those wondering



********UPDATE************

Teams identified an ACL was updated on multiple routers and is currently being rolled back to restore services.

[eblend]

Originally posted by rage2

Wonder if it was a DNS issue since most people by default use Shaw's DNS servers. Their DNS servers used to be wildly unreliable, but it's gotten better over the years. Would explain all the home phones not being able to find where to connect to as well.

I run my own DNS servers so reliability is on me, and I get better routes doing so as well.

We use Cisco Umbrella DNS at work and we were down, so I think it's more than DNS.

[adam c]

Originally posted by eblend


We use Cisco Umbrella DNS at work and we were down, so I think it's more than DNS.

Look one post up

[revelations]

Originally posted by adam c
This was the Shaw response for those wondering



********UPDATE************

Teams identified an ACL was updated on multiple routers and is currently being rolled back to restore services.

There has to be more to that story. I just cant see SHAW updating ALL the major system infrastructure simultaneously .... for exactly this reason.

Start with a smaller area and work your way up.

[revelations]

Originally posted by eblend


We use Cisco Umbrella DNS at work and we were down, so I think it's more than DNS.

I was being issued a WAN address of 192.168.100.xxx ..... not a DNS issue.

[adam c]

Originally posted by revelations


There has to be more to that story. I just cant see SHAW updating ALL the major system infrastructure simultaneously .... for exactly this reason.

Start with a smaller area and work your way up.

This is all the details we were provided, seems like someone fucked up big time, which happens when you layoff numerous staff

[revelations]

from reddit /Canada

I work with a Shaw Business Partner, and they were upgrading their core network over the last couple of days and were having IP assignment issues which caused intermittent issues yesterday. I assume today's issue is related to the upgrade as well.

which correlates to what I saw on my end ....

Outage was caused by Cisco performing upgrades on backbone routers. Affected multiple isps across the Nation.

Still, allowing Cisco etc. to just dump all the major units like that is deplorable.

[rage2]

I'm on static IP so that makes sense why I was fine.

[firebane]

Yeah my IP changed as well from the outage.

[Brent.ff]

Mines been out pushing 3.5 hours.. anyone else?

[adam c]

Fine in McKenzie Towne

[A790]

Fine in New Brighton.

[ercchry]

Inglewood seems okay

[firebane]

https://community.shaw.ca/docs/DOC-17638

3.5hr outage for me.

[Brent.ff]

Still out in deer ridge.

[firebane]

This quote is hidden because you are ignoring this member. Show Quote

Still out in deer ridge.

I usually work from home on Friday ... Not today.