Update - We are continuing to monitor for any further issues.
Jul 17, 2026 - 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, 2026 - 12:13 AEST
Identified - The issue has been identified and a fix is being implemented.
Jul 17, 2026 - 11:15 AEST

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
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.
Jul 18, 2026

No incidents reported today.

Jul 17, 2026

Unresolved incident: Network stability.

Jul 16, 2026
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
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
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
Jul 12, 2026
Completed - The planned upgrade to our core voice platform has now been completed successfully. This weekend's maintenance window finished within the advertised timeframe and all services are operating as expected on the new release.

The earlier attempt at this upgrade was postponed after pre-upgrade checks identified a small number of customers on older TLS configurations. We rolled back, contacted every affected customer directly with configuration guidance, and rescheduled. The upgrade has now proceeded without further issues.
What you need to do: Nothing, unless you've been contacted about updating your TLS configuration. If you have been contacted and haven't yet made the change, please action it at your earliest convenience.

If you're experiencing call or registration issues and haven't received our previous communication, please contact support.

Jul 12, 15:45 AEST
Update - We will be undergoing scheduled maintenance during this time.
Jul 6, 08:30 AEST
Update - We have elected to postpone this upgrade by one week.
During the upgrade process we identified a number of customers with outdated TLS security configurations that would have prevented them from making and receiving calls.

We have since rolled back to the previous version to restore full service.
Security is not a destination — it's a treadmill. TLS standards continue to evolve, and older configurations that worked previously may no longer meet current security requirements. To avoid further disruption, we are taking the time to communicate with all affected customers directly before proceeding. Advisories will be issued over the coming days with guidance on updating configurations.

The upgrade itself is ready and will proceed once affected customers have had the opportunity to make the necessary changes.

Jul 11, 02:00 AEST
Update - Maintenance Window: 4 July, 2026
Scheduled Start: 03:00 AEST
Expected Service Interruption: Approximately 5 minutes
Maintenance Window Allowance: Up to 15 minutes

We have elected to postpone this upgrade by one week.
While we do not anticipate any issues with the upgrade itself, the 03:00 AEST Saturday maintenance window was chosen specifically because it carries the minimum traffic disruption for our customers. To preserve that low-impact window, we will reschedule for the same time slot next Saturday rather than proceed sooner during higher-traffic hours.
We will confirm the new date and time shortly.

Jun 28, 10:40 AEST
Update - We did not proceed with this morning's upgrade. An unrelated issue was identified on supporting infrastructure ahead of the maintenance window, and out of caution we elected to postpone rather than proceed. The OpenSIPS upgrade itself remains ready to go. We will reschedule and confirm a new date shortly.
Jun 27, 04:03 AEST
Update - We will be undergoing scheduled maintenance during this time.
Jun 25, 08:19 AEST
Scheduled - We will be performing a planned upgrade to our core voice platform as part of our ongoing infrastructure improvement program.

The upgrade has been thoroughly tested in our environment over the past month and is a straightforward software version upgrade. It delivers ongoing platform improvements, enhanced stability, and ensures we remain on the latest supported release.

Maintenance Window: 27 June, 2026
Scheduled Start: 03:00 AEST
Expected Service Interruption: Approximately 5 minutes
Maintenance Window Allowance: Up to 15 minutes

During the maintenance window, customers will experience a brief interruption to voice services, including call establishment and registration, while the upgrade is completed. Existing calls in progress will also be affected.

Our engineering team will be actively monitoring the upgrade throughout the maintenance window, and services are expected to resume automatically once the upgrade is complete.

Jun 25, 08:00 AEST
Jul 11, 2026

No incidents reported.

Jul 10, 2026

No incidents reported.

Jul 9, 2026

No incidents reported.

Jul 8, 2026

No incidents reported.

Jul 7, 2026

No incidents reported.

Jul 6, 2026

No incidents reported.

Jul 5, 2026

No incidents reported.

Jul 4, 2026

No incidents reported.