RingCentral Outage History

RingCentral reported a call quality issue impacting a portion of customers in the Americas, affecting both inbound and outbound calling. Users experienced degraded audio and intermittent call problems during the incident window. The issue began at 4:46 PM UTC.

An update at 5:02 PM UTC indicated the cause had been identified and corrective actions were underway to restore service. By 5:21 PM UTC inbound and outbound calling had returned to normal across the affected components: Americas / Calling - Inbound and Americas / Calling - Outbound.

Overall, the disruption was regional to the Americas and did not indicate a global outage. The incident lasted roughly 35 minutes before full restoration.

A portion of RingCentral Events customers were unable to view or broadcast from stages, affecting attendees and speakers. The issue was confined to the Americas region and prompted an investigation by RingCentral Operations, with an update planned in four hours. The incident began at 2:31 PM UTC and was resolved by 2:56 PM UTC.

This outage impacted the session broadcasting experience for affected users, and RingCentral confirmed that the relevant Events component returned to normal as the incident was closed.

Users in the Americas region experienced a login outage that prevented signing in to RingCentral desktop, web, and mobile apps. The issue began around 7:36 PM UTC and persisted for several days as RingCentral Operations investigated and issued updates describing ongoing login problems that impacted messaging and collaboration features.

By 2:06 PM UTC the team had identified the root cause and began mitigation efforts. Mitigation steps were completed by 4:46 PM UTC, and internal testing plus end-user feedback confirmed restoration for the Americas / Messaging component by 6:16 PM UTC, with continued monitoring to ensure stability.

RingCentral users in North America experienced inbound calling failures, disrupting basic voice services for some customers. The issue appeared when the Americas / Calling - Inbound component moved to a degraded state at 11:56 PM UTC as RingCentral Operations began investigating. The outage affected call setup and call quality for affected users, with ongoing troubleshooting for several hours.

By 12:21 AM UTC, engineers had identified the underlying cause and started deploying a potential fix. A subsequent update at 12:36 AM UTC confirmed the root cause and noted a permanent fix would be deployed in the next maintenance window. The service stabilised and inbound calling returned to normal by 8:56 AM UTC.

A portion of RingCentral customers in the Americas could not reliably send outbound SMS messages due to an underlying carrier issue affecting the outbound SMS path. The issue surfaced for the Americas / SMS - Outbound component and caused failures or delays for affected users. The incident began at 9:21 PM UTC and was resolved by 10:16 PM UTC as the carrier issue was addressed, bringing the outbound SMS service back to normal. RingCentral Operations teams were coordinating with the underlying carrier to resolve the problem, and the status page indicated a follow-up update would be provided as changes occurred.

A portion of RingCentral's Contact Center customers in the Americas experienced failures when attempting manual outbound calls from the agent workspace, disrupting outbound call workflows for agents and customers. The impact began at 1:41 PM UTC and was resolved by 2:16 PM UTC, with impact confined to the Americas region.

RingCentral's status updates document the response: after the incident was detected, the team investigated with an update promising further details within four hours. At 1:51 PM UTC they reported that telecommunications routing changes had been applied to restore services and that monitoring would continue to confirm stability. The Americas / Contact Center component returned to normal at 2:16 PM UTC.

RingCentral reported a partial outage affecting calls for a portion of Contact Center customers in the Americas. Users could experience failed call setups or degraded call quality as platform requests failed to complete the expected connection handshake with external servers. The incident began at Feb 27, 2026 10:36 PM UTC and persisted through Feb 28, 2026 2:16 AM UTC, lasting roughly 3 hours and 40 minutes. The issue involved the Americas / Contact Center component and affected call-related services for affected users.

RingCentral's Contact Center teams investigated and posted two updates during the incident. The initial update noted ongoing investigation and promised updates roughly every 4 hours or sooner if the situation changed. The second update stated that platform-originated requests were not completing the handshake with the external server, with traffic possibly being blocked or filtered before reaching the destination, and that external network conditions were contributing to the issue. The team continued to investigate and a resolution had not been reported at the time of the latest update.

RingCentral experienced a partial outage impacting RingCX and Contact Center components in the Americas. Users reported application errors in RingCX and inbound/outbound call failures in Contact Center, with some calls fading in and out. RingCentral issued multiple updates as teams investigated and implemented mitigations, including rerouting calls and monitoring for stability. The incident affected a subset of users across two components in the Americas and lasted for several hours before services returned to normal. The outage began at Feb 26, 2026 7:36 PM UTC and was resolved by Feb 26, 2026 11:21 PM UTC.

A subset of RingCentral customers using two-factor authentication experienced login problems across RingCentral Messaging and the Service Portal. The issue affected users across the Americas, EMEA, and APAC regions; those already logged in were not impacted. Affected components included Americas Messaging, EMEA Messaging, APAC Messaging, Americas Service Portal, EMEA Service Portal, and APAC Service Portal. The outage lasted about 30 minutes. The incident involved multiple regions and components, with investigations and updates provided by RingCentral during the incident.

RingCentral reported a regional outage affecting the Americas Contact Center, with agents unable to log into the agent portal. The issue began at 10:56 AM UTC and lasted about 25 minutes, with access restored by 11:21 AM UTC. The problem appeared isolated to the Americas / Contact Center component, with no broader service disruptions indicated. The incident prompted three status updates from RingCentral during the event. An emergency network change was deployed at 11:16 AM UTC to resolve the issue, and login access began returning shortly after. The component returned to up by 11:21 AM UTC.