RingCentral outage history

RingCentral experienced a brief partial disruption affecting SMS delivery in North America, with inbound and outbound SMS routes showing delays for a portion of customers. The issue began at 10:52 AM UTC and was resolved by 11:01 AM UTC. RingCentral's status page indicated that the delays were caused by an underlying carrier issue and that the North America SMS delay problem has been resolved; customers still experiencing issues were advised to contact customer care. The disruption was localized to North America, with other services remaining operational and the overall impact limited to longer SMS delivery times rather than a full outage.

In the Americas, a portion of RingCentral users could not log in because notification emails, including two-factor authentication messages, were not being delivered. The outage began around 9:11 PM UTC as the company’s Operations teams investigated, with guidance to contact customer care and a cadence of updates approximately every four hours or on significant changes. Affected components in this initial issue included RingCentral Video, Messaging, Service Portal, and RingCX, and users experienced login hurdles while the email delivery problem persisted.

Separately, RingCentral’s Contact Center also saw degraded experience, with dead air during IVR interactions reported starting around 10:31 PM UTC. Teams implemented routing mitigations and monitored traffic recovery as they worked to restore call quality. By 12:26 AM UTC, the Americas Contact Center component had returned to normal, marking the partial outage’s easing, while other services continued to stabilize. The impact was most evident for contact center users needing reliable IVR access and for customers relying on timely notification emails to sign in.

Users relying on RingCentral's APAC Contact Center faced intermittent call handling issues, including calls not reaching available agents and one-way or missing audio. The problem began at 12:31 AM UTC and affected a portion of APAC customers, prompting ongoing investigation and remediation by RingCentral's Contact Center teams. The situation improved as fixes were applied, with the APAC / Contact Center component returning to normal by 3:11 AM UTC.

RingCentral customers in the Americas experienced a partial outage with a one-time drop of calls or loss of registration, impacting Deskphone and both inbound and outbound calling. The affected components were Americas / Phones - Deskphone, Americas / Calling - Inbound, and Americas / Calling - Outbound. Impact began at 3:41 PM UTC as RingCentral Operations opened an investigation; mitigation steps were implemented and improvements were noted by 3:56 PM UTC.

By 4:16 PM UTC, the affected components had returned to normal operation (up), and service was stabilizing. The incident lasted about 35 minutes, with RingCentral continuing to monitor for stability and provide updates as needed.

A portion of RingCentral's Americas / Contact Center customers experienced delays in routing contacts to available agents, resulting in longer wait times for calls and messages. The incident began at 8:51 PM UTC and affected users for roughly two hours before mitigations took effect.

RingCentral's Contact Center teams implemented mitigation steps and observed improvements as they monitored stability. Routing returned to normal by 10:56 PM UTC, and teams continued to monitor for stability in the component.

A portion of RingCentral's Contact Center customers in the Americas experienced delays routing contacts to available agents, impacting live interactions and customer service workflows. The issue began at 3:16 PM UTC and persisted for about two and a half hours before returning to normal at 5:46 PM UTC.

RingCentral's Americas / Contact Center team investigated and provided a temporary workaround to manually assign contacts while a fix was developed, with updates to follow as the situation evolved (the next update was planned in roughly four hours or sooner if there were significant changes).

Some RingCentral customers in the Americas experienced SMS messages being routed to the wrong number, impacting both inbound and outbound SMS. RingCentral's Operations teams began investigating, with the status updated to a partial outage starting at 5:02 PM UTC. The issue affected the Americas / SMS - Inbound and Americas / SMS - Outbound components. The incident was resolved by 7:06 PM UTC, with services returning to normal. The status page noted updates would be provided as the investigation progressed, with the next update in 4 hours or when there is a significant change.

A portion of RingCentral's Contact Center customers experienced issues starting around 12:46 PM UTC, with stuck contacts and disrupted agent sessions. The disruption extended to inbound and outbound calls and affected regional deployments in the Americas and EMEA. RingCentral’s Contact Center teams investigated and began applying mitigations, with improvements noted as steps took effect. By 2:11 PM UTC mitigations were producing results, and by 3:21 PM UTC in EMEA the region showed progress toward stability. The Americas component moved back to up by 5:06 PM UTC as services stabilized. Overall, user reports remained limited, indicating a partial outage rather than a global failure. The status page continued to provide updates and indicated a cadence of roughly four hours for the next update or until a significant change occurred.

Users in the Americas experienced delays in receiving RingCentral notification emails, including two-factor authentication messages, which prevented logins across key services. The issue began at 6:31 PM UTC and affected components across RingCentral Video, Messaging, Service Portal, RingCX, and both inbound and outbound calling.

A portion of RingCentral's APAC Contact Center customers experienced degraded sound quality on inbound calls starting 4:16 AM UTC. RingCentral's Contact Center teams stated they were investigating the problem and would provide updates as they progressed, signaling a partial outage affecting inbound audio for the APAC region. The incident reflects user-facing disruption in voice calls for agents and customers relying on APAC inbound lines.

The issue was resolved by 6:31 AM UTC, with the APAC / Contact Center component returning to normal operation and status updated to up. The disruption was contained to the affected component, and service has since stabilized.