Monitoring
Status Pages
Pricing
Well, 2016 has been another banner year for major website crashes. Distributed denial of service (DDoS) attacks, such as the hugely disruptive one on Dyn, were on the rise, but many of these crashes were preventable. As in past years, the main culprit was inadequate preparation for an increase in traffic that was entirely predictable.
It is understandable that many new small businesses would not plan for traffic surges. However, just as in past years, large businesses and governmental agencies launched major campaigns that are guaranteed to generate huge increases in traffic and then found themselves the target of unrelenting negative publicity in the press and on social media when that increased traffic crashed their websites. As the late American baseball player Yogi Berra would say: “It’s déjà vu all over again.” Here are a just a few of the crashes that generated a lot of frustration.
Every major retailer knows that traffic on Black Friday will be off the charts as consumers chase the bargains that retailers had been previewing during the previous two weeks, so you would think they would be prepared. Unfortunately, some retailers were not. On Black Friday, the websites of the following companies crashed and/or experienced a severe degradation in service: Currys, PC World, Macy’s, Quidco (a cashback site), and GAME.
The negative reaction on social media was overwhelming. Frustrated customers vowed never again to shop at some of these retailers, and some helpfully posted links to competitors’ websites that were holding up just fine under the Black Friday onslaught.
Their poor performance on Black Friday hurt these firms in two ways. They lost an undetermined amount of sales to their competitors on the day because customers were unable to complete their purchases. Their reputation also suffered, causing them to lose future sales as well, Black Friday certainly was “black” for those firms, but for the wrong reasons.
Leading up to the voting on the EU referendum in June, voters were encouraged to register online. Traffic on gov.uk steadily increased during the week before the registration deadline and traffic eventually reached over 200,000 users per hour. The site could not handle the traffic spike and crashed on the registration deadline date, leaving many people unable to become eligible to vote.
Frustrated voters took to social media to vent their anger and demand an extension of the voting registration deadline. After the furor, the government agreed to extend the registration deadline by two days.
As you can see, when a website goes down, users of the site can get very frustrated. Websites can go down for many reasons, not just because of a traffic spike. Sometimes technical issues at your hosting company over which you have no control can be the cause. In any event, you need to know promptly if your site is down so you can take corrective action and keep customer dissatisfaction to a minimum; consider using a website monitoring service to get alerted fast.
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
