Wati Outage History

The performance issue affecting live.wati.io has been resolved, and all services are now operating normally. Messaging and core functionalities have fully recovered. Our team will continue monitoring the platform to ensure stability. Thank you for your patience and understanding.

We experienced a service disruption between 3:40 PM – 5:20 PM HKT (now resolved) that affected message delivery across all WhatsApp Business Accounts on Meta's platform. You may have seen this error: (#200) You do not have the necessary permission to send messages on behalf of this WhatsApp Business Account. What you need to do : Resend any messages that failed during the outage—they should go through now. We're working closely with Meta to prevent this from happening again. Thanks for bearing with us.

Between 15:36–15:46 HKT on July 8, two of our three database secondaries experienced high CPU load due to an inefficient query pattern from an automated batch job checking for duplicate broadcast names across multiple accounts. This did not affect the primary node or write operations. Read performance may have been briefly degraded for some customers during this window. Root cause identified, and we're working on a fix: optimizing the query and adding a database index to prevent recurrence. We apologize for the inconvenience caused and thank you for your continued support. Thank you, Wati Team

All components are Operational

We experienced degraded performance around ~30 minutes due to the recent deployment. We've rolled back to the stable version, and we see the performance is now back to normal. We apologize for the inconvenience caused.

The previous disruption on the Meta side has now been resolved, and the services are now back to normal.

The latency issues have been resolved, and all systems are now fully operational. Our team is performing a thorough post-mortem to identify root causes and prevent recurrence. We sincerely apologize for any disruption this caused to you and your business.

Hi All, We would like to inform you that the template submission issue has now been resolved. The incident occurred due to a recent change from Meta. As an immediate measure, we have implemented a temporary hotfix that has successfully restored normal functionality. Our team is currently working on a long-term solution to ensure this does not recur. We sincerely apologize for the inconvenience caused and appreciate your understanding and patience. - WATI

The previous issue affecting login and core services has been fully resolved. The issue was caused by a backend infrastructure component reaching its capacity limit due to an accumulation of internal processing records. This temporarily prevented several platform services from operating normally. We sincerely apologize for the inconvenience caused by this service disruption. We understand how important uninterrupted access to Wati is for your business operations. Our team is committed to implementing the preventive measures outlined above to ensure a more reliable experience going forward. If you have any questions or concerns, please do not hesitate to reach out to our support team.

Meta has confirmed that the previous issue affecting the onboarding flow has been fully resolved, and all systems are now operating normally. If you previously faced issues with connecting a number, Instagram, or Messenger, please try again now. We apologize for any inconvenience that this may have caused.

The issue affecting payment checkout has been fully resolved, and all systems are now operating normally. We've also receive confirmation from our payment gateway service provider that they have concluded that the incident has been fully resolved. Our team is conducting a full post-mortem analysis along with our vendor to prevent this from happening again. We sincerely apologize for the impact this had on you and your business.

Users attempting to authenticate with API docs tokens encountered 403 Forbidden errors around 9:55 AM - 10:50 AM HKT. The issue was caused by an integration failure between the services responsible for the security update that should allow old active tokens generated before February 2026 to remain active. (You can read more about the security update here .) We quickly rolled back the problematic deployment to avoid further impact, and it resolved the issue. We remain committed to improving the system and preventing similar issues in the future. Thank you for your continued support.

The issue affecting Multi WhatsApp number and some other services has been fully resolved, and all systems are now operating normally. Summary of the Event: Between 9:30 AM HKT and 4:20 PM HKT some customers with certain features like Multi WhatsApp number may have experienced issue with their Team Inbox The incident was caused by issue with the feature controllers. Our team is conducting a full post-mortem analysis to prevent this from happening again. We sincerely apologize for the impact this had on you and your business.

We have confirmed that the CPU utilization is now back to normal and all component and services are now working as expected.

The issue is now resolved, and all services are operational.