RingCentral Outage History

An incident affected RingCentral's Europe (EMEA) Contact Center customers, causing delays in routing digital contacts and degrading routing performance across digital channels. The outage began at Feb 25, 2026 2:56 AM UTC and was resolved by Feb 25, 2026 4:41 AM UTC, lasting about 1 hour and 45 minutes. The issue was limited to the Europe region and impacted the EMEA / Contact Center component.

A portion of RingCentral customers in Europe experienced failures in both inbound and outbound calling, affecting numbers in the Czech Republic and several other countries (UK, France, Germany, Poland, Luxembourg). The issue appears to be carrier-related and affected two RingCentral components in the EMEA region: Inbound Calling and Outbound Calling. The impact included missed calls and degraded calling quality for some users.

The disruption lasted from Feb 20, 2026 1:01 PM UTC to Feb 23, 2026 8:01 PM UTC, spanning roughly 3 days and 7 hours. The provider issued 6 status updates during the incident. By Feb 23, 2026 4:21 PM UTC some callers reported calls completing, and remediation steps were planned for the next maintenance window, with the final update confirming inbound and outbound calling were back to normal.

A subset of RingCentral users in the Americas experienced delayed inbound and outbound SMS messages due to an issue with a partner mobile carrier. This caused messages to be delivered late for affected customers and disrupted two-way messaging in the region. The outage began on Feb 20, 2026 1:41 AM UTC and was resolved by Feb 20, 2026 6:16 AM UTC, lasting approximately 4 hours and 35 minutes. RingCentral issued 2 status updates during the incident as the carrier investigated and then restored service. The issue affected the Americas / SMS - Inbound and Americas / SMS - Outbound components.

RingCentral experienced a partial outage affecting APAC contact centers, with some CXone Agent users unable to log in. This prevented agents from signing into CXone Agent and could disrupt day-to-day operations for APAC-based contact centers. The APAC / Contact Center component moved to a degraded state at 6:11 AM UTC and was fully restored by 7:31 AM UTC, for a total duration of approximately 1 hour 20 minutes. RingCentral published two status updates during the incident to communicate investigation and restoration steps, and corrective actions were taken to return service to normal.

An issue in RingCentral's Europe region caused a partial outage of the RingCentral customer portal, preventing a portion of European users from accessing the portal. The impact was limited to the EMEA / Service Portal component, with users in Europe experiencing outages for a period of time. The outage began at Feb 13, 2026 2:52 PM UTC and was resolved by Feb 13, 2026 4:56 PM UTC, lasting approximately 2 hours and 4 minutes.

An outage disrupted outbound fax delivery for a portion of RingCentral customers due to an underlying carrier network issue. The problem affected the Americas Fax-Outbound service and RingCX in Americas, EMEA, and APAC, with users reporting failed faxes while other communications remained available. The incident began at Feb 12, 2026 7:11 PM UTC and was resolved by Feb 13, 2026 12:11 AM UTC, lasting about 5 hours. The provider issued four status updates as the situation evolved.

RingCentral Operations teams investigated and reassessed the scope, providing ongoing updates and guidance through the incident. By the time services were restored, the affected components (Americas RingCX, EMEA RingCX, APAC RingCX, and Americas Fax-Outbound) were returned to normal operation, and users could resume sending outbound faxes. The issue appeared isolated to outbound fax delivery and did not indicate a broader service disruption across RingCentral’s platform.

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.