Two paths through the same incident.
Without the Doppelgänger
- 1
Over months
Log files and old backups fill up the storage space.
- 2
Saturday night
It is full. The database can no longer write, and orders and forms fail, some without any visible error message.
- 3
Monday noon
Someone notices when the order emails stop coming in.
With the Doppelgänger
- 1
Every night
The nightly server check reports low disk space before the disk is full.
- 2
Immediately
If the website goes down anyway, uptime monitoring reports it immediately.
An update alone is not enough: for almost half of all WordPress vulnerabilities there is no patch yet when they are published. That is why nightly monitoring is part of it.
What the incident costs.
More case studies
The host switches PHP versions
The host raised the PHP version. For three days the home page looked empty.
The checkout that is only broken sometimes
For three weeks, not a single purchase on invoice went through in the store for wholesale customers. The main store worked perfectly.
The agency was on the server
For a promotion, an outside agency changed files directly on the server. With the next update, the promotion was gone.
A typical course of events, assembled from real incidents. Figures are example calculations based on the stated assumptions.