Is WaAPI down?
This page reads the live state of our delivery fleet. It is generated on request, not maintained by hand.
All systems operational
The delivery fleet is reporting in normally.
- Checked
- 13 Aug 2026, 19:33:45 UTC
- Last heartbeat received
- 13 Aug 2026, 19:33:45 UTC
This indicator covers the fleet that sends and receives messages. Because you are reading this page, the website itself — including sign-in and the dashboard — is reachable from where you are.
Everything is green but it still is not working
Most reports that reach us during a green window are one of the three below. They look identical from the outside and have completely different fixes.
You cannot sign in
This is your account on this website, and it is separate from any connected account. If the password is refused, reset it — if the reset mail does not arrive, check the spam folder before writing in, because that is where it usually is.
Reset your passwordAn instance went back to the QR screen
The linked device was signed out — usually from the phone, or after the phone was offline for a long stretch. The platform cannot re-link on your behalf; scan the code once and the session resumes.
Keeping a session aliveMessages are accepted but never arrive
A restriction on the sending number looks exactly like an outage from your side: the API returns success and nothing is delivered. Sending speed and cold recipients are the usual causes.
Restrictions and how to lift themStatus questions
What this page does and does not tell you.
-
It is generated when you load it. Nodes report in every 15 seconds, and anything that has not reported for two minutes counts as unhealthy, so a real problem shows up here within roughly two minutes of starting.
-
The fleet that sends and receives messages. It does not separately measure billing, the dashboard or third-party services we depend on. If the page renders at all, the website and sign-in are reachable.
-
Those are different things. The fleet can be perfectly healthy while one linked device has been signed out — reconnect the instance from your dashboard by scanning the code again.
-
That is almost never an outage. It usually means the sending number is under a restriction, which the API cannot see at send time. Slow down to at least 15 seconds between messages, warm new numbers up gradually and never message cold lists.
-
Trust what you are seeing and open a support ticket. The indicator is honest about the fleet but it cannot detect every failure mode, and it deliberately shows an unknown state rather than guessing.
Still stuck?
Support tickets go to the people who run the platform, not to a queue.
Open a support ticket