Monitoring
Status Pages
Pricing
Website maintenance is important because as good as you may have coded your website or however good the infrastructure they’re hosted on.
By carrying out maintenance at regular intervals over short periods of time you’d hope that this helps ensure that major, unexpected issues don’t rear their ugly heads. Maintenance on your terms and at a time of your choosing is absolutely preferable to your website doing down and you having to carry out unplanned maintenance.
Planned maintenance is time you set aside, and by its very definition, have planned in advance to makes changes to your website or server. During these short periods of maintenance you may need to make certain parts of your website inaccessible, but you should always try if you can avoid it.
In the case of planned website maintenance just try where possible, let people know in advance that it’s going to be happening; particularly if popular features or aspects of the website that people rely on are going to be inaccessible.
When informing customers of the planned maintenance give them a heads up of the extent of the disruption. Give yourself enough time to get your maintenance done before customers come flocking back expecting a full website service to have resumed.
As well as telling your “human” visitors you also need to make sure that the search engine crawlers know that your site being down is just temporary. You can do this by utilizing an HTTP status code “503 Service Unavailable.” This status informs the search engines that the downtime is only temporary and that they should come back later.
If you need help in setting up maintenance windows within your StatusCake account then please don’t hesitate to contact one of the StatusCake team by email or Live-Chat.
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
