System status

Status page in progress.

Hooks does not publish a live uptime dashboard yet. This page states what we would monitor, how we would measure it, and which signals you can check yourself. It intentionally shows no estimated, sample, or historical availability numbers.

Monitoring coverage

No automated probe is connected to this page yet. The planned probes and their reporting rules are listed below.

No probe data yet
Ingress API (/in/*)
Current signal: Support reports only.
Planned method: Signed synthetic request from three regions.
Frequency: Every 60 seconds; window: 30-day rolling; basis: 2xx probe responses ÷ scheduled probes; planned maintenance excluded.
Delivery pipeline (queue to destination)
Current signal: Support reports only.
Planned method: Synthetic event delivered to an internal probe destination.
Frequency: Every 5 minutes; window: 30-day rolling; basis: Probe deliveries accepted ÷ probe events queued.
Console, REST API and MCP
Current signal: Support reports only.
Planned method: Authenticated metrics read from two regions.
Frequency: Every 5 minutes; window: 30-day rolling; basis: 2xx probe responses ÷ scheduled probes.

Last reviewed and updated: 2026-11-08. No probe results exist yet, so no uptime percentage is published.

What you can verify today

Per-workspace delivery data is measured, not illustrative, and stays available for up to 90 days.

Delivery success rate and latency
The console shows accepted events, delivery outcomes and latency percentiles for your workspace. The same data is available from GET /v1/metrics.
Metrics API
Per-attempt delivery log
Every attempt records its response status, response time and error, so a failed delivery can be traced end to end.
Open console
Published hard limits
Body size, retention, retry schedule, timeouts and quotas are documented limits, not availability estimates.
Limits reference

Reporting an incident

If something looks wrong, contact us and we will look into it.

Email support
support@hooks.events
Replies within one business day. Include the event ID (or X-Hooks-Event header), the time window, and the destination ID; never include signing secrets or API keys.
We do not run a public incident feed. We reply with what we have verified and do not publish unverified numbers.
Send an email