RingCentral outage history

RingCentral experienced partial SMS outages in the Americas, starting with outbound message failures and later broadening to delays for both inbound and outbound SMS. The impact began around 3:16 PM UTC, with customers unable to send outbound SMS. By 3:36 PM UTC, delays affected inbound and outbound messages across the Americas / SMS - Inbound and Americas / SMS - Outbound components. A user in Redding, California reported that SMS messages were not going through or arriving. The incident persisted for several hours as engineering worked on a root cause and mitigation, and queues were cleared in the following updates.

RingCentral later confirmed a root cause and started mitigation around 4:56 PM UTC, with subsequent updates noting improvement and backlog processing. By 5:16 PM UTC the situation was improving, though delays could remain while the backlog cleared. In the end, inbound and outbound SMS returned to normal by 7:06 PM UTC.

RingCentral reported that a portion of its Americas / Contact Center customers experienced disconnected calls, prompting investigation by RingCentral teams. The incident began at 1:41 PM UTC and was described as a partial outage affecting the Contact Center in the Americas. The status page indicated that updates would come as they were available, with the next update due in about four hours.

The issue persisted for a few hours and was resolved by 4:41 PM UTC, when the Americas / Contact Center component returned to normal and the status was updated to up. The incident appeared limited to the Americas / Contact Center and did not indicate a broader service disruption.

RingCentral experienced a partial outage affecting a portion of Contact Center customers, starting at 1:56 PM UTC with issues connecting to social media channels. RingCentral's Contact Center teams investigated and coordinated with the external platform provider to restore access. Over the next several days, the disruption expanded to voice and messaging services, including inbound and outbound calls and faxing, with reports of dropped calls and inbound call and fax failures tied to underlying carrier issues in some locales, notably in the Val-d’Or region of Quebec. An emergency fix was deployed at 9:51 AM UTC to address outbound calls and faxes in the 907 area code, and the company continued working with carriers to restore service. User reports from New York and Fairport described SMS outages during the incident.

Most services began returning to normal by Aug 11, 2026 1:21 PM UTC, with key voice paths in the Americas moving from warn to up and social-channel connectivity largely restored. RingCentral continued coordinating with the underlying carrier and platform providers to deploy fixes and provide updates as more information became available. The incident affected multiple regions over several days, with social-channel connectivity issues early on and ongoing voice, fax, and SMS problems noted in North America and Val-d’Or, Quebec before a phased recovery.

RingCentral experienced an inbound PSTN calling issue affecting a portion of customers in the Americas. The issue first appeared at 10:02 PM UTC and a partial mitigation was implemented by 10:21 PM UTC as RingCentral Operations identified the cause and began corrective actions for the Americas / Calling - Inbound component. Investigations continued through the overnight and into the next day, with updates at 2:11 AM UTC indicating ongoing work to fully resolve the problem. On 11:11 AM UTC RingCentral said customers were not affected and the incident would be cancelled. Inbound calling was restored, and the component returned to normal by 3:51 PM UTC.

Impact began at 1:11 PM UTC, when RingCentral flagged a degraded SMS experience in the Americas and a portion of Contact Center users faced an inability to make or receive calls. The disruption was regional, affecting messaging delivery and voice interactions for a subset of customers. Actions were taken to restore services, with SMS inbound and outbound returning to normal by 3:26 PM UTC and the Americas / Contact Center service recovery confirmed by 6:01 PM UTC after ongoing monitoring.

RingCentral experienced a partial outage impacting outbound calls to numbers with the 867 area code. Users in the Americas could encounter failed call setups when dialing 867-area numbers, and Deskphone services in the Americas and EMEA were affected as well. Impact began around 10:36 PM UTC as RingCentral Operations began investigating the issue and coordinating the response.

To mitigate, RingCentral routed traffic via an alternate carrier starting around 3:21 PM UTC. The underlying carrier actions helped mitigate the problem by around 7:11 PM UTC, and the affected components returned to normal by 9:02 PM UTC. The outage primarily affected Americas / Calling - Outbound, Americas / Phones - Deskphone, and EMEA / Phones - Deskphone.

A portion of RingCentral customers with New Zealand numbers experienced intermittent inbound and outbound call failures due to an underlying carrier issue, affecting the APAC / Calling - Inbound and APAC / Calling - Outbound components. The issue began at 9:11 AM UTC and was being investigated by RingCentral in coordination with the carrier; customers were advised to contact customer care if they were affected.

By 10:11 AM UTC, the affected calling services had been restored and normal operation resumed for New Zealand numbers. The incident was regional in scope, tied to a carrier issue, and RingCentral continued to provide updates as information became available.

A portion of RingCentral Contact Center customers in the Americas experienced a partial outage starting at 8:31 AM UTC. Users encountered issues saving changes in the service web, receiving push notifications, syncing messages, purchasing devices, changing call queue status, and confirming emergency location in the mobile app. Some customers reported stuck contacts and agent sessions, disrupting normal contact-center workflows. RingCentral’s Contact Center teams began investigating and working to restore functionality.

The issue was resolved and services returned to normal by 8:46 AM UTC, roughly 15 minutes after it began. The affected component was Americas / Contact Center, with the incident described as a partial outage impacting key contact-center capabilities.

A portion of RingCentral customers with Calgary, AB numbers experienced calls that returned a fast busy tone. The issue began at 9:01 AM UTC and was tied to an underlying carrier problem. RingCentral Operations teams were coordinating with the carrier and providing ongoing updates to affected customers; users were advised to contact RingCentral customer care for assistance.

Over the day, the incident appeared to affect additional regions for inbound and outbound calling and, in some cases, fax, with multiple components entering warn status as the carrier investigation continued. Regions including APAC, EMEA, and the Americas showed impact on calling and fax endpoints before stabilization.

By 6:16 PM UTC, affected components returned to normal and callers could again complete calls and faxes. The outage lasted roughly nine hours, with a resolution as the carrier issue was addressed.

A partial RingCentral RingCX outage prevented outbound calls for a portion of RingCX customers in the Americas. RingCentral's Operations teams investigated the issue, and outbound calling was restored after services returned to normal. The impact began at 2:11 AM UTC and was resolved by 4:22 AM UTC, with the affected component identified as Americas / RingCX.