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
When Code Becomes Cheap: The New Reliability Constraint in Software Engineering
4 min read How AI Is Shifting Software Engineering’s Primary Constraint For most of the history of software engineering, the primary constraint was production. Code was expensive, skilled engineers were scarce, and shipping features required concentrated human effort. Velocity was limited by how fast people could reason, implement, test, and deploy. That constraint shaped everything from team size,
James Barnes
March 25, 2026
Buy vs Build in the Age of AI (Part 3)
5 min read Autonomous Code, Trust Boundaries, and Why Governance Now Matters More Than Ever In Part 1, we looked at how AI has reduced the cost of building monitoring tools. Then in Part 2, we explored the operational and economic burden of owning them. Now we need to talk about something deeper. Because the real shift isn’t
James Barnes
March 18, 2026
Buy vs Build in the Age of AI (Part 2)
6 min read The Real Cost of Owning Monitoring Isn’t Code — It’s Everything Else In Part 1, we explored how AI has dramatically reduced the cost of building monitoring tooling. That much is clear. You can scaffold uptime checks quickly, generate alert logic in minutes, and set-up dashboards faster than most teams used to schedule the kickoff
James Barnes
March 11, 2026
Buy vs Build in the Age of AI (Part 1)
5 min read AI Has Made Building Monitoring Easy. It Hasn’t Made Owning It Any Easier. A few months ago, I spoke to an engineering manager who proudly told me they had rebuilt their monitoring stack over a long weekend. They’d used AI to scaffold synthetic checks. They’d generated alert logic with dynamic thresholds. They’d then wired everything
James Barnes
March 4, 2026
Alerting Is a Socio-Technical System
3 min read In the previous posts, we’ve looked at how alert noise emerges from design decisions, why notification lists fail to create accountability, and why alerts only work when they’re designed around a clear outcome. Taken together, these ideas point to a broader conclusion. That alerting is not just a technical system, it’s a socio-technical one. Alerting
James Barnes
February 25, 2026
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