Elevated TTS errors in Asia Pacific (Mumbai)

Resolved

Started

Lasted 3h 32m

View official incident ↗

Updates

  1. Resolved

    This incident has been resolved.

  2. Monitoring

    We have mitigated the issue on our end and are continuing to monitor the state of our service.

  3. Resolved

    From 21:51 PT on November 14 (05:51 UTC, November 15), an internal routing component lost its connection and did not reconnect automatically. As a result, a substantial portion of TTS requests in our Asia Pacific (Mumbai) region failed or responded slowly. We identified the issue and restored service at 22:03 PT (06:03 UTC), and error rates and latency have been normal since. We’re improving how this component recovers more gracefully from connection failures in the future.