All systems operational.
We publish the state of every channel and the API, including incidents that come from the provider and not from us. If something is degraded, you find out here before opening a ticket.
Availability measured on the send API, per the SLA clause in the contract.
The last 90 days, component by component.
Each bar is a day. Click a component to see the history and the nature of the events — including when the cause was the channel provider, which is not counted in our SLA measurement.
Every incident is logged, including the ones that weren't our fault.
We publish what happened, the real impact, the cause and what changed to prevent a repeat. A channel-provider incident is labeled as such — it's information you need, even when it's not our contractual responsibility.
You don't find out about an incident from a customer complaint.
This page is updated during the event, not after. Subscribers get opening, updates and closure by email — and the dashboard shows a banner for affected teams.
Report a problem →An internal alarm opens the incident here and places a banner on the dashboard of affected teams.
Email to subscribers with what is known, the observed impact and the next expected update.
While the event lasts, we publish progress even when the news is that there is still no fix.
Cause, measured impact and what changed to prevent a repeat — published on this page.
Start today with R$ 50 in test credit.
Sandbox wallet released when you create the account, a WhatsApp test number and guided onboarding. No card, no contract.
