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.

Jul 27, 2026

No incidents reported today.

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.

Jul 17, 2026
Network stability
Resolved - This incident has been resolved.
Jul 17, 14:30 AEST
Update - We are continuing to monitor for any further issues.
Jul 17, 12:13 AEST
Monitoring - On 17 July 2026, customers on the AU platform experienced call timeouts and failures on PSTN calls. Some also saw delayed or failed SIP device registration. Today, a brief follow-on outage occurred as the CEPH cluster completed its recovery from yesterday's incident.

Cause
A log rotation script that should have deleted transcribed voicemail messages stopped running. Messages accumulated on our shared storage layer (CEPH) until it neared capacity and began blocking writes. This starved other services sharing that storage, including the SIP proxies that set up PSTN calls.

What is CEPH?
CEPH is a distributed storage platform that unifies block, file, and object storage. It pools disks across ordinary servers into a fault-tolerant cluster: if a disk or server fails, data is recomputed and redistributed from surviving copies automatically. That resilience comes at a cost — CEPH can become a bottleneck at scale.

What we're doing about it
Since May we've been separating core voice and network services from CEPH: removing CEPH as the backing store for the voice network entirely, and upgrading from mechanical drives to server-class SSDs. That project is in its final weeks. Once complete, storage growth from voicemail or recordings will no longer be able to affect call setup or SIP services.

On a brighter note
Today I released Voice AI agents, running on our own private GPU cluster in Sydney, and our desktop client now includes a full call centre system, with video conferencing across desktop and mobile scheduled for release later this month.
Jul 17, 12:13 AEST
Identified - The issue has been identified and a fix is being implemented.
Jul 17, 11:15 AEST
Jul 16, 2026
Interrupted calling
Resolved - This incident has been resolved.
Jul 16, 17:02 AEST
Monitoring - A fix has been implemented and we are monitoring the results.
Jul 16, 16:57 AEST
Identified - The issue has been identified and a fix is being implemented.
Jul 16, 16:10 AEST
Calling outage
Resolved - This incident has been resolved.
Jul 16, 15:04 AEST
Investigating - We are currently investigating this issue.
Jul 16, 14:49 AEST
Jul 15, 2026

No incidents reported.

Jul 14, 2026

No incidents reported.

Jul 13, 2026
Scheduled Maintenance Notice
Update - The scheduled maintenance has been completed.
Jul 13, 12:05 AEST
Completed - The scheduled maintenance has been completed.
Jul 13, 12:01 AEST
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jul 13, 12:00 AEST
Scheduled - This weekend we completed an upgrade to our core SIP gateway. While the upgrade itself was successful, we identified that one of the supporting monitoring services did not restart correctly.

Although customer services are operating normally, this monitoring service is essential for our Network Operations team to effectively monitor and diagnose any issues. To restore full operational visibility, we will be performing a brief restart of the SIP gateway during the lunchtime period when call volumes are at their lowest.

We expect the interruption to be brief and apologise for any inconvenience this may cause. This maintenance has been scheduled to minimise customer impact while ensuring the continued reliability of the SIPcity platform.

Expected impact: Brief interruption to calling services during the maintenance window.
Reason: Restoration of a critical monitoring service following a successful gateway upgrade.
Status: Scheduled Maintenance.
Jul 13, 11:31 AEST
← Incident History Powered by Atlassian Statuspage