Monitoring
Status Pages
Pricing
We get asked ALOT about the cause of website downtime, especially if it happens regularly. The answer is downtime can be caused by many different things depending on the size and set up of your website. Luckily with StatusCake, we can help you identify what has caused your downtime and what needs to be done to fix it!
Here’s just a few reasons why your website could go down:
•Network device faults
• Device configuration updates/developments
• Human error in the backend
• Network congestion
• Power outages
• Server hardware failure
• Security threats/attacks
• Failed software patches
We find that one of the most regular reasons for website downtime is problems with a customer’s server. Server issues are common and can easily go unnoticed until they cause the infamous downtime. But with our server monitoring tool, you can set alerts for when your server is exceeding its thresholds for disk, RAM, CPU usage so you can avoid this.
We’ve found that a lot of people don’t know that a surge in traffic to their website can also cause downtime, whether it’s partial downtime on a singular page like a payment page or full downtime meaning the entire website.
A classic example of this happening is on Black Friday; many more websites experience downtime during this period than at any other time in the year purely because of the extra amount of traffic hitting their site which puts too much pressure on it.
This is one of the leading causes of downtime and can cause even the world’s biggest websites to go down.
It is estimated that businesses lose 60 million hours a year due to website downtime caused by network outages. According to BMC Blogs, 92% of companies they surveyed who had experienced downtime reported financial losses from outages. This is something that StatusCake tries to drill into our customers; downtime really does cause a loss in revenue, as well as reputation and you truly can’t put a price on that.
If you make any big changes to your website, maybe you update the WordPress version you’re on for example, this can easily cause website downtime. Even simple things like removing plugins or 3rd party integrations you have can have a big impact that can end with partial or full downtime. The way around this is to always do back ups of your website before any updates, and to test/research how any changes could potentially negatively affect your site beforehand.
The majority of websites out there are using third party apps for a multitude of different things on their website. From payment applications to cloud applications, there’s always something extra running in the background which has the capability of causing website downtime. We’ve seen this happen plenty of times and the only way to ensure you’re on top of it is to use our uptime monitoring solution which will alert you within 30 seconds if your website has gone down!
Share this
4 min read On 13th August 2026, a storm knocked out cooling at RadiusDC’s Phoenix data centre, which hosted essential Namecheap operations. To protect hardware from thermal damage, Namecheap took services offline while temporary chillers were brought in. The incident and recovery ran for roughly 30 hours, with Namecheap’s own site unreachable for about 11 hours 42 minutes
3 min read On Wednesday 19 August, Monzo had an outage. DownDetector logged more than 3,000 reports by midday. Monzo’s own statement was direct about what it did next: it activated Monzo Stand-in, its fully independent backup bank, while it investigated an issue affecting customers. By the end of the day, Monzo said the issue was resolved and
3 min read GitHub’s incident on 17 August 2026 ran from 13:28 to 21:15 UTC, seven hours and forty-seven minutes. At peak, web and API traffic saw error rates of around 20%, while archive and raw-content downloads reached roughly 50%. SAML and OIDC authentication, SCIM and Team Sync were affected alongside Git operations, Actions, Pages, Issues, Pull Requests
3 min read Adding a new website, launching a customer portal, or handing a service to a new team should be straightforward. Setting up monitoring is part of that job, but it is easy for a manual step to be missed when information is spread across several systems. StatusCake now integrates with viaSocket, giving teams a way to connect
7 min read A website may be standing and still be in trouble. It may answer a request, return a cheerful 200 OK, and yet load slowly enough that visitors begin to lose patience. Its certificate may be nearing expiry. Its domain records may have changed. A server may be filling its disk in the background, patient and
6 min read StatusCake tells you that something might be broken. Hermes can check whether it really looks broken, decide who should hear about it, send the email, and keep the record for tomorrow morning’s summary.
Find out everything you need to know in our new uptime monitoring whitepaper 2021
