Rival5 Outage History

Rival5 is up right now

Rival5 had 7 outages in the last 2 years — averaging 0.3 incidents per month.

There were 7 Rival5 outages since September 18, 2024. Each is summarised below — incident details, duration, and resolution information.

Source: https://www.rival5status.com

Minor October 24, 2025

Intermittent service interruption

Detected by Pingoru
Oct 24, 2025, 02:37 PM UTC
Resolved
Oct 24, 2025, 02:37 PM UTC
Duration
Timeline · 1 update
  1. resolved Oct 24, 2025, 02:37 PM UTC

    Type: Incident Duration: 2 hours and 4 minutes Affected Components: RCom Unified Communications Hosted PBX Instances Oct 24, 16:40:37 GMT+0 - Resolved - We have resolved the issues with the affected virtualization node within our network that the affected customers instances are housed on. These customers have submitted tickets with our team and will be updated accordingly in the respective channels. Thank you for your patience and understanding. Oct 24, 14:37:00 GMT+0 - Investigating - Intermittent service interruption. We are experiencing intermittent service interruptions. This is only affecting a few customers, and we are aware of the issue. Our team is researching the cause and working to resolve the issue.

Read the full incident report →

Minor October 3, 2025

Brief Service Interruption on Subset of Infrastructure

Detected by Pingoru
Oct 03, 2025, 04:15 PM UTC
Resolved
Oct 03, 2025, 04:15 PM UTC
Duration
Timeline · 1 update
  1. resolved Oct 03, 2025, 04:15 PM UTC

    Type: Incident Duration: 20 minutes Affected Components: RCom Unified Communications Hosted PBX Instances Oct 3, 16:15:00 GMT+0 - Investigating - Hello, we are investigating a brief service interruption on a subset of infrastructure comprising our RCom Hosted PBX instances. Oct 3, 16:35:00 GMT+0 - Resolved - Affected hosts and systems comprising our infrastructure have been re-initalized within our core virtualization platform and service availability should be restoring. As of this notification at 11:35, all affected instances are now back in service and have returned to normal device registration levels.

Read the full incident report →