RingCentral Outage History

From Dec 2, 2025 8:11 PM UTC to Dec 2, 2025 9:21 PM UTC, a portion of RingCentral's RingCX users in the Americas experienced outbound calling issues, resulting in call failures for affected customers. RingCentral's Operations team announced they were investigating and would provide updates as they became available. The incident lasted about 1 hour and 10 minutes, during which two status updates were issued before services returned to normal. The issue appeared localized to the Americas RingCX outbound calling component, with no broader impact reported.

A portion of RingCentral Engage Digital customers in Europe experienced application issues impacting the Europe region within the EMEA / Engage Digital - Digital AWS component. The incident began at Dec 1, 2025 11:11 PM UTC and lasted about 1 hour and 15 minutes before services returned to normal. RingCentral’s Operations team investigated and provided updates as the situation evolved, with the next status update planned in four hours or on any significant change in status. The impact was regional to Europe, with service restored by Dec 2, 2025 12:26 AM UTC after two official updates.

RingCentral experienced a partial outage affecting inbound calling and RingCX in the Americas. Users experienced inbound and outbound call issues and some dropped calls. The incident began at Dec 1, 2025 4:21 PM UTC when the Americas / Calling - Inbound component moved to a degraded state, with RingCX issues appearing shortly after. RingCentral Operations implemented mitigations and started to see improvements as the incident progressed, with updates issued at Dec 1, 2025 5:36 PM UTC, Dec 1, 2025 6:06 PM UTC, and Dec 1, 2025 6:46 PM UTC. By Dec 1, 2025 6:46 PM UTC, the Americas / RingCX and the Americas / Calling - Inbound components returned to up, and the incident was resolved. The outage lasted approximately 2 hours and 25 minutes. The provider issued 4 status updates during the incident, and two components in the Americas were affected.

RingCentral experienced a partial outage affecting inbound calling and fax services for a portion of customers in Singapore due to an underlying carrier issue. Affected components included APAC / Fax - Inbound and APAC / Calling - Inbound, with users in the region reporting failed calls and fax transmissions.

RingCentral communicated via its status page and noted that teams were working with the underlying carrier to resolve the issue. The outage began at 6:41 PM UTC and was resolved by 10:06 PM UTC, lasting about 3 hours and 25 minutes. The provider issued 2 status updates during the incident.

An outage affected inbound calling and fax services for a subset of RingCentral numbers in Sarnia and Clinton, Ontario, Canada due to an underlying carrier issue. The problem began at 2025-11-25T14:01:00Z and caused inbound calling and faxing failures for affected customers. RingCentral Operations teams were working with the underlying carrier to resolve the disruption, and customers were advised to contact customer care if they were affected. The issue impacted the Americas / Fax - Inbound and Americas / Calling - Inbound components.

RingCentral reported an outage impacting inbound calling. The issue began on Nov 21, 2025 12:31 AM UTC with toll-free inbound calls failing for customers in New Zealand due to an underlying carrier issue. Over the following days, a regional impact expanded to Europe and the UK, with intermittent inbound call failures and routing problems in the EU/UK region. The incident involved multiple components and persisted until Nov 24, 2025 5:51 PM UTC, roughly 3 days and 17 hours after it began.

During the incident, RingCentral posted five official updates outlining investigation progress. The affected components included APAC / Calling - Inbound, EMEA / Calling - Inbound, and EMEA / Calling - Call Queue, illustrating a regional spread across APAC and EMEA. By the final update at Nov 24, 2025 5:51 PM UTC, inbound calling and call routing had returned to normal and services were restored.

During a scheduled maintenance window for RingCentral Contact Center in the Americas, a portion of customers experienced stuck contacts and agent sessions. RingCentral listed this as informational with no overall service impact. The Americas / Contact Center component moved from up to warn at Nov 18, 2025 10:11 PM UTC and the incident was resolved by Nov 19, 2025 9:21 AM UTC, with maintenance completing and status returning to up. The provider issued 2 status updates over the course of the incident, and the outage lasted approximately 11 hours and 10 minutes.

A partial outage affected RingCentral portals and outbound calling due to a third-party issue. The incident began at 1:46 PM UTC and impacted customers across APAC, Americas, and Europe, with reports of difficulties accessing customer and application portals, missing caller names, and errors when verifying emergency addresses. Eight components were affected, including RingCentral Events, Service Portal, and Calling - Outbound.

A partial outage affected a portion of RingEX and RingCX customers in the United Kingdom, preventing access to the list of past calls and to display call recordings. This impacted users who rely on call history for review and QA, with issues appearing across two EMEA components (RingCX and RingSense). RingCentral Operations teams began investigating and planned an update within four hours as more information became available. The problem was limited to the UK region and did not constitute a global service disruption. The provider issued two status updates during the incident.

An issue affected a portion of RingCentral's Americas Contact Center customers, with presence synchronization problems disrupting call routing, status displays, and agent state updates. This caused degraded operations and reduced visibility within the Contact Center interface for affected users.

The incident began at Nov 13, 2025 9:41 PM UTC and was resolved by Nov 14, 2025 5:06 PM UTC, lasting about 19 hours and 25 minutes. RingCentral's Contact Center team investigated the problem and provided updates as the situation evolved. The status page transitioned from up to warn and then back to up, with a total of two official status updates during the incident.