One of our routers is broken...
...or we stuffed up a firmware update.
But we can't tell you more, because we disabled remote access to all our routers as a security measure.
// or some such tale
Canadian ISP Shaw is experiencing a "nationwide outage affecting internet browsing", according to the polite phone robot put in place to discourage affected punters from overwhelming support systems. The issue appears to be multi-faceted. Your Canadian vultures have personally encountered numerous "rolling" outages over the …
Nyet. There are so many fiddly little agreements, so many stupid little routes put in for political and financial reasons that the basis of routing on which the internet was founded - get the fucking packet there in the most efficient manner possible - seems to no longer apply. At least not for everyone, and certainly not all of the time.
Office 365, MS may control their own Asure Cloud's reliability...the connections in-between not so much. When I was doing tech support I can recall times when Office 365 outages cut us techs off from our hourly event notifications. The Shaw tech support guys must be getting hammered with calls and their own notifications may be cut off by this too. There's nothing like the experience of looking up at the call queue board and seeing 2000+ incoming calls waiting. Best of luck to Vulture North, Shaw and all their customers.
Seriously, around here we just assume that once or twice a day the Internet will just stop happening for no obvious reason.
Such is life with Shaw as your ISP.
Personally I think that they're all pissed off at us for using Netflix at $9.95 a month instead of paying them $75 a month for a bundle of mostly crappy cable channels....
(Is it just me, or has "routing issues" become the new catch-all excuse for any Internet outage?)
I'm investigating exactly that. The big question then is "why do we have some sites where all protocols work except a specific few?"
I suppose it's possible that, for example, RDP (and not just to 3389, but all RDP!) is being sent to a DPI system and that hitting the 512K limit has screwed up routing for that protocol. I'll buy that as a possibility, but doing DPI on RDP sessions is really, really rude. I wonder if this didn't have some sort of cascade effect on DPI systems beyond just the basic routing issue.
Biting the hand that feeds IT © 1998–2019