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
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.
James Barnes
Share this
More from StatusCake
AI Didn’t Kill the SDLC. It Made It Harder to See
10 min read Whilst AI has compressed the visible stages of software delivery; requirements, validation, review and release discipline have not disappeared. They have been pushed into automation, runtime and governance. The real risk is not that the lifecycle is dead, but that organisations start acting as if accountability died with it. There is a now-familiar story about
James Barnes
April 2, 2026
When Code Becomes Cheap: The New Reliability Constraint in Software Engineering
4 min read How AI Is Shifting Software Engineering’s Primary Constraint For most of the history of software engineering, the primary constraint was production. Code was expensive, skilled engineers were scarce, and shipping features required concentrated human effort. Velocity was limited by how fast people could reason, implement, test, and deploy. That constraint shaped everything from team size,
James Barnes
March 25, 2026
Buy vs Build in the Age of AI (Part 3)
5 min read Autonomous Code, Trust Boundaries, and Why Governance Now Matters More Than Ever In Part 1, we looked at how AI has reduced the cost of building monitoring tools. Then in Part 2, we explored the operational and economic burden of owning them. Now we need to talk about something deeper. Because the real shift isn’t
James Barnes
March 18, 2026
Buy vs Build in the Age of AI (Part 2)
6 min read The Real Cost of Owning Monitoring Isn’t Code — It’s Everything Else In Part 1, we explored how AI has dramatically reduced the cost of building monitoring tooling. That much is clear. You can scaffold uptime checks quickly, generate alert logic in minutes, and set-up dashboards faster than most teams used to schedule the kickoff
James Barnes
March 11, 2026
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