Maintenance and troubleshooting

The scheduled work that prevents most incidents — updates, monitoring, backup verification — plus the investigation when something misbehaves intermittently and nobody can say why.

Prevention is cheaper than the incident

Nearly every emergency we get called into was preventable: an update that was never applied, a certificate nobody renewed, a backup that had been failing silently for months, or a disk quietly filling up. None of these are difficult problems. They are just problems nobody was looking for.

The other half of this work is the awkward category — the intermittent fault, the page that is slow only sometimes, the process that fails once a fortnight. That needs patient investigation with proper logging rather than guesswork, which is exactly the work that gets abandoned when nobody owns it.

What maintenance covers

Scheduled updates

Core, plugin and dependency updates applied on a cadence and checked afterwards, not applied blindly.

Monitoring

Uptime, performance and error monitoring so problems are found before your customers report them.

Backup verification

Backups tested by restoring them, because an untested backup is an assumption rather than a safeguard.

Fault investigation

Methodical diagnosis of intermittent and hard-to-reproduce problems, with findings written down.

Frequently Asked Questions

How often should updates be applied?

Security updates promptly; feature updates on a regular scheduled cadence with checks afterwards. Applying everything the moment it appears, without testing, is how sites break — but leaving updates for months is how they get compromised.

Are backups really necessary if our host takes them?

Host backups are a starting point, not a strategy. What matters is whether a restore has actually been tested, how far back the retention goes, and whether a copy exists somewhere independent of the host.

Can you find a fault that only happens occasionally?

Usually, though it takes patience and proper logging rather than guesswork. Intermittent faults are exactly the category that gets abandoned when nobody owns the system, which is why they persist for so long.

Tired of finding out when it breaks?

Tell us what you are running and when it last went wrong. We will suggest what maintenance would actually prevent.

Get in touch

Quick question? Send us a message.

Start a project

Tell us about your project. We’ll get back within 24 hours with a clear assessment and timeline.