RingCentral outage history

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.

A portion of RingCentral's Contact Center customers in the Americas could not log in or access platform applications, hindering contact center operations. The outage appeared tied to a broader infrastructure connectivity event that affected multiple components responsible for platform access and request routing. The issue began at 12:16 PM UTC and recovery followed about an hour later, with the Americas Contact Center component returning to normal operation around 1:16 PM UTC as monitoring indicated stability. RingCentral communicated ongoing investigations and advised affected customers to reach out to customer care as updates were provided.

A portion of RingCentral Contact Center customers in the Americas experienced outbound SMS delivery issues, likely impacting users trying to send SMS messages. The disruption began at 11:21 PM UTC and appeared to be resolved by 11:37 PM UTC after RingCentral implemented corrective actions and conducted internal testing. Affected users were advised to log out of the application, clear browser cache and cookies, and fully close and relaunch their browser to restore operation. The incident was brief and monitoring indicated stability after recovery.

RingCentral reported degraded audio quality on inbound calls affecting a portion of customers using the Americas / Contact Center. Impact began at 6:01 PM UTC and the status page noted the team was investigating, with updates planned every few hours. The issue persisted for about two hours as engineers worked to restore service, and the component returned to normal later in the incident period, with a final update indicating the issue had been resolved for that segment.