i.e azure, aws or whatever, then yeah it will be a mess

Which I understand, and I'm going to go back to my previous point;

If it's something under their control, i.e. something in their codebase which has changed so suddenly some people can't upload - then the best thing to do would be roll back, or fail forward.

If it's out of their control, ...

Most of the companies out there that have been around for 20+ years have old code in their codebase which gets refactored, replaced over time. It's called maintaining a codebase

That can be either out of their control (regional CDN, storage etc) or it could be something under their control

Like I said elsewhere, if it's not something under their control then yeah it's a messy issue. If it is under their control, then it looks bad for them

I do understand that lol and that's why testing is done, both written, end to end, and manual testing

And the usual practice for that should be either roll back, or fail forward and deploy a fix asap, not offline the entire site for over 24 hours

Be that as it may, it shouldn't take 24+ hours to roll back to a working build or to deploy a fix. If this isn't due to a third-party like a storage provider (AWS S3 etc), then it doesn't shine FA in a good light as a for-profit company with ~44mil views a month

... As someone who does it professionally, and has done for years - this is why changes get tested in a separate environment before release to production, with the ability to roll back if something breaks.

That's if this is something in FA's own infrastructure

You're not allowed to say anything that isn't "awww get well soon" here or they'll just accuse you of being toxic

But yeah, the length of this outage is very bad reflection lol

Love it

That's understandable, it can be overwhelming. Don't be a stranger for too long, you still got friends dotted around who miss your antics

Where's my spicy ulveon gone?