All Systems Operational

Uptime over the past 90 days. View historical uptime.
Provisioning Portal & API Endpoints Operational
Knowledge base Operational
Ringotel MCP Operational
Regions Operational
Asia Pacific (Singapore) Operational
Australia Operational
Europe (Dublin) Operational
Europe (Frankfurt) Operational
Europe (London) Operational
US East Operational
US West Operational
India (Mumbai) Operational
Canada (Central) Operational
Africa (Cape Town) Operational
South America (São Paulo) Operational
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.

No incidents or maintenance related to this downtime.

Sep 23, 2026

No incidents reported today.

Sep 22, 2026

No incidents reported.

Sep 21, 2026

No incidents reported.

Sep 20, 2026

No incidents reported.

Sep 19, 2026

No incidents reported.

Sep 18, 2026

No incidents reported.

Sep 17, 2026

No incidents reported.

Sep 16, 2026

No incidents reported.

Sep 15, 2026

No incidents reported.

Sep 14, 2026

No incidents reported.

Sep 13, 2026

No incidents reported.

Sep 12, 2026

No incidents reported.

Sep 11, 2026

System outage in multiple regions
Resolved - This incident has been resolved.
Sep 11, 15:06 UTC
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 1, 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 1, 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, 12:44 UTC

Sep 10, 2026

No incidents reported.

Sep 9, 2026

No incidents reported.

Incident History Powered by Atlassian Statuspage