There were 157 RingCentral outages since January 2025 which are summarized below, including incident details, duration, and resolution information.
RingCentral not working for you?
RingCentral not working for you?
Minor
: RingCentral India calls briefly impacted, resolved in 10 minutes
Detected by StatusGator:
Officially acknowledged:
Outage ended:
(10 minutes)
RingCentral reported a partial outage localized to India, affecting APAC / Calling - Inbound and APAC / Calling - Outbound. The issue began at and was resolved by , lasting roughly 10 minutes. RingCentral operations teams took mitigation steps to restore stability and monitored the situation as updates were provided. The provider issued 2 status updates during the incident.
Minor
: RingCentral partial outage affects Mitel desk phones and calling
Detected by StatusGator:
Officially acknowledged:
Outage ended:
(3 hours and 5 minutes)
The RingCentral incident affected Mitel phones rebooting, causing an inability to make and receive calls for a portion of customers in the Americas. The outage began at and was resolved by , lasting about 3 hours and 5 minutes. Affected components included Americas / Calling - Inbound, Americas / Calling - Outbound, and Americas / Phones - Deskphone. The provider issued 2 status updates during the incident, describing the investigation and later confirming restoration of services.
Minor
: RingCentral Canada calling outage disrupts inbound and outbound calls
Detected by StatusGator:
Officially acknowledged:
Outage ended:
(2 hours and 20 minutes)
A portion of RingCentral customers with numbers in Canada experienced inbound and outbound call failures, impacting voice communications for affected users. The incident began at and lasted for about 2 hours and 20 minutes, with service restored by . RingCentral Operations teams were investigating and provided updates on the status page, with Americas / Calling - Inbound and Americas / Calling - Outbound identified as impacted.
Two status updates were posted during the incident, and inbound/outbound calling returned to service after the final update.
Minor
: RingCentral inbound calls and portal updates partial outage
Detected by StatusGator:
Officially acknowledged:
Outage ended:
(6 hours and 35 minutes)
RingCentral experienced a partial outage affecting inbound calling and the ability to update incoming call rules on the Customer Portal for a portion of customers. The issue spanned multiple regions, impacting Americas and APAC inbound calling and related Fax outbound components, with EMEA affected as well. The outage began at and was resolved by , lasting roughly 6 hours and 35 minutes. During the window, users could experience failed inbound calls or be unable to modify call routing rules in the Customer Portal.
RingCentral's Operations teams issued nine status updates, confirming the issue, providing a workaround, and continuing mitigation. Updates indicated a workaround was available and that teams were working to fully mitigate the issue, with the service returning to normal after the final update at 22:31 UTC.
Minor
: RingCentral Video start issues impact meetings globally
Detected by StatusGator:
Officially acknowledged:
Outage ended:
(1 hour and 5 minutes)
RingCentral Video experienced a partial outage that prevented some users from starting video meetings, affecting RingCentral Video in the Americas, EMEA, and APAC regions. RingCentral said a portion of customers may be unable to start video meetings and that their Operations teams were investigating. The outage began at and was resolved by , lasting about 1 hour 5 minutes. The outage impacted the Americas / Meetings - RingCentral Video, EMEA / Meetings - RingCentral Video, and APAC / Meetings - RingCentral Video components.
Two status updates were published during the incident: the first at 13:06 UTC indicating an investigation and potential impact to video meetings, and the second at 14:11 UTC confirming resolution and restoration of services.
Minor
: RingCentral toll-free numbers outage hits Contact Center users (EMEA)
Detected by StatusGator:
Officially acknowledged:
Outage ended:
(2 hours)
The toll-free number service for a portion of RingCentral's Contact Center customers in the EMEA region experienced an outage, causing toll-free calls to fail for affected accounts. The incident began on and lasted until , for a total duration of about 2 hours and 1 minute. RingCentral's Contact Center teams opened an investigation to determine the cause and work toward a fix.
The provider issued two official status updates during the incident, and toll-free functionality returned to normal by . The outage affected a subset of customers within the EMEA region using RingCentral's Contact Center toll-free functionality.
RingCentral experienced a partial outage affecting RingCX login for a portion of customers in the Americas region. The issue began at when RingCentral Operations announced they were investigating login problems and would provide updates as they became available. Users may have experienced sign-in difficulties or inability to access RingCX features during this period. The outage was resolved by , lasting approximately 1 hour and 34 minutes.
Minor
: RingCentral Contact Center login issues and slow performance (Americas)
Detected by StatusGator:
Officially acknowledged:
Outage ended:
(50 minutes)
RingCentral's Americas Contact Center experienced login issues and slow platform performance affecting a portion of customers. The incident began at and RingCentral's Contact Center teams began investigating the issue.
RingCentral issued 2 status updates during the incident. The issue was resolved by , and the Americas Contact Center component returned to normal operation. The outage lasted approximately 49 minutes.
Minor
: RingCentral Contact Center login issues brief outage
Detected by StatusGator:
Officially acknowledged:
Outage ended:
(20 minutes)
RingCentral's Contact Center users in the Americas experienced a brief outage affecting login and contact delivery for a portion of customers. The issue began at and was resolved by , lasting roughly 20 minutes. The incident appeared localized to the Americas / Contact Center component rather than global.
RingCentral published two status updates during the incident. The initial update noted investigation and indicated that a follow-up update would be provided in up to four hours or sooner if there were significant changes; about 20 minutes later, the status returned to normal and service resumed for affected customers.
Minor
: RingCentral Twitter/X messaging issue affects RingCX and Engage Digital
Detected by StatusGator:
Officially acknowledged:
Outage ended:
(4 hours and 10 minutes)
The outage affected a portion of RingCentral's Engage Digital and RingCX customers who were unable to send messages on Twitter/X. The issue was centered in the Americas region, impacting three components: Americas / RingCX, Americas / Engage Digital - Digital AWS, and Americas / Engage Digital - Digital Claranet. The problem began at and was resolved by , lasting approximately 4 hours and 10 minutes. Users may have experienced failures or delays when attempting to send messages on Twitter/X during the window.