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
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.

Jun 19, 2025

No incidents reported today.

Jun 18, 2025

No incidents reported.

Jun 17, 2025

No incidents reported.

Jun 16, 2025

No incidents reported.

Jun 15, 2025

No incidents reported.

Jun 14, 2025

No incidents reported.

Jun 13, 2025

No incidents reported.

Jun 12, 2025
CloudPBX - Important Update:
Resolved - This incident has been resolved.
Jun 12, 12:00 AEST
Monitoring - A fix has been implemented and we are monitoring now.
Jun 12, 10:15 AEST
Identified - Our team has identified a potential security issue and, as a precaution, we’ve temporarily taken the CloudPBX portal offline to apply a critical update.

We’re working to restore access as quickly as possible and expect services to be back online shortly. Thank you for your patience and understanding.
Jun 12, 10:01 AEST
Jun 11, 2025
Registration issue
Resolved - This incident has been resolved.
Jun 11, 09:20 AEST
Monitoring - A fix has been implemented and we are monitoring the results.
Jun 10, 14:19 AEST
Investigating - We are currently investigating this issue.
Jun 10, 14:05 AEST
Jun 10, 2025
SIP Gateway Degradation Due to Load Balancer Instability
Resolved - Incident Summary – Monday, 10 June

On Monday, 10 June, we experienced a service degradation affecting our primary SIP gateway, resulting in a brief interruption to inbound calling. The issue was caused by human error during the rollout of a new monitoring process, which inadvertently introduced instability into our high-availability load balancing systems.

The root cause was identified and mitigated quickly; however, the disruption impacted several critical load-balancing components before full service was restored.

While we typically avoid deploying changes during business hours, a security event on 7 June — a Distributed Denial of Service (DDoS) and credential stuffing attack — necessitated the urgent release of an emergency patch, which led to the unscheduled deployment and this incident.

We apologise for the disruption and appreciate your understanding as we continue to improve the resilience of our platform.
Jun 10, 02:00 AEST
Jun 9, 2025

No incidents reported.

Jun 8, 2025

No incidents reported.

Jun 7, 2025

No incidents reported.

Jun 6, 2025
Incident Summary – Friday, 7 June - Distributed Denial of Service (DDoS) and Credential Stuffing Attack
Resolved - On Friday, 7 June, we experienced a distributed denial of service (DDoS) attack combined with a credential stuffing brute-force attempt. The attack originated from over 6,000 IP addresses, associated with a Canadian ISP, and targeted our authentication endpoints at a sustained rate of requests per second.

Our monitoring systems quickly detected the abnormal traffic patterns and elevated failure rates, triggering automated protection mechanisms.

In response, we implemented aggressive IP bans and temporarily disabled all authentication requests — including legitimate ones — until the malicious traffic was isolated and contained. While core voice services remained unaffected, some auxiliary systems, including faxing and email notifications, were inadvertently added to the banned IP jail. This misclassification was not identified for approximately 24 hours.

As a result, a small number of inbound faxes during this window were lost and are unfortunately unrecoverable.

We continue to actively monitor for further attacks and are implementing additional safeguards to harden our authentication infrastructure and improve service resilience.
Jun 6, 19:00 AEST
Jun 5, 2025

No incidents reported.

← Incident History Powered by Atlassian Statuspage