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
You might have heard us say it before but downtime really does happen to any website, anywhere. Website downtime essentially doesn’t discriminate; it doesn’t matter if you’re a huge multi-billion dollar company or if you’re a start-up finding your feet in the online world. Downtime happens to the best of us.
So to really drive this point home, we’ve put together the websites that have suffered downtime this June and how they dealt with the issue.
Facebook Messenger
Unfortunately for Facebook, it seems to be a regular on our “website downtime” blog series. This time it was a short-lived outage that affected the messenger feature with DownDetector reporting around 2,000 users with issues at around 4pm UK time on July 5th 2022. We have no insight into what caused the issue but we must say it was dealt with quickly and efficiently which customers reacted to well.
On 14th July 2022, Twitter suffered one of its longest outages in its history with an hour-long downtime. Over 30,000 reports were issued to DownDetector as the social media giant struggled to rectify the issue promptly. The worst part? It seemed to be an international outage as opposed to a country or continent specific outage.
Twitter issued a statement saying the following:
“Some of you are having issues accessing Twitter – and we’re working to get it back up and running for everyone. Thanks for sticking with us.”
Much like Facebook, it’s not unusual for Twitter to feature on the website downtime list. There’s many reasons for this – too much pressure on the servers caused by an influx of traffic or users, for example. Hmm, if only there was a server monitoring solution they could use?
Netflix
Streaming giant Netflix suffered an outage on July 15th 2022 with DownDetector noting 4,000 reports of issues from their customers. At first, it seemed to only be a minor outage which wasn’t worldwide spread with customers based in India affected the most. But soon there was plenty of UK-based customers that seemed to be experiencing the same thing – the dreaded 500 error message.
The issue seemed to be fixed within a very short period of time with users Tweeting that they could access their accounts soon after reporting the issue.
Much like its social media friend Facebook, Instagram is a regular website on our list suffering downtime very regularly. As a prime example of this, in the month of July alone, Instagram went down twice.
On July 22nd 2022, Twitter suffered a full outage after suffering an issue with their photo app a week prior. The worst part? Their users took to social rival Twitter to complain about the issues with logging into the platform.
This seemed to be a prolonged outage for Instagram, causing a bigger ripple across its users with the hashtag #instagramdown trending.
StatusCake Team
Share this
More from StatusCake
Engineering
Beyond Uptime: Building a Self-Healing OpenClaw Observability Stack
3 min read The allure of OpenClaw is undeniable. You deploy a highly autonomous, self-hosted AI agent, give it access to your repositories and inboxes, and watch it reason through complex workflows while you sleep. It is the dream of the ultimate 10x developer tool realized. But as any veteran DevOps engineer will tell you: running an LLM-backed
Daniel
April 23, 2026
When AWS us-east-1 Fails, Much of the Internet Fails With It
7 min read There are cloud outages, and then there are us-east-1 outages. That distinction matters because failures in AWS’s Northern Virginia region rarely feel like ordinary regional incidents. They tend instead to expose something larger and more uncomfortable: too much of the modern internet still behaves as though one place is an acceptable concentration point for infrastructure,
James Barnes
April 15, 2026
In the Age of AI, Operational Memory Matters Most During Incidents
7 min read Artificial intelligence is making software easier to produce. That much is already obvious. Code that once took hours to scaffold can now be drafted in minutes. Boilerplate, integration logic, tests, refactors and small internal tools can be generated with startling speed. In some cases, even substantial pieces of implementation can be assembled quickly enough to
James Barnes
April 10, 2026
AI Didn’t Kill the SDLC. It Made It Harder to See
10 min read Whilst AI has compressed the visible stages of software delivery; requirements, validation, review and release discipline have not disappeared. They have been pushed into automation, runtime and governance. The real risk is not that the lifecycle is dead, but that organisations start acting as if accountability died with it. There is a now-familiar story about
James Barnes
April 2, 2026
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