Ringotel incident

Ringotel Incident - India

Resolved after 6 hours 27 minutes, affecting India (Mumbai), on August 26, 2026.

resolved Aug 26, 2026, 09:40 PM UTC

This incident has been resolved and connectivity is fully restored. The problem was caused by an increase in error rates within a system component which resulted in a heap out-of-memory (OOM) error. This caused a temporary service interruption for organisations hosted in the India region. Our team is working on a solution to ensure that such incidents won't occur in the future. We appreciate your cooperation and apologise for any inconveniences caused by this issue.

Started
Aug 26, 2026, 03:13 PM UTC
Resolved
Aug 26, 2026, 09:40 PM UTC
Duration
6h 27m
Detected by Pingoru
Aug 26, 2026, 03:13 PM UTC

Affected components

India (Mumbai)

Update timeline

  1. investigating Aug 26, 2026, 03:13 PM UTC

    A new Ringotel incident has been automatically created in the affected region (India). Our team has been notified and will review it immediately. If you have any questions, please contact us at [email protected] or use the online chat / create a ticket. We appreciate your patience in the meantime.

  2. monitoring Aug 26, 2026, 04:18 PM UTC

    The incident has been resolved. Our team is monitoring the status and will provide an update shortly.

  3. resolved Aug 26, 2026, 09:40 PM UTC

    This incident has been resolved and connectivity is fully restored. The problem was caused by an increase in error rates within a system component which resulted in a heap out-of-memory (OOM) error. This caused a temporary service interruption for organisations hosted in the India region. Our team is working on a solution to ensure that such incidents won't occur in the future. We appreciate your cooperation and apologise for any inconveniences caused by this issue.

Your product runs on more than Ringotel

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →