The problem
A site can return HTTP 200 while showing a cached error, a security challenge, or an unusable page. Agencies also need to know who to notify and what happened before attempting recovery.
How the system fits together
AximWatch combines HTTP and keyword checks with TLS expiry monitoring, alerts, and incident context. Persistent downtime can trigger a controlled EC2 recovery action where the target is configured for it.
Decisions that matter
- Check the expected content as well as the HTTP status.
- Use sustained failures to distinguish transient interruptions from incidents that require action.
- Capture operational context so the team can review a recovery attempt and follow up.
Scope and evidence
This case study describes the documented project and its engineering approach. It does not imply independently measured business results or a service-level guarantee.
Discuss the architecture