YourCloudTelco incident

Degraded calling

Notice Resolved View vendor source →

YourCloudTelco experienced a notice incident on January 31, 2025, lasting —. The incident has been resolved; the full update timeline is below.

Started
Jan 31, 2025, 12:02 AM UTC
Resolved
Jan 27, 2025, 10:00 AM UTC
Duration
Detected by Pingoru
Jan 31, 2025, 12:02 AM UTC

Update timeline

  1. resolved Jan 31, 2025, 12:02 AM UTC

    Incident Summary: On January 31, 2025, a voice server (OpenSIPS) experienced severe performance degradation due to excessive CPU utilisation, resulting in impaired call handling capabilities. The incident was resolved through a service restart. Timeline: 9:30 PM: Initial spike in outbound calls observed 10:00 AM: Beginning of a significant decrease in call volume 11:45 AM: Continued service degradation 12:00 AM: Service restored following OpenSIPS restart Impact: Reduced capacity to handle inbound and outbound calls Noticeable decrease in successful call completions No complete service interruption, but severely degraded performance Root Cause: The OpenSIPS server experienced CPU utilisation reaching 99%, severely impacting its ability to process calls efficiently. While the service remained running, it was effectively non-responsive due to the excessive load. Resolution: The immediate issue was resolved by restarting the OpenSIPS service at 12:00 AM AEDT. Following the restart, normal service operation resumed with CPU usage returning to expected levels.