Wati incident

Platform Stability Issue

Minor Resolved View vendor source →

Wati experienced a minor incident on July 8, 2026, lasting 30m. The incident has been resolved; the full update timeline is below.

Started
Jul 08, 2026, 07:49 AM UTC
Resolved
Jul 08, 2026, 08:19 AM UTC
Duration
30m
Detected by Pingoru
Jul 08, 2026, 07:49 AM UTC

Update timeline

  1. investigating Jul 08, 2026, 07:49 AM UTC

    We're currently experiencing degraded performance on the live.wati.io domain. Our team is currently investigating and working to resolve the issue as soon as possible. Thank you for your extended patience.

  2. monitoring Jul 08, 2026, 08:18 AM UTC

    The performance is now back to normal. Our team is still investigating the root cause of the issue. We will share another update once we have more details on this issue.

  3. resolved Jul 08, 2026, 08:19 AM UTC

    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