There were 156 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 RingCX partial outage affects login and calling
Detected by StatusGator:
Officially acknowledged:
Outage ended:
(4 hours)
A partial outage impacted RingCentral RingCX login and calling for a portion of customers across APAC, Americas, and EMEA. The issue began at and was resolved by , 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.
Minor
: RingCentral partial calling outage impacts select Canadian regions
Detected by StatusGator:
Officially acknowledged:
Outage ended:
(2 hours and 50 minutes)
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 and was resolved by , 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.
Minor
: RingCentral inbound/outbound call failures in Thetford Mines, QC
Detected by StatusGator:
Officially acknowledged:
Outage ended:
(2 hours and 40 minutes)
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 and was resolved by , 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.
Minor
: RingCentral SMS delays in Americas briefly affect users
Detected by StatusGator:
Officially acknowledged:
Outage ended:
(10 minutes)
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 and was resolved by . 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.
Minor
: RingCentral SMS delays and regional inbound call/fax failures
Detected by StatusGator:
Officially acknowledged:
Outage ended:
(4 days, 1 hour and 25 minutes)
The incident began at 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 and again at , 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 , 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 to .
Minor
: RingCentral RingCX partial outage hits Ring No Answer in Americas and EMEA
Detected by StatusGator:
Officially acknowledged:
Outage ended:
(6 hours and 45 minutes)
A portion of RingCentral RingCX customers experienced Ring No Answer and were unable to take calls, starting around 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 , with continued mitigation as the rollback progressed. EMEA recovered by , and the Americas region recovered by . 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.
Minor
: RingCentral Canada outbound fax impacted by carrier issue
Detected by StatusGator:
Officially acknowledged:
Outage ended:
(3 hours and 5 minutes)
The RingCentral status page indicated a partial outage affecting outbound faxes to toll-free numbers for some Canadian customers due to an underlying carrier problem. The issue affected the Americas / Fax - Outbound component. The outage began at and was resolved by , lasting about 3 hours and 5 minutes. RingCentral issued 2 status updates during the incident as teams worked with the carrier to restore service. The impact was limited to outbound fax to toll-free numbers in Canada; other RingCentral services were not indicated as affected.
Minor
: RingCentral outage hits Ontario 519 area inbound calls and fax
Detected by StatusGator:
Officially acknowledged:
Outage ended:
(1 day)
A partial RingCentral outage affected inbound calls and fax for Ontario, Canada numbers in the 519 area code. The impact expanded to SMS inbound and outbound later in the incident, with users reporting call failures. RingCentral attributed the disruption to an underlying carrier issue and issued multiple status updates as the situation was investigated and mitigated. The outage spanned roughly 24 hours and affected several components in the Americas region, including Fax Inbound, Calling Inbound, SMS Inbound, SMS Outbound, and Calling Outbound. Recovery timelines show Fax Inbound resolved by , SMS inbound/outbound by , and Calling inbound/outbound by . The incident involved six official updates. User reports were limited, with at least one noting call drops.
Minor
: RingCentral Contact Center login issue in Americas resolved
Detected by StatusGator:
Officially acknowledged:
Outage ended:
(1 hour and 40 minutes)
A portion of RingCentral Contact Center customers in the Americas experienced their applications failing to load after logging in, causing login-related disruptions for users accessing the Contact Center. RingCentral's Contact Center teams began investigating immediately and pledged an update in about four hours as more information became available. The incident involved the Americas / Contact Center component, which briefly degraded before returning to normal.
Minor
: RingCentral EMEA contact center routing partial outage
Detected by StatusGator:
Officially acknowledged:
Outage ended:
(1 hour and 30 minutes)
RingCentral reported a partial outage impacting its EMEA Contact Center, with digital chat contacts not routing automatically for a portion of customers. The outage began at and was resolved by , lasting about 1 hour and 30 minutes. The issue affected the EMEA / Contact Center component and disrupted automatic routing of digital contacts.
The RingCentral status page published two updates during the incident, noting the issue and that teams were investigating to restore routing. The affected component returned to normal by the end of the incident.
