Monitoring
Status Pages
Pricing
Virgin Money Giving experienced a website crash during the London Marathon, and that crash was both embarrassing and costly. In the short term, the crash prevented people from providing support to the marathon participants promptly. In the long term, Virgin has taken a hit in brand reputation that may take a while to recover from.
Of course, Virgin is not the only organization to fall victim to website crashes or slowdown. During Black Friday last year, many large online retailers suffered the same fate. Even a degradation in site loading time can have detrimental effects as serious as a website crash. Customers will abandon a site that is slow to load and take their business elsewhere, and search engines will downgrade the ranking of sites that have a track record of frequent crashes or slow loading time.
You need to be proactive to keep your site up and running. Here are four steps that you should take:
Most businesses know when they will experience peak traffic based on previous experience. If you are on online retailer, you know what volume you experienced on previous peak days such as Black Friday, and this should be your starting point for planning for how much traffic your site should be capable of handling to allow for a major spike in traffic.
Once you determine the peak traffic flow that you wish to accommodate, identify any bottlenecks on your website that might prevent you from handling it. Then, load test each to see if any of them fail, and make appropriate changes to eliminate those bottlenecks. Be sure to do this well in advance of when you expect your peak traffic to hit.
After evaluating the individual potential bottlenecks, conduct a complete load and stress test on your site and apps using the maximum anticipated amount of traffic plus an additional amount of traffic to give you a margin of safety. A complete professional load test will simulate peak traffic amounts easily and quickly and will show you exactly what failed if your site does not pass the test. Once your site passes the final check, you can be confident that your site is ready.
Sometimes, circumstances beyond your control can thwart even the most comprehensive plan, and your site will still crash. Therefore, it’s best to have a plan to help mitigate the damage if your site does go down. Consider using a website monitoring service so that you will know promptly if your site does crash. Prepare a communications plan so that you can inform your visitors and customers why your site went down, what steps you are taking to get the site back online, and how long you expect it will take for you to resume normal operations.
When your website goes down, it’s the equivalent of a brick-and-mortar store locking its front door. Taking steps to keep your website up and running during peak traffic flows is crucial in maintaining your reputation and keeping your customers from going elsewhere.
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
