RingCentral Outage History

RingCentral's Americas Contact Center experienced login issues and slow platform performance affecting a portion of customers. The incident began at May 28, 2025 3:07 PM UTC and RingCentral's Contact Center teams began investigating the issue.

RingCentral issued 2 status updates during the incident. The issue was resolved by May 28, 2025 3:56 PM UTC, and the Americas Contact Center component returned to normal operation. The outage lasted approximately 49 minutes.

RingCentral's Contact Center users in the Americas experienced a brief outage affecting login and contact delivery for a portion of customers. The issue began at May 27, 2025 6:16 PM UTC and was resolved by May 27, 2025 6:36 PM UTC, lasting roughly 20 minutes. The incident appeared localized to the Americas / Contact Center component rather than global.

RingCentral published two status updates during the incident. The initial update noted investigation and indicated that a follow-up update would be provided in up to four hours or sooner if there were significant changes; about 20 minutes later, the status returned to normal and service resumed for affected customers.

The outage affected a portion of RingCentral's Engage Digital and RingCX customers who were unable to send messages on Twitter/X. The issue was centered in the Americas region, impacting three components: Americas / RingCX, Americas / Engage Digital - Digital AWS, and Americas / Engage Digital - Digital Claranet. The problem began at 2:11 PM UTC and was resolved by 6:21 PM UTC, lasting approximately 4 hours and 10 minutes. Users may have experienced failures or delays when attempting to send messages on Twitter/X during the window.

RingCentral reported a partial outage affecting the Americas Contact Center, with some customers experiencing stuck contacts and disrupted agent sessions. The issue impacted the Americas region's Contact Center component and lasted from May 22, 2025 1:56 PM UTC to May 22, 2025 7:26 PM UTC, a duration of about 5 hours and 30 minutes. Users may have seen delays or interruptions in routing conversations or agent workflows during the incident. The provider issued two status updates, first noting the problem and ongoing investigation, and later confirming resolution as the service returned to normal.

A portion of RingCentral's Contact Center customers in the Americas experienced platform issues, causing degraded performance for contact center features. The incident began at 8:31 PM UTC and was resolved by 9:11 PM UTC, lasting roughly 40 minutes. The issue appears limited to the Americas region. RingCentral issued two status updates during the incident, identified the cause, and implemented corrective actions to restore service. Users were advised to log out of the application, clear browser cache and cookies, and fully close and relaunch their browser; contact customer care if issues persisted. Monitoring continued after the final update and service stability was restored.

RingCentral reported a partial outage in its Americas-based Contact Center that disrupted chat delivery to available agents and affected Digital First Omnichannel interactions. Some customers experienced chats not connecting to agents or delays in routing. The incident began at 10:11 AM UTC and was resolved by 11:06 AM UTC, lasting roughly 55 minutes. RingCentral issued 2 status updates during the incident as teams investigated and worked to restore normal service. The impact appeared limited to a portion of Contact Center users in the Americas region.

A portion of RingCentral Contact Center customers experienced missing dispositions, affecting how calls and interactions were labeled and routed. The issue appeared primarily in the Americas, with reports indicating US callers, including a Texas case, were unable to reach or properly disposition some support interactions. The incident began at May 19, 2025 8:16 PM UTC and was resolved by May 21, 2025 4:26 AM UTC, with RingCentral releasing multiple updates during the period.

The outage affected the Americas / Contact Center and Americas / RingCX components and lasted roughly 1 day and 8 hours. The provider issued four official updates as the situation evolved, and overall user impact was described as a partial outage with degraded workflow for handling dispositions.

A partial outage affected RingCentral's Americas Contact Center customers, with some users unable to receive inbound calls or place outbound calls. The incident began at 2:11 PM UTC and was resolved by 3:26 PM UTC, lasting roughly 25 hours and 15 minutes. The issue involved the Americas / Contact Center component and impacted customer communications in the region.

RingCentral's Contact Center teams investigated the issue and provided updates on the status page. The provider issued 2 official status updates during the incident, describing the investigation and eventual restoration. The status transitions reflected a move from a warning to normal operation as services recovered.

The outage began on 1:16 PM UTC and was resolved by 6:32 PM UTC. A portion of RingCentral customers using Android devices were unable to register for Events, causing a partial outage for Event registration. A workaround allowed users to register on the web and then access the event from the application, or to use Chrome on Android. The Americas / RingCentral Events component was affected.

Two official status updates were published during the incident as RingCentral investigated the issue. The outage lasted approximately 5 hours 16 minutes, ending when status returned to up.

A partial outage affected inbound calling for UK numbers in RingCentral, impacting customer support access for a subset of users in the EMEA region. The incident began at 9:21 AM UTC and impacted the EMEA / Calling - Inbound component, with UK customers unable to reach RingCentral support lines while teams investigated. The outage lasted approximately 5 hours and 6 minutes and was resolved by 2:27 PM UTC.

RingCentral issued two status updates during the incident, outlining ongoing investigation and restoration efforts. By the time service was restored, inbound calling for UK numbers returned to normal operation.