All Systems Operational

About This Site

Learn more about status and outage updates from SIPcity.

Uptime over the past 90 days. View historical uptime.
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
SMS Operational
90 days ago
99.97 % 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.

No incidents or maintenance related to this downtime.

Aug 1, 2026

No incidents reported today.

Jul 31, 2026

No incidents reported.

Jul 30, 2026

No incidents reported.

Jul 29, 2026

No incidents reported.

Jul 28, 2026

No incidents reported.

Jul 27, 2026

No incidents reported.

Jul 26, 2026

No incidents reported.

Jul 25, 2026

No incidents reported.

Jul 24, 2026

No incidents reported.

Jul 23, 2026

No incidents reported.

Jul 22, 2026

Service Disruption - WebServices
Resolved - Summary

Between approximately 09:00 and 12:30 AEST today, customers experienced call delays and app registration failures. Service has been restored.

What happened

A botnet attack originating from a legitimate wholesale customer generated a large volume of malicious traffic, overwhelming our infrastructure — including our website, app, and handset registration services.

Resolution

We identified the source quickly but were slow to escalate and isolate the customer's traffic via our WAF and firewall rules; the surge should have been quarantined as soon as it was detected. We've since updated our automated traffic defences to prevent a recurrence.

Apology

We apologise for the disruption. If you're still experiencing push notification registration issues, please contact support and reference 22-Jul-2026.
Jul 22, 13:24 AEST
SIPcity apps registration
Resolved - This incident has been resolved.
Jul 22, 12:27 AEST
Monitoring - A fix has been implemented and we are monitoring the results.
Jul 22, 11:30 AEST
Identified - The issue has been identified and a fix is being implemented.
Jul 22, 11:07 AEST

Jul 21, 2026

Double registration
Resolved - This incident has been resolved.
Jul 21, 11:50 AEST
Identified - We are aware that some customers are receiving duplicate inbound calls, where a single incoming call generates two INVITE legs to the endpoint. The second leg is presented on hold and must be manually hung up. An earlier restart of our SIP Gateway appeared to clear the issue, but it has now reoccurred. Our engineering team has identified the behaviour and is actively working on a permanent fix. We will provide a further update once the fix is deployed and validated.
Jul 21, 11:20 AEST

Jul 20, 2026

No incidents reported.

Jul 19, 2026

No incidents reported.

Jul 18, 2026

No incidents reported.

← Incident History Powered by Atlassian Statuspage