RingCentral Outage History

The RingCentral incident affected multiple regions and components, including Americas Contact Center, RingCX in Americas/EMEA/APAC, and Webinar, causing platform slowness, login issues, and in some cases the inability to go live. Users across the Americas, Europe, and APAC experienced degraded performance and access problems while RingCentral investigated the cause and worked toward a fix. The outage began on Feb 10, 2026 9:21 PM UTC and was resolved by Feb 11, 2026 8:21 AM UTC, lasting roughly 11 hours. The provider issued several updates detailing progress and provided user-facing remediation steps (such as re-logging and clearing browser cache) as the teams worked to restore services.

The outage affected RingCentral RingCX in the Americas, APAC, and EMEA regions and the Americas-based Contact Center, causing outbound campaign dials to connect to agents instead of leads and later loss of agent sessions and contacts. The incident began at Feb 4, 2026 8:51 PM UTC and lasted until all affected components were restored at Feb 5, 2026 8:16 PM UTC, spanning roughly 23 hours and 25 minutes. This disruption impacted customer interactions and critical workflows that rely on outbound dialing and contact center operations.

RingCentral issued four status updates during the incident, including details about investigating the issue and, later, removing a carrier from call routing for affected customers before confirming recovery. The updates show progression from initial degradation across RingCX components in multiple regions to eventual restoration of the Americas Contact Center and then all RingCX components, with services returning to normal by the end of the period.

RingCentral reported a brief partial outage affecting mobile notifications for users of the RingCentral mobile app. The issue was localized to the Americas region, specifically the Americas / Calling - Inbound component, and could cause delayed alerts and missed calls. The incident began at Feb 4, 2026 5:26 PM UTC and lasted about 20 minutes, with service returning to normal by Feb 4, 2026 5:46 PM UTC. The provider issued two status updates during the event: an investigation notice and a follow-up confirming resolution.

The RingCentral Contact Center in the Americas experienced intermittent issues completing dispositions for contacts within the application, affecting a portion of customers. The problem began at Feb 3, 2026 3:53 PM UTC and lasted roughly 4 hours and 8 minutes, ending at Feb 3, 2026 8:01 PM UTC. Users reported being unable to finalize dispositions and, in some cases, were asked to log out and back in to receive the next contact. RingCentral issued two official status updates during the incident as the team investigated and moved toward a resolution, with the Americas / Contact Center component returning to normal after the outage.

A partial outage impacted RingCentral RingCX login and calling for a portion of customers across APAC, Americas, and EMEA. The issue began at Feb 2, 2026 4:36 PM UTC and was resolved by Feb 2, 2026 8:36 PM UTC, lasting about four hours. RingCentral issued two status updates during the incident as the RingCX teams investigated and worked to restore services. The incident affected multiple regional RingCX components before services returned to normal.

A partial outage affected inbound and outbound calling for a subset of RingCentral customers in Granby, QC; Cranbrook, BC; Trois-Rivieres, QC; and Saint-Lambert, QC. Users in these areas experienced call failures while attempting to place or receive calls, with the issue traced to an underlying carrier problem. The affected components were Americas / Calling - Inbound and Americas / Calling - Outbound. The incident began at 8:06 AM UTC and was resolved by 10:56 AM UTC, lasting approximately 2 hours and 50 minutes. The provider issued 2 status updates during the incident, noting ongoing communication with the carrier and that services would be restored as the carrier issue was addressed.

RingCentral reported a regional issue affecting inbound and outbound calling for a portion of customers in Thetford Mines, QC. Users may have experienced failed calls or degraded calling quality, with related RingCentral Apps and Services impacted.

The outage began on Jan 28, 2026 8:11 AM UTC and was resolved by Jan 28, 2026 10:51 AM UTC, lasting approximately 2 hours and 40 minutes. The provider issued 4 status updates during the incident, describing ongoing effects and eventual restoration. The impact was limited to 4 components: Americas / Calling - Inbound, Americas / Calling - Outbound, Americas / Service Portal, and Americas / Calling - Call Queue.

A portion of RingCentral customers in the Americas experienced delays sending and receiving SMS messages due to an underlying carrier issue. Inbound and outbound SMS services were briefly degraded for some users, resulting in slower message delivery.

The outage began at 2:46 AM UTC and was resolved by 2:56 AM UTC. RingCentral posted two official updates during the event, noting that the underlying carrier was investigating and that the next update would be provided in about four hours or when a significant change occurred. The impact was limited to Americas SMS inbound and outbound components.

The incident began at Jan 23, 2026 6:41 PM UTC when RingCentral reported a portion of customers were intermittently experiencing delayed or failed SMS messages due to an underlying carrier issue. The impact affected multiple regions (Americas, EMEA, APAC) with SMS inbound and outbound paths experiencing delays or undelivered messages. RingCentral Operations teams engaged the underlying carrier and pledged further updates as the investigation progressed, with the next update due roughly every 4 hours.

On Jan 27, 2026 4:41 PM UTC and again at Jan 27, 2026 5:01 PM UTC, a separate issue emerged impacting inbound calls and faxes for numbers in Stoney Point, Wheatley, and Windsor, ON. RingCentral teams continued to work with the carrier to resolve the issue, issuing additional updates as the situation evolved. By Jan 27, 2026 8:06 PM UTC, some components in the Americas for inbound fax and inbound calling had returned to normal, indicating partial recovery while other SMS paths remained degraded. The incident spanned from Jan 23, 2026 6:41 PM UTC to Jan 27, 2026 8:06 PM UTC.

A portion of RingCentral RingCX customers experienced Ring No Answer and were unable to take calls, starting around 2:56 PM UTC in the Americas. This degraded call delivery affected agents and customers relying on RingCX for inbound and outbound calls. RingCentral Operations identified the issue and initiated a rollback of a recent release to mitigate impact.

The issue extended to the EMEA region starting at 3:21 PM UTC, with continued mitigation as the rollback progressed. EMEA recovered by 5:46 PM UTC, and the Americas region recovered by 9:41 PM UTC. The provider issued four status updates during the incident while restoring stability. The outage durations were approximately 6 hours 45 minutes for the Americas segment and about 2 hours 25 minutes for EMEA, with service returning to normal thereafter.