RingCentral Outage History

RingCentral reported a brief period of intermittent login issues affecting multiple services in the Americas, including RingCX, RingCentral Video (Meetings), and other components. The incident began at 1:06 PM UTC and was resolved by 2:01 PM UTC, lasting about 55 minutes. Official updates noted mitigation steps and improvements toward stability, with the next update planned in 4 hours or upon a significant change. By 2:01 PM UTC all components were listed as up again. User reports during this window indicated login issues, concentrated in the Americas region.

RingCentral's Americas Contact Center experienced a partial outage with dead air on outbound calls. The issue began at Apr 16, 2025 9:26 PM UTC and was resolved by Apr 16, 2025 11:46 PM UTC, lasting about 2 hours and 20 minutes. RingCentral issued two status updates during the incident as teams investigated and implemented fixes, and the service was restored after the updates. The impact was limited to outbound call paths in the Americas Contact Center, affecting a subset of customers.

RingCentral reported a partial inbound calling outage affecting a portion of customers in Japan, who could not receive inbound calls from other numbers in Japan. The issue impacted two inbound calling components: Americas / Calling - Inbound and APAC / Calling - Inbound, and was attributed to a third-party provider. The incident began on Apr 9, 2025 5:46 AM UTC and was resolved by Apr 9, 2025 11:06 AM UTC, lasting approximately 5 hours and 20 minutes.

A portion of RingCentral's Contact Center customers experienced issues with the Agent application, affecting users in the Americas. The incident began at Apr 4, 2025 6:31 PM UTC and was resolved by Apr 4, 2025 7:16 PM UTC, lasting about 45 minutes. The outage disrupted agent workflows and could have impacted login or session stability for affected users. The provider issued two status updates during the incident and a small number of user reports were observed.

A portion of RingCentral's Contact Center customers in the EMEA region experienced call refusals and degraded audio quality when using the agent platform; investigations focused on network routing and session handling, with a workaround to move the WebRTC Gateway away from London and Manchester until the issue is resolved. The incident began at Mar 25, 2025 4:11 PM UTC and was resolved by Mar 25, 2025 5:36 PM UTC, lasting about 1 hour 25 minutes; RingCentral issued two status updates during the incident documenting the degraded state for the EMEA / Contact Center component and the workaround, after which service returned to normal.

A portion of RingCentral's EMEA Contact Center customers experienced stuck contacts and agent sessions, impacting call and chat flows for a short period. The disruption affected the EMEA Contact Center component and lasted approximately 5 minutes, beginning at Mar 6, 2025 5:01 AM UTC and resolved by Mar 6, 2025 5:06 AM UTC. RingCentral posted two official status updates during the incident, confirming the issue was resolved. Users were advised to contact customer care if they still experienced problems. The incident appeared to be limited to the EMEA region's Contact Center and did not indicate broader impact.

A portion of RingCentral Events customers in the Americas experienced an outage that prevented access to the events platform, impacting their ability to manage or participate in live events. The issue began at 12:01 AM UTC and lasted until 4:16 AM UTC, for an approximate duration of 4 hours and 15 minutes.

RingCentral's Operations teams issued multiple status updates as they investigated the cause and worked to restore access. The RingCentral status page indicated a partial outage for the Americas / RingCentral Events component and advised that the next update would be provided in about 4 hours or when a significant change occurred. The incident was resolved when the status changed back to normal at 4:16 AM UTC.

RingCentral experienced a partial outage affecting outbound SMS messaging for a portion of customers with compliant outbound campaigns and number pools in the Americas. Customers could experience provisioning and message delivery delays, with provisioning delays up to 24 hours while RingCentral mitigated the issue. The disruption was limited to outbound SMS and did not indicate a global service failure. The impact was regional to the Americas.

The incident timeline: The outage began on Feb 7, 2025 9:31 PM UTC and was resolved by Feb 8, 2025 8:56 PM UTC. The provider issued 2 status updates during the incident and implemented mitigation actions to restore outbound SMS for compliant campaigns and number pools. Customers who were out of compliance were instructed to take necessary actions to join outbound SMS campaigns.

The SMS messaging issue began on 3:16 PM UTC when RingCentral reported that a portion of customers were experiencing SMS problems due to an underlying carrier. The impact started with outbound SMS in the Americas and later affected inbound SMS, with Europe seeing related login issues on 1:56 PM UTC as the incident evolved. The disruption impacted at least six components across Americas and EMEA, including Americas / SMS - Outbound, Americas / SMS - Inbound, Europe / Messaging, RingCX, Meetings - RingCentral Video, and Service Portal, hindering SMS delivery and related workflows. The outage persisted for roughly 3 days and 6 hours, from Feb 4, 2025 3:16 PM UTC to Feb 7, 2025 9:26 PM UTC, with users reporting text send failures and intermittent access to SMS features. The provider issued seven official updates during the incident and introduced a workaround for campaigns with fewer than 49 numbers registered to help some customers maintain messaging workflows.

RingCentral experienced an incident where a portion of RingCentral Contact Center customers could not load the agent portal, impacting users in the Americas and EMEA regions. The issue began at Jan 29, 2025 8:32 AM UTC and was resolved by Jan 29, 2025 1:01 PM UTC, lasting roughly 4 hours and 29 minutes. Affected components were Americas / Contact Center and EMEA / Contact Center.

During the event, RingCentral issued two status updates, documenting the progression from an initial issue to resolution. The affected regions returned to normal after remediation.