RingCentral Outage History

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 10:26 AM UTC and was resolved by 1:31 PM UTC, 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.

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 Jan 15, 2026 4:46 AM UTC, SMS inbound/outbound by Jan 15, 2026 8:36 AM UTC, and Calling inbound/outbound by Jan 15, 2026 4:41 PM UTC. The incident involved six official updates. User reports were limited, with at least one noting call drops.

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.

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 Jan 12, 2026 1:41 PM UTC and was resolved by Jan 12, 2026 3:11 PM UTC, 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.

RingCentral experienced a partial outage affecting number porting for a portion of customers in Australia. The issue was first listed at Jan 8, 2026 2:21 AM UTC as a carrier-related problem, with the underlying carrier investigating. The APAC / Other component was affected during this period, resulting in degraded service for affected users. The outage lasted approximately 6 hours and 25 minutes and was resolved by Jan 8, 2026 8:46 AM UTC.

Over the course of the incident, RingCentral posted 2 status updates detailing the ongoing investigation and restoration of services.

RingCentral reported intermittent outbound call failures affecting a portion of customers in the Americas. The issue impacted the Americas / Calling - Outbound component, causing some users to experience failed or blocked outbound calls. A workaround was suggested: place calls back-to-back to the same number, after which the call would go through. The provider issued 2 status updates during the incident, with the status moving from up to warn and then back to up. The outage lasted about 2 hours and 30 minutes, beginning at Jan 7, 2026 9:41 PM UTC and being resolved by Jan 8, 2026 12:11 AM UTC.

The RingCentral SMS service experienced a partial outage affecting a portion of customers in the Americas, with both inbound and outbound SMS paths impacted for SMS and MMS messages. A user in Oakland, California reported that text message notifications were not working. The incident began at Jan 5, 2026 4:41 PM UTC and was resolved by Jan 5, 2026 8:06 PM UTC, lasting approximately 3 hours and 25 minutes. The provider issued two status updates during the incident as investigation progressed and service was restored.

The affected components were Americas / SMS - Inbound and Americas / SMS - Outbound, and the outage was characterized as a partial outage in the Americas region.

RingCentral reported a partial outage impacting inbound and outbound calling in the RingCentral MiCloud service for customers in the Americas. Some users could not make or receive calls due to certain endpoints being unavailable. The outage began at Jan 5, 2026 4:36 AM UTC and was resolved by Jan 5, 2026 5:46 AM UTC, lasting about 1 hour and 10 minutes. The incident affected the Americas / Calling - Inbound and Americas / Calling - Outbound components.

A portion of RingCentral customers experienced failures in inbound and outbound calls and RingCX functionality. The disruption affected multiple regions, including Americas, EMEA, and APAC, and impacted 12 components spanning RingCX, Calling (Inbound/Outbound), and Other services. Users reported degraded calling experiences and RingCX issues during the incident window. The outage began at 10:46 AM UTC and was resolved by 11:31 AM UTC.

A partial RingCentral RingCX outage affected a portion of customers in the Americas, with users unable to transfer or disconnect calls and inbound calls not being accepted. Some calls were routed to Ring No Answer during the incident. The outage began at 6:46 PM UTC and was resolved by 9:31 PM UTC, lasting approximately 2 hours and 45 minutes. The Americas RingCX component was impacted during this time.