Service status
What we can honestly tell you about the service right now, and what we cannot.
Right now
Waiting for the API to answer.
This check runs in your browser and asks the API whether it can reach the things it needs. It is a reading of one moment, taken when you loaded this page.
Sending and the API
Accepting messages, running campaigns, and answering API calls.
Records
Your accounts, your message history, and the queue of what is waiting to go out.
Pacing and live updates
The gap kept between one message and the next, and the updates that reach the dashboard without a reload.
This website
You are reading a page it served, so it reached you. That says nothing about the API: a signed-in dashboard needs both.
Your WhatsApp connection
Each linked number connects on its own and can drop while everything here is working. There is no single connection for us to report, so this page does not pretend to have one. Your dashboard shows the state of each of your numbers.
This check only ever sees the path from your browser to us. A green reading means that path worked at that moment, and nothing about anybody else's.
What it means when a check fails
If sending and the API are not reachable
New messages are refused at the moment you send them, with an error, rather than accepted and quietly dropped. Messages you had already submitted stay in the queue and go out once the service recovers. Scheduled sends and campaigns run late rather than being skipped. Nothing is deleted by an outage: your contacts, your history, your API keys, and your webhook addresses are all still there afterwards.
What to do: wait, and send again once this page reports the API reachable. A send that came back as an error was never accepted, so sending it again will not produce a duplicate.
If pacing and live updates are not reachable
Sending slows down or pauses, because the gap this service keeps between messages is tracked there, and sending without it would look to WhatsApp like the behaviour that gets numbers blocked. The dashboard also stops updating on its own, so you have to reload to see new messages. Nothing is lost: the queue is held with the records and drains when this comes back.
If this website is not reachable
You would not be reading this page. The website and the API are served separately, so the API can keep sending your queued messages while the site is down, and the site can stay up while the API is not.
If one of your WhatsApp numbers disconnects
This is the failure most likely to reach you, and it is the one this page cannot see. A number drops when the phone has been offline too long, when the device is removed from the linked devices list, or when WhatsApp interrupts the link on its own. A new send for that number is refused with an error naming the account, and a message already queued for it is retried rather than discarded. Open the accounts screen in your dashboard and link the number again by scanning a fresh code.
If the check itself cannot run
A blocked request, a browser with no network, and a check that times out are not outages, and this page does not draw them as one. Nothing was measured in any of those cases, so the row says no answer rather than not reachable. An extension, a company proxy, a captive portal on public wifi, or a filtered connection can all stop this one request while the service itself is running normally. The test that settles it is your dashboard: if it loads and a message sends, the service is working.
What this page does not claim
There is no uptime history here, because we do not have one. A row of green squares for days nobody recorded would look like evidence and be nothing of the kind.
To publish history honestly we would need a recorder outside this service, checking from somewhere that stays up when we do not, keeping every result with the time it was taken, and a written rule for what counts as an outage. Until that exists and has run long enough to be worth reading, this page reports the current moment and nothing more.
If something looks wrong
Tell us what you saw and when it happened. Include the account, and the message id or the error code you got back if you have one.
Write to [email protected] or use the contact page. Email reaches us even when the rest of the service does not.