Want to know how much website downtime costs, and the impact it can have on your business?
Find out everything you need to know in our new uptime monitoring whitepaper 2021
We have to admit that customers and brands alike are able to put a good spin on website downtime and social media managers are undoubtedly having all their Christmases arrive at once! We’ve found some of the most reactions to website downtime online, albeit the majority are from the notorious Facebook, Instagram and WhatsApp downtime experienced globally.
Feel free to actually LOL.
When Instagram and Facebook experienced downtime
It’s safe to say that a common theme for people expressing their thoughts on this downtime on Twitter was using Squid Game memes.
Twitter’s famous Tweet
Twitter went viral for all the right reasons when its rival social media platforms with a simple yet genius Tweet below:
This one Tweet became one of their best performing Tweets ever and got some other world-famous companies involved, ironically including Instagram!
An unlikely brand to get involved in the Facebook downtime is Mercedes! The F1 Twitter account posted this hilarity. We can’t help wondering if it was Max Verstappen behind this one.
Universal Studios Hollywood smashed it by sneakily making it about themselves. Everyone loves Gru, don’t they?
It’s unusual for companies to take such a damaging experience like website downtime and manage to put a positive spin on it. With Instagram suffering from its app being down and jumping on Twitter, it shows that they’re able to turn this incident on its head and at least engage with some of its users.
What is the impact of website downtime?
Well ultimately, it’s not just Facebook and Instagram as companies that are affected, all of the companies that rely on ads on those platforms will also suffer revenue loss. And we’re talking millions upon millions of dollars even for a few minutes of website downtime.
What causes website downtime?
Facebook and Instagram have suffered from multiple outages over the past 12 months and people are starting to question if they’re going to manage to get a hold of whatever issue is causing this to happen so regularly. In general, website downtime can be caused from many different things including server issues, page load issues, human error, network outages and more.
Maybe Facebook and Instagram should use StatusCake’s website monitoring solution? 😉
StatusCake Team
Share this
More from StatusCake
Designing Alerts for Action
3 min read In the first two posts of this series, we explored how alert noise emerges from design decisions, and why notification lists fail to create accountability when responsibility is unclear. There’s a deeper issue underneath both of those problems. Many alerting systems are designed without being clear about the outcome they’re meant to produce. When teams
James Barnes
February 18, 2026
A Notification List Is Not a Team
3 min read In the previous post, we looked at how alert noise is rarely accidental. It’s usually the result of sensible decisions layered over time, until responsibility becomes diffuse and response slows. One of the most persistent assumptions behind this pattern is simple. If enough people are notified, someone will take responsibility. After more than fourteen years
James Barnes
February 11, 2026
Alert Noise Isn’t an Accident — It’s a Design Decision
3 min read In a previous post, The Incident Checklist: Reducing Cognitive Load When It Matters Most, we explored how incidents stop being purely technical problems and become human ones. These are moments where decision-making under pressure and cognitive load matter more than perfect root cause analysis. When systems don’t support people clearly in those moments, teams compensate.
James Barnes
February 4, 2026
The Incident Checklist: Reducing Cognitive Load When It Matters Most
4 min read In the previous post, we looked at what happens after detection; when incidents stop being purely technical problems and become human ones, with cognitive load as the real constraint. This post assumes that context. The question here is simpler and more practical. What actually helps teams think clearly and act well once things are already
James Barnes
January 28, 2026
When Things Go Wrong, Systems Should Help Humans — Not Fight Them
3 min read In the previous post, we explored how AI accelerates delivery and compresses the time between change and user impact. As velocity increases, knowing that something has gone wrong before users do becomes a critical capability. But detection is only the beginning. Once alerts fire and dashboards light up, humans still have to interpret what’s happening,
James Barnes
January 21, 2026
When AI Speeds Up Change, Knowing First Becomes the Constraint
5 min read In a recent post, I argued that AI doesn’t fix weak engineering processes; rather it amplifies them. Strong review practices, clear ownership, and solid fundamentals still matter just as much when code is AI-assisted as when it’s not. That post sparked a follow-up question in the comments that’s worth sitting with: With AI speeding things
James Barnes
January 14, 2026