Your site went down at night. What AICOMBase shows you.
From the first failed check to the recovery: how incidents, alerts and timelines work, and why outside monitoring matters even when nobody is working on the site.
3 min read · For every site owner · Illustrative example
The timeline
- 03:12 — the check from outside gets an HTTP 503. One failed check isn’t an incident yet — it could be a blip.
- 03:14 — the following checks fail too: an incident opens, the site turns red in the overview and in “Needs you”, and you’re notified.
- 03:15 — the AICOM heartbeat is also missing, so it’s the whole server, not just one page.
- 07:40 — the host fixes the server. Checks pass, the incident closes by itself with its full timeline.
Why outside checks matter
A plugin inside a broken site can’t report that the site is broken. AICOMBase checks from the outside — availability, response time, SSL — so you know even when the site itself can’t tell you.