Ringotel incident
Ringotel Incident - Cape Town (South Africa)
Ringotel experienced a critical incident on September 2, 2026 affecting Africa (Cape Town), lasting 1d 3h. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Sep 02, 2026, 05:54 AM UTC
A new Ringotel incident has been automatically created in the affected region (Cape Town (South Africa)). 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.
- investigating Sep 02, 2026, 09:28 AM UTC
Our team is investigating a brief outage in Cape Town region between 5:55 and 6:13 AM UTC. The server is fully operational and under extended monitoring. This issue is unrelated to the recent outage in other regions. An update will follow soon.
- identified Sep 02, 2026, 08:22 PM UTC
We have identified a situation that causes heap out-of-memory (OOM) error. 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.
- resolved Sep 03, 2026, 09:36 AM UTC
The team has pinpointed the cause of the heap out-of-memory error and implemented a fix to prevent future occurrences. The affected region is now fully operational and no issues have been reported across the platform. Should you have any question or concerns please don't hesitate to reach out to our support team.