All Systems Operational

About This Site

Learn more about status and outage updates from SIPcity.

SIPcity Calling Platform (Network) Operational
SIPcity Cloud PBX Operational
MySIPcity app Operational
90 days ago
100.0 % uptime
Today
Desktop app Operational
90 days ago
100.0 % uptime
Today
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.
Past Incidents
Feb 8, 2025

No incidents reported today.

Feb 7, 2025

No incidents reported.

Feb 6, 2025

No incidents reported.

Feb 5, 2025

No incidents reported.

Feb 4, 2025

No incidents reported.

Feb 3, 2025

No incidents reported.

Feb 2, 2025

No incidents reported.

Feb 1, 2025

No incidents reported.

Jan 31, 2025

No incidents reported.

Jan 30, 2025

No incidents reported.

Jan 29, 2025

No incidents reported.

Jan 28, 2025

No incidents reported.

Jan 27, 2025
Resolved - 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.

Jan 27, 21:00 AEDT
Jan 26, 2025

No incidents reported.

Jan 25, 2025

No incidents reported.