All systems operational
Updated every minute · last check
Components
- Operational
- Degraded
- Outage
- No data
- Operational
REST API
Answered in 79 ms.
9030 days agoToday62 ms p50 today
99.95% uptime · 90 days
How this is measured
api.wuapi.dev, measured with a GET /health every minute.
Degraded: 1 failed check, or a response slower than 1500 ms.
Outage: 3 failed checks in a row.
Uptime is the share of the day's checks that passed. A day with no checks has no bar color.
- Operational
WhatsApp engine
Every engine worker is reporting in.
9030 days agoToday6 ms p50 today
99.80% uptime · 90 days
How this is measured
The service that holds the linked-device sessions, measured with a GET /health every minute.
Degraded: 1 failed check, or a response slower than 2000 ms.
Outage: 3 failed checks in a row.
Uptime is the share of the day's checks that passed. A day with no checks has no bar color.
- Operational
Webhook delivery
100% of first attempts succeeded in the last 15 minutes; 0% of endpoints failing.
9030 days agoToday100% of first attempts succeeded · last 15 min
100% uptime · 90 days
How this is measured
First delivery attempts to customer endpoints over the last 15 minutes, counted per endpoint.
Degraded: 25% of endpoints failing (at least 3), or deliveries waiting more than 2 minutes for a first attempt.
Outage: 50% of endpoints failing (at least 3), or half of all deliveries (at least 10) waiting for a first attempt.
An endpoint with no successful delivery in the previous 24 hours is not counted.
Uptime is the share of the day's checks that passed. A day with no checks has no bar color.
- Operational
Sending
100% of sends reached WhatsApp in the last 15 minutes.
9030 days agoToday100% of sends reached WhatsApp · last 15 min
99.25% uptime · 90 days
How this is measured
Outbound sends over the last 15 minutes that reached WhatsApp, against failures on our side.
Degraded: 5% of sends failing on our side (at least 3).
Outage: 50% of sends failing on our side (at least 3).
Not counted: recipients not on WhatsApp, rejected requests, and sends waiting for their pace.
Uptime is the share of the day's checks that passed. A day with no checks has no bar color.
- Operational
Dashboard
Answered in 74 ms.
9030 days agoToday74 ms last check
96.00% uptime · 90 days
How this is measured
wuapi.dev, measured with a GET every minute.
Degraded: 1 failed check, or a response slower than 3000 ms.
Outage: 3 failed checks in a row.
Uptime is the share of the day's checks that passed. A day with no checks has no bar color.
Past incidents · 30 days
Outage: SendingSep 26, 21:55 UTC · lasted 7 min · Sending · automaticmajor impact
resolved/
Resolved automatically: 5 checks in a row passed.
investigating/
Opened automatically: 3 checks in a row found Sending outage. 25% of sends reached WhatsApp in the last 15 minutes.
Degraded SendingSep 25, 20:04 UTC · lasted 17 min · Sending · automaticminor impact
resolved/
Resolved automatically: 5 checks in a row passed.
investigating/
Opened automatically: 3 checks in a row found Sending degraded. 71.4% of sends reached WhatsApp in the last 15 minutes.
Degraded SendingSep 25, 17:03 UTC · lasted 19 min · Sending · automaticminor impact
resolved/
Resolved automatically: 5 checks in a row passed.
investigating/
Opened automatically: 3 checks in a row found Sending degraded. 77.4% of sends reached WhatsApp in the last 15 minutes.
Outage: DashboardSep 25, 01:09 UTC · lasted 2 h 49 min · Dashboard · automaticmajor impact
resolved/
Resolved automatically: 5 checks in a row passed.
investigating/
Opened automatically: 3 checks in a row found Dashboard outage. The request could not connect.
Outage: WhatsApp engineSep 25, 01:02 UTC · lasted 15 min · WhatsApp engine · automaticmajor impact
resolved/
Resolved automatically: 5 checks in a row passed.
investigating/
Opened automatically: 3 checks in a row found WhatsApp engine outage. The request could not connect.