Use cases
Software Products E-commerce MSPs Schools Development & Marketing DevOps Agencies Help Desk
Company
Internet Status Blog Pricing Log in Get started free

RingCentral Outage History

Every past RingCentral outage tracked by IsDown, with detection times, duration, and resolution details.

There were 645 RingCentral outages since June 2023. The 218 outages from the last 12 months are summarized below, with incident details, duration, and resolution information.

Minor March 31, 2026

March 2026: A portion of customers in Barrie and Collingwood, Ontario, may be experiencing failing inbound calls and faxes

Detected Mar 31, 2026 7:58 AM EDT · Resolved Mar 31, 2026 9:46 AM EDT · Duration about 2 hours

RingCentral customers in Barrie and Collingwood, Ontario experienced failing inbound calls and faxes for 1.8 hours due to an underlying carrier issue. The incident affected inbound calling and fax services in the Americas region. Operations teams worked with the carrier to resolve the issue.

Minor March 31, 2026

March 2026: A portion of customers may experience delayed SMS messages delivery for toll-free numbers to destinations within the United States and Canada due to an underlying carrier issue.

Detected Mar 31, 2026 5:59 AM EDT · Resolved Mar 31, 2026 6:37 AM EDT · Duration 39 minutes

RingCentral experienced delayed SMS message delivery for toll-free numbers to US and Canada destinations due to an underlying carrier issue. The incident affected both inbound and outbound SMS services across the Americas region for 39 minutes. RingCentral Operations worked with the carrier to investigate and restore normal service.

Minor March 31, 2026

March 2026: A portion of Contact Center customers may be experiencing call refusals

Detected Mar 31, 2026 5:49 AM EDT · Resolved Mar 31, 2026 10:02 AM EDT · Duration about 4 hours

RingCentral Contact Center customers in the EMEA region experienced an issue where they were unable to accept incoming calls, resulting in call refusals. The incident affected call processing capabilities for a portion of Contact Center users over a 4.2-hour period. Operations teams implemented fixes and mitigation measures that stabilized call processing, with service returning to normal levels.

Minor March 30, 2026

March 2026: A portion of customers in Saint-Lambert, QC, may be experiencing incoming call and fax failures due to an underlying carrier issue.

Detected Mar 30, 2026 9:48 AM EDT · Resolved Mar 30, 2026 11:45 AM EDT · Duration about 2 hours

RingCentral customers in Saint-Lambert, Quebec experienced incoming call and fax failures for 2 hours due to an underlying carrier issue. The incident affected inbound calling and fax services in the Americas region. Operations teams worked with the carrier to resolve the issue.

Minor March 29, 2026

March 2026: A portion of RingCentral customers in Barrie, Beeton and Collingwood, Ontario, Canada may experience fast busy on inbound calls due to underlying carrier

Detected Mar 29, 2026 9:40 AM EDT · Resolved Mar 29, 2026 10:46 PM EDT · Duration about 13 hours

RingCentral customers in Barrie, Beeton, and Collingwood, Ontario, Canada experienced fast busy signals on inbound calls and faxes due to an underlying carrier issue. The incident affected inbound calling and fax services across multiple regions and lasted 13.1 hours. RingCentral worked with their underlying carrier to resolve the connectivity problem.

Minor March 28, 2026

March 2026: A portion of RingCentral customers may be experiencing SMS delivery delays.

Detected Mar 28, 2026 12:03 AM EDT · Resolved Mar 28, 2026 3:54 AM EDT · Duration about 4 hours

RingCentral experienced SMS delivery delays affecting outbound messaging for customers in the Americas region. The issue impacted a portion of customers who experienced delays in their outbound SMS messages being delivered. Operations teams investigated and mitigated the problem after 3.9 hours, with active monitoring continuing afterward.

Minor March 27, 2026

March 2026: A portion of customers in Ontario, Canada may be experiencing inbound call and fax failures due to an underlying carrier issue.

Detected Mar 27, 2026 1:49 PM EDT · Resolved Mar 27, 2026 10:49 PM EDT · Duration about 9 hours

RingCentral customers in Ontario, Canada experienced inbound call and fax failures for 9 hours due to an underlying carrier issue. The incident affected inbound calling and fax services in the Americas region. RingCentral operations teams worked with the carrier to resolve the issue, which was confirmed fixed after the carrier completed their investigation and remediation.

Minor March 27, 2026

March 2026: A portion of Contact Center customers in Europe may experience issues with chat functionality.

Detected Mar 27, 2026 9:20 AM EDT · Resolved Mar 27, 2026 10:48 AM EDT · Duration about 1 hour

A portion of RingCentral Contact Center customers in Europe experienced issues with chat functionality for 1.5 hours. The incident was classified as minor and affected the EMEA Contact Center components. RingCentral teams identified the root cause and implemented corrective actions to resolve the chat functionality problems.

Minor March 25, 2026

March 2026: A portion of customers may be experiencing delayed SMS messages due to an underlying carrier issue.

Detected Mar 25, 2026 3:19 AM EDT · Resolved Mar 25, 2026 3:59 AM EDT · Duration 40 minutes

RingCentral experienced delayed SMS messages for some customers in the Americas region due to an underlying carrier issue affecting both inbound and outbound SMS services. The carrier investigated and restored service after 40 minutes. RingCentral continued monitoring for additional issues following the resolution.

Minor March 24, 2026

March 2026: A portion of Contact Center customers may be experiencing login issues.

Detected Mar 24, 2026 9:21 AM EDT · Resolved Mar 24, 2026 2:27 PM EDT · Duration about 5 hours

A portion of RingCentral Contact Center customers in the Americas region experienced login issues for 5.1 hours. The incident affected customers' ability to access the Contact Center platform. RingCentral teams identified and implemented a fix after an initial proposed solution failed, ultimately resolving the login problems and restoring successful access.