Update - Dear Customers,

We apologise both for yesterday's service disruption and for the delay in getting you a full update. We continue to monitor the situation and in the meantime would like to share the incident's report.

Starting at approximately 11:30 AM UTC yesterday, malicious actors launched a coordinated attempt to gain unauthorised access to our SIP infrastructure. It began in the US East and US West regions and then spread to London, Dublin, Singapore, and a few on-premise regions. This caused intermittent call failures, degraded performance, and issues with connections and user visibility in the admin portal. Because the attack degraded service rather than knocking regions fully offline, our automatic failover never triggered. Our team manually failed affected regions over to secondary infrastructure. After switching to secondary infrastructure, some customers had trouble connecting because only our primary IP was whitelisted on their PBX security appliance.

The incident was largely resolved by 2:30 PM UTC, though full resolution in a few remaining regions wasn't reached until around 3:00 AM UTC on September 1st. As a result of this attack, no customer data was accessed, and no unauthorised calls were made.

We have implemented additional security measures to our SIP-layer to minimise the impact of similar attacks. We'll also improve our response speed during an active incident.

Moving forward, please confirm both Ringotel IPs are whitelisted on your PBX security appliance for the region(s) where your Ringotel organisations are created. Check our help center for the current IP addresses by region: https://help.ringotel.com/en/articles/11190222-configure-firewall-to-work-with-ringotel

Thank you for your patience, and please reach out to us with any questions.

Sep 01, 2026 - 17:42 UTC
Monitoring - We apologise for the delayed communication about this incident. The root cause has been identified and mitigation measures are in place. We’re now completing infrastructure updates across the regions and a post-mortem will follow shortly.
Sep 01, 2026 - 15:21 UTC
Investigating - We received multiple reports of system outage in US East and London regions. We are currently investigating this issue and will report back as soon as possible.
Aug 31, 2026 - 12:44 UTC
Provisioning Portal & API Endpoints Operational
90 days ago
100.0 % uptime
Today
Knowledge base Operational
90 days ago
99.95 % uptime
Today
Ringotel MCP Operational
90 days ago
100.0 % uptime
Today
Regions Operational
90 days ago
99.99 % uptime
Today
Asia Pacific (Singapore) Operational
90 days ago
100.0 % uptime
Today
Australia Operational
90 days ago
100.0 % uptime
Today
Europe (Dublin) Operational
90 days ago
100.0 % uptime
Today
Europe (Frankfurt) Operational
90 days ago
100.0 % uptime
Today
Europe (London) Operational
90 days ago
100.0 % uptime
Today
US East Operational
90 days ago
100.0 % uptime
Today
US West Operational
90 days ago
99.99 % uptime
Today
India (Mumbai) Operational
90 days ago
99.99 % uptime
Today
Canada (Central) Operational
90 days ago
100.0 % uptime
Today
Africa (Cape Town) Operational
90 days ago
99.98 % uptime
Today
South America (São Paulo) Operational
90 days ago
100.0 % uptime
Today
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.

Sep 7, 2026

No incidents reported today.

Sep 6, 2026

No incidents reported.

Sep 5, 2026

No incidents reported.

Sep 4, 2026

No incidents reported.

Sep 3, 2026

Resolved - 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.
Sep 3, 09:36 UTC
Identified - 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.
Sep 2, 20:22 UTC
Update - 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.
Sep 2, 09:28 UTC
Investigating - 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 support@ringotel.co or use the online chat / create a ticket. We appreciate your patience in the meantime.
Sep 2, 05:54 UTC

Sep 2, 2026

Sep 1, 2026

Resolved - This incident has been resolved.
Sep 1, 15:23 UTC
Monitoring - We apologise for the delayed communication about this incident. The root cause has been identified and mitigation measures are in place. We’re now completing infrastructure updates across the regions and a post-mortem will follow shortly.
Sep 1, 15:20 UTC
Investigating - A new Ringotel incident has been automatically created in the affected region (US West). Our team has been notified and will review it immediately. If you have any questions, please contact us at support@ringotel.co or use the online chat / create a ticket. We appreciate your patience in the meantime.
Aug 31, 14:03 UTC

Aug 31, 2026

Aug 30, 2026

No incidents reported.

Aug 29, 2026

No incidents reported.

Aug 28, 2026

No incidents reported.

Aug 27, 2026

No incidents reported.

Aug 26, 2026

Resolved - 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.
Aug 26, 21:40 UTC
Monitoring - The incident has been resolved. Our team is monitoring the status and will provide an update shortly.
Aug 26, 16:18 UTC
Investigating - 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 support@ringotel.co or use the online chat / create a ticket. We appreciate your patience in the meantime.
Aug 26, 15:13 UTC

Aug 25, 2026

No incidents reported.

Aug 24, 2026

No incidents reported.