OmniSignal watchdog
Keeping tayaprowave.com online
A server-side watchdog probes tayaprowave.com continuously, retrying across request methods before it declares an outage. Every result is recorded, and a state change emails the operator immediately — even when browser notifications are blocked.
- Uptime 24 h
- 0.00%
- Uptime (window)
- 0.00%
- Avg response
- —
- Incident state
- Healthy
Failing streak 0 · slow streak 0 · outage declared at 3 failures, degraded at 3 probes over 3000 ms.
Outage thresholds
Alerts after 3 failed probes in a row, or 3 probes slower than 3000 ms, with a 15-minute cooldown. Single blips and one-off slow responses stay in the log without paging anyone.
Escalation — repeat reminders
While an incident stays open you are re-notified every 30 min, up to 5 times, until the site recovers. Reminders stop the moment tayaprowave.com recovers, and a recovery notice always goes out.
Alert channels
EmailEmail always pages on a state change. SMS and Slack fire alongside it, each independently — one channel failing never blocks the others.
Use full international format starting with +.
The alert bot must be invited to this channel before it can post.
Sends JSON {type:"uptime.state_change", state, status_code, latency_ms, detail, occurred_at, thresholds} on every state change and reminder. With a secret set, each request carries X-OmniSignal-Signature: sha256=<HMAC of the raw body>.
Response time
Oldest to newest, last 0 probes. Red bars are failed probes.
Waiting for the first probe…
Probe log
| Time | Result | Code | Latency | Source | Detail |
|---|---|---|---|---|---|
| No probes yet — run a check to start the history. | |||||
For 24/7 coverage without this page open, point any scheduler at /api/public/uptime-check — each call runs one full watchdog cycle and alerts on state change.