> We're currently investigating potential impact to performance with our CDN services.

Guys, you are offline with a 503 error, this is a little more than "potential impact to performance".

Lowkey status reports are the norm now :)

"some users may experience degraded service" => site completely down for all locations

I fully expect that if I find a "major outage" on Slack's status page that it could only mean the outbreak of nuclear war.

"Some users may experience brief service disruption."

"By the account of them and us being completely vaporized"

I was going to link the appropriate XKCD where organised attackers are panicing as they realise they're dealing with a sysadmin muttering about uptime..

.. but of course XKCD is down too.

e: https://xkcd.com/705/

"Only the last couple seconds of their lives."

Or the AWS typical status of ‘seeing increased error rates on the API’ = us-east-1 is dead

At least that's accurate. "Degraded performance" would imply to me that things are functional, but slow. increased error rates can be anything from "try again" to ":shrug:"

"We're investigating reports of intermittent connectivity issues" => transatlantic cables cut, WWIII imminent

Well to be fair some users were not accessing the site at that time

Yeah, that's my experience as well. I thought it meant "we have no idea what's going on" though.

Yeah, I also wrote a bot that chooses to create a status incident with the lowest key neutral message when it detects continued healthcheck fails (outside of maintenance) that steps in if an operator hasn't already created an incident. Maybe they're too busy fixing.

Yes, I also thought the header was hilarious:

> CDN Performance Impact

No issues reported for Perth Australia. Strange because reddit, zip pay, fastly itself, and probably a bunch of other sites are down.

Doesn't seem the status page is automatically updated or perhaps whatever event or polling is used is also broken.

Im experiencing the outage here in brissy its not looking good

In Adelaide, experiencing the outage as well.

> This incident affects: North America (Ashburn (BWI), Ashburn (DCA)).

How come we are affected by this in the Netherlands?

They've updated it to

>North America (Ashburn (BWI), Ashburn (DCA), Ashburn (IAD)), Europe (Amsterdam (AMS)), and Asia/Pacific (Hong Kong (HKG), Tokyo (TYO), Singapore (QPG)).

MAD affected, not on the list. I assume it is all locations.

I've seen errors return to me referencing a LON (London I assume) server - Details: cache-lon4238-LON for example

Auckland (AKL) is affected but not on the list.

Seems like they are still taking stock of exactly what is broken.

It has now been updated to a pretty sizable list.

edit: And now it looks like it includes every location.

Currently only listing a small issue in NA