Resolved after 11 days 22 hours, affecting India (Mumbai), on July 8, 2025.
The incident was triggered by the unusual behavior of the garbage collector, leading to a heap out of memory error. In response, our team has implemented changes and activated extended logging to closely monitor the situation.
Affected components
Update timeline
- investigating Jul 08, 2025, 04:48 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.
- resolved Jul 20, 2025, 03:28 PM UTC
The incident was triggered by the unusual behavior of the garbage collector, leading to a heap out of memory error. In response, our team has implemented changes and activated extended logging to closely monitor the situation.
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.
Amazon Web Services