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
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
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