Rival5 experienced a major incident on May 27, 2025, lasting —. The incident has been resolved; the full update timeline is below.
Update timeline
- resolved May 27, 2025, 03:31 PM UTC
Type: Incident Duration: 1 hour and 44 minutes Affected Components: Emergency / 911 Call Routing, Termination (Outbound) Calling, International Calling, , RCom Unified Communications Hosted PBX Instances, Origination (Inbound) Calling, Toll-Free Origination (Inbound) Calling, RVoice Telecom Service → May 27, 15:31:00 GMT+0 - Identified - Rival5 engineering and networking teams have identified a storage latency issue causing an unreliable connection to our storage network infrastructure within our primary data center beginning this morning, 05/27/25, at 10:31 AM. This incident is backdated. Another latency event occurred at 11:04 AM. This storage latency exhibits instance unavailability for some customers' devices, apps, and other endpoints to connect reliably and remain connected to our infrastructure. Rival5 has engaged storage and network resources within our private cloud provider's organization for assistance in troubleshooting and rectifying the issue. Rival5 will continue updating and working with customers that have submitted a ticket reporting issues this morning, but this incident will serve as a overarching communication path for updates for those customers that have yet to open a support ticket. If you have any questions or concerns, please reach out to our support team at . May 27, 17:14:59 GMT+0 - Resolved - Rival5 is continuing to monitor this storage latency closely. There have been no observed latency events since 11:04 AM. We are closing out this active incident. Rival5 will continue working with our private cloud provider in the background on the triage case in progress, and exploring alternative connectivity methods to our storage network.