RingCentral Outage History

RingCentral experienced a partial outage affecting number porting for a portion of customers in Australia. The issue was first listed at Jan 8, 2026 2:21 AM UTC as a carrier-related problem, with the underlying carrier investigating. The APAC / Other component was affected during this period, resulting in degraded service for affected users. The outage lasted approximately 6 hours and 25 minutes and was resolved by Jan 8, 2026 8:46 AM UTC.

Over the course of the incident, RingCentral posted 2 status updates detailing the ongoing investigation and restoration of services.

RingCentral reported intermittent outbound call failures affecting a portion of customers in the Americas. The issue impacted the Americas / Calling - Outbound component, causing some users to experience failed or blocked outbound calls. A workaround was suggested: place calls back-to-back to the same number, after which the call would go through. The provider issued 2 status updates during the incident, with the status moving from up to warn and then back to up. The outage lasted about 2 hours and 30 minutes, beginning at Jan 7, 2026 9:41 PM UTC and being resolved by Jan 8, 2026 12:11 AM UTC.

The RingCentral SMS service experienced a partial outage affecting a portion of customers in the Americas, with both inbound and outbound SMS paths impacted for SMS and MMS messages. A user in Oakland, California reported that text message notifications were not working. The incident began at Jan 5, 2026 4:41 PM UTC and was resolved by Jan 5, 2026 8:06 PM UTC, lasting approximately 3 hours and 25 minutes. The provider issued two status updates during the incident as investigation progressed and service was restored.

The affected components were Americas / SMS - Inbound and Americas / SMS - Outbound, and the outage was characterized as a partial outage in the Americas region.

RingCentral reported a partial outage impacting inbound and outbound calling in the RingCentral MiCloud service for customers in the Americas. Some users could not make or receive calls due to certain endpoints being unavailable. The outage began at Jan 5, 2026 4:36 AM UTC and was resolved by Jan 5, 2026 5:46 AM UTC, lasting about 1 hour and 10 minutes. The incident affected the Americas / Calling - Inbound and Americas / Calling - Outbound components.

A portion of RingCentral customers experienced failures in inbound and outbound calls and RingCX functionality. The disruption affected multiple regions, including Americas, EMEA, and APAC, and impacted 12 components spanning RingCX, Calling (Inbound/Outbound), and Other services. Users reported degraded calling experiences and RingCX issues during the incident window. The outage began at 10:46 AM UTC and was resolved by 11:31 AM UTC.

A partial RingCentral RingCX outage affected a portion of customers in the Americas, with users unable to transfer or disconnect calls and inbound calls not being accepted. Some calls were routed to Ring No Answer during the incident. The outage began at 6:46 PM UTC and was resolved by 9:31 PM UTC, lasting approximately 2 hours and 45 minutes. The Americas RingCX component was impacted during this time.

An outage affected a portion of RingCentral's MAX Agent users in the Americas, preventing some Contact Center customers from logging into the MAX Agent application. The issue began at 12:41 AM UTC and was listed as a partial outage while RingCentral investigated. Users attempting to access MAX Agent in the Americas region may have experienced login failures or authentication delays impacting contact center operations. During the incident, RingCentral issued 2 status updates and worked to restore access. The problem was resolved by 2:56 AM UTC, with services returning to normal. The impact appeared localized to the Americas / Contact Center component, with no wider regional disruption.

RingCentral experienced a partial outage affecting the Service Portal for a portion of users across the Americas, EMEA, and APAC, with intermittent portal access and some users unable to modify their call handling rules. The incident began at 4:36 PM UTC and prompted investigation by RingCentral Operations. EMEA components moved to a restored state by 4:56 PM UTC, while Americas and APAC remained degraded for longer.

RingCentral posted three status updates during the incident, describing ongoing investigation and expected updates in 4 hours or upon significant changes. By 6:21 PM UTC, Americas and APAC portals were restored, with EMEA already recovered earlier; the overall outage lasted about 1 hour 45 minutes.

From Dec 3, 2025 10:16 PM UTC RingCentral began listing intermittent issues affecting multiple services across regions. Users were impacted by outbound faxing problems when using Analog Telephone Adapters, outages or delays in the Contact Center agent application, and degraded performance for video meetings. In Canada, some customers experienced inbound calling and faxing failures due to an underlying carrier issue. The problems spanned Americas, APAC, and EMEA, with different components reporting degraded performance at different times. The incident extended across several days, with ongoing updates as teams investigated and deployed mitigations. The situation progressed toward recovery, with components gradually returning to normal activity by Dec 15, 2025 9:16 PM UTC.

The incident affected a broad set of RingCentral services, with issues reported across Messaging, Service Portal, and Other components spanning Americas, EMEA, and APAC. Users could experience saving changes in the web app, not receiving push notifications, delays in message syncing, problems purchasing devices, changes to call queue status, and the inability to confirm emergency location in apps.

The outage began on Dec 3, 2025 2:01 PM UTC and was resolved by Dec 3, 2025 3:56 PM UTC, lasting about 1 hour and 55 minutes. RingCentral's Operations teams investigated the issue and published two status updates during the incident as more information became available.