Reinvent Telecom Outage History

Reinvent Telecom is up right now

Reinvent Telecom had 8 outages in the last 2 years totaling 31h 7m of downtime — averaging 0.3 incidents per month.

There were 8 Reinvent Telecom outages since June 4, 2025 totaling 31h 7m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.reinventtelecom.com

Minor May 1, 2026

Call Impairment

Detected by Pingoru
May 01, 2026, 12:26 PM UTC
Resolved
May 01, 2026, 04:04 PM UTC
Duration
3h 37m
Affected: Inbound NationalOutbound NationalToll-Free
Timeline · 6 updates
  1. investigating May 01, 2026, 12:26 PM UTC

    We are currently investigating an issue on calls that may have no audio. We are working the issue at this time and will follow up with updates as they become available.

  2. identified May 01, 2026, 12:58 PM UTC

    The issue has been identified and we are working on a solution at this time.

  3. identified May 01, 2026, 01:01 PM UTC

    Please join our Partner Conference Bridge for live updates. Toll-Free: +1 (800) 309-2350 Conference ID: 117-0584

  4. monitoring May 01, 2026, 01:23 PM UTC

    A fix has been applied and we are monitoring at this time. RTP is flowing at this time.

  5. resolved May 01, 2026, 04:04 PM UTC

    After continuous monitoring all results have been positive and calls are completing as expected with RTP. We are resolving this intendent.

  6. postmortem May 01, 2026, 06:13 PM UTC

    Following the successful completion of the scheduled cutover for Sinch, Bandwidth, and ThinQ to cCFS, two separate voice service issues were reported the morning of May 1, 2026. The first issue resulted in one-way audio and was caused by a routing issue between the Chicago Secondary SBC and cCFS. The routing issue was identified at approximately 06:05 MST and corrected by approximately 06:12 MST, restoring call audio. The second issue affected some inbound calls over Bandwidth and was determined to be related to SBC call policy settings that required adjustment following the cutover. The policy issue was identified at approximately 07:35 MST and resolved by approximately 07:45 MST. Resolution was confirmed through testing and partner ticket validation at approximately 07:48 MST.

Read the full incident report →

Major March 3, 2026

Degraded Voice

Detected by Pingoru
Mar 03, 2026, 02:01 PM UTC
Resolved
Mar 03, 2026, 04:44 PM UTC
Duration
2h 43m
Affected: Inbound NationalOutbound National
Timeline · 5 updates
  1. investigating Mar 03, 2026, 02:01 PM UTC

    We are currently investigating a voice impairment issue. We will update as more information is available.

  2. identified Mar 03, 2026, 02:20 PM UTC

    We have identified the issue with the carrier and we are working for resolution at this time. More information will follow when available.

  3. identified Mar 03, 2026, 02:31 PM UTC

    The identified carrier is still investigating the issue at this time.

  4. monitoring Mar 03, 2026, 03:01 PM UTC

    Teams are observing expecting Inbound and Outbound Call patterns and network behavior. We will continue to monitor for prolonged stability.

  5. resolved Mar 03, 2026, 04:44 PM UTC

    After continuous monitoring with the carrier all calls are stable. We consider this matter resolved.

Read the full incident report →

Minor December 11, 2025

ORD/PHL Voice Degradation

Detected by Pingoru
Dec 11, 2025, 08:31 PM UTC
Resolved
Dec 12, 2025, 05:10 AM UTC
Duration
8h 39m
Affected: Inbound NationalOutbound NationalToll-Free
Timeline · 3 updates
  1. identified Dec 11, 2025, 08:31 PM UTC

    We have identified an issue with an L3 primary circuit. We have move traffic over to secondary and traffic has stabilized. This only affected our ORD/PHL datacenters.

  2. identified Dec 11, 2025, 08:34 PM UTC

    We are continuing to work on a fix for this issue.

  3. resolved Dec 12, 2025, 05:10 AM UTC

    Lumen has reported that the impairment with their service has been resolved, and traffic is flowing normally over the primary circuit. This incident is resolved.

Read the full incident report →

Major November 18, 2025

RPP Impairment

Detected by Pingoru
Nov 18, 2025, 01:22 PM UTC
Resolved
Nov 18, 2025, 04:09 PM UTC
Duration
2h 46m
Affected: Call RecordingFax ServicesIntermediaReInvent Partner Portal (RPP)
Timeline · 5 updates
  1. investigating Nov 18, 2025, 01:22 PM UTC

    We are currently investigating an issue with our RPP platform. More information will follow as it becomes available.

  2. identified Nov 18, 2025, 01:40 PM UTC

    The impairment has been identified as a global issue with Cloudflare services. This will also affect our Hosted Faxing and call recording on the Metaswitch Platform.

  3. identified Nov 18, 2025, 02:20 PM UTC

    CloudFlare at this time is still working for a resolution on this Global issue.

  4. monitoring Nov 18, 2025, 02:41 PM UTC

    Clouflare has deployed a fix and services are recovering at this time. We will continue to monitor as the recovery may be a slow role out.

  5. resolved Nov 18, 2025, 04:09 PM UTC

    All Reinvent services are stable and remain accessible. We consider this matter closed.

Read the full incident report →

Major November 7, 2025

Hosted Fax Impairment

Detected by Pingoru
Nov 07, 2025, 01:47 PM UTC
Resolved
Nov 07, 2025, 04:08 PM UTC
Duration
2h 20m
Affected: Fax Services
Timeline · 5 updates
  1. investigating Nov 07, 2025, 01:47 PM UTC

    We are currently investigating an issue with our Hosted Fax server. We will update as more information is available.

  2. identified Nov 07, 2025, 02:01 PM UTC

    We have identified the issue for the Hosted Fax service and are implementing solutions at this time. Updates will follow.

  3. identified Nov 07, 2025, 02:34 PM UTC

    We are working with the vendor at this time to restore services.

  4. monitoring Nov 07, 2025, 02:58 PM UTC

    A fix has been implemented and services are restored we will continue to monitor.

  5. resolved Nov 07, 2025, 04:08 PM UTC

    After careful monitoring system feature are behaving normally. This incident is resolved.

Read the full incident report →

Minor October 22, 2025

Metaview Web Imparment

Detected by Pingoru
Oct 22, 2025, 03:01 PM UTC
Resolved
Oct 22, 2025, 06:58 PM UTC
Duration
3h 57m
Affected: Inbound NationalCommPortalMetaview Web
Timeline · 8 updates
  1. investigating Oct 22, 2025, 03:01 PM UTC

    We are currently investigating an issue with Metaview Web Access. This is just affecting Metaview at this time. Calls are completing as expected.

  2. investigating Oct 22, 2025, 03:20 PM UTC

    We are also investigating an impairment of Inbound calling for Auto Attendants and ICM's. We will update as more information is available.

  3. investigating Oct 22, 2025, 03:42 PM UTC

    As a service to our Partners we are activating our Partner Bridge. This will allow you to stay up to date on the current situation. If you would like to join please read below for access. Toll Free: 800-309-2350 Conference Bridge ID: 1170584

  4. identified Oct 22, 2025, 04:10 PM UTC

    We have identified the impairment and we are with the vendor at this time. Updates will be provided when available.

  5. identified Oct 22, 2025, 04:32 PM UTC

    We have identified the impairment and we are with the vendor at this time. Updates will be provided when available.

  6. identified Oct 22, 2025, 05:09 PM UTC

    We are currently applying a fix at this time and awaiting the results. More updates to follow as they are available.

  7. monitoring Oct 22, 2025, 05:58 PM UTC

    A fix has been applied and we are seeing connections now stable We will continue to monitor.

  8. resolved Oct 22, 2025, 06:58 PM UTC

    This incident is now resolved. If you experience any issues please reach out to support. Thank you for your patience in this matter.

Read the full incident report →

Major October 1, 2025

Dropped Calls Reported MCU Platform

Detected by Pingoru
Oct 01, 2025, 01:15 PM UTC
Resolved
Oct 01, 2025, 05:22 PM UTC
Duration
4h 6m
Affected: Outbound NationalMyCloud Inbound National
Timeline · 8 updates
  1. investigating Oct 01, 2025, 01:15 PM UTC

    We are currently investigating an issue with dropped calls on our MCU Platform. Updates will follow as information is available.

  2. investigating Oct 01, 2025, 01:45 PM UTC

    We are continuing to research the issue at this time. Updates will follow when available.

  3. investigating Oct 01, 2025, 02:10 PM UTC

    We have discovered in our process that call queues are affected only. Direct calls to customer will process as normal. We are still in investigating the issue.

  4. investigating Oct 01, 2025, 02:39 PM UTC

    We are continuing to research the issue at this time. Updates will follow when available.

  5. identified Oct 01, 2025, 03:04 PM UTC

    We have identified the issue and we are working with our vendor at this time. Updates will follow as they are readily available.

  6. identified Oct 01, 2025, 03:40 PM UTC

    We are currently still working with the vendor at this time.

  7. monitoring Oct 01, 2025, 04:15 PM UTC

    A fix has been implemented with positive feedback and we are monitoring the results. If you experience any issues please notify us.

  8. resolved Oct 01, 2025, 05:22 PM UTC

    All testing has produced positive results after fix was put in place. We are considering this impairment resolved.

Read the full incident report →

Minor June 4, 2025

MCU Calling Anomalies

Detected by Pingoru
Jun 04, 2025, 04:18 PM UTC
Resolved
Jun 04, 2025, 07:13 PM UTC
Duration
2h 54m
Affected: MyCloud Inbound NationalMyCloud Toll-Free
Timeline · 5 updates
  1. investigating Jun 04, 2025, 04:18 PM UTC

    We are currently investigating inbound calling anomalies with in our MCU Platform. More information to follow as it becomes available.

  2. identified Jun 04, 2025, 04:50 PM UTC

    The issue has been identified and we are working to a fix at this time. More information to follow as it becomes available.

  3. identified Jun 04, 2025, 05:40 PM UTC

    We are currently still working on a fix with the issue identified for the MCU Platform. More updates will follow as they are available.

  4. monitoring Jun 04, 2025, 06:01 PM UTC

    A fix was implemented and we are monitoring the results. If you experience any issue please do no hesitate to reach out to our support team.

  5. resolved Jun 04, 2025, 07:13 PM UTC

    We have monitored the fix and all has been verifying stable at this time. Closing this incident.

Read the full incident report →