Live operations

System status

Checking…

Live health of the after-hours answering, escalation, and paging engine. This page refreshes every 30 seconds; no account or sign-in is needed.

Call answering	checking Inbound calls reached the dispatcher and captured the job.
Escalation clock	checking The ladder advances on a one-minute sweep.
Voice and email paging	checking Automated calls and email go to the on-call technician and the owner.
SMS paging	limited Carrier registration for application-to-person texting is in progress. Until it clears, pages go by voice and email, and SMS resumes automatically after approval.
Durable ticket store	checking Tickets, acknowledgments, and billing evidence survive restarts.
Off-machine backup	daily A full JSON copy is emailed to the owner every morning at 08:00 UTC.
Independent watchdog	every 5 min A separate system checks this engine from its own runtime and pages the owner if it stops.

Recent incidents

No incidents recorded.

How status is determined

The engine writes a heartbeat on every minute sweep. If that heartbeat is more than ten minutes old, this page shows an outage and the owner is paged automatically by SMS, voice, and email. A second, independent watchdog project checks the same health endpoint from its own runtime, so a broken deployment cannot hide behind a slow reply.

This page reports engine health only. A single carrier, handset, or mailbox issue can delay one message even while the engine is healthy; those failures are recorded per attempt and visible to the operator.