Real World Technology Solutions had 12 outages in the last 2 years totaling 51h 38m of downtime — averaging 0.5 incidents per month.
There were 12 Real World Technology Solutions outages since November 27, 2025 totaling 51h 38m of downtime. Each is summarised below — incident details, duration, and resolution information.
We are currently aware of registration issues when using the CloudPBX Desktop application. Engineers are current working on a fix to restore full performance on the application.
Engineers have applied a fix and testing shows fully restored performance on the CloudPBX desktop softphone application.
We have resolved a CloudPBX instability that affected client registration for a small number of requests and some data reporting.
This incident has been resolved.
Earlier this morning a backup process interrupted a database node as part of the CloudPBX system. In this database state, the database node continued to accept connections, but was unable to service them leading to stuck queries, updates and transactions. Because the node was acting like it was alive, the mechanisms that usually handle node failures did not work. The affected node was taken offline and the underlying issues were addressed in relation to the backup process which caused the issue, and the node was recovered. In addition, we’ve identified an improved way of detecting node availability that covers all existing scenarios, including this one, and have implemented this. The incident affected traffic on approximately 30% of requests on two CloudPBX home servers, approximately 4% of users.
Customers using our Ivanti VPN service are currently unable to log in due to a platform issue. This has been raised with Ivanti who have allocated resources to it. At 2:37am an update was received indicating that they anticipated an “expedited” resolution, however we have not received any updates since then. Our team will continue to follow up with Ivanti for next steps in the resolution process.
Ivanti has provided a resolution which has now been applied and tested, resolving this incident. We thank you for your patience.
Our team are working to address an issue impacting authentication to the CloudPBX Administration Interface. Next update in approximately 15 minutes.
CloudPBX Admin Authentication has been restored.
Due to changes in the SSL Certificate Issuance, this systems were migrated to dynamic SSL Certificate issuance. Unfortunately an error in the renewal hooks prevented the systems from correctly applying the certificates post renewal. This has been rectified.
We are currently aware of delayed call connections with CloudPBX Desktop application. This is affecting both inbound and outbound calling. Engineers are current working on a fix to restore full performance on the application.
Engineers have applied a fix and testing shows fully restored performance on the CloudPBX desktop application.
Engineers have identified and are investigating a critical hardware failure within our CloudPBX infrastructure.
This incident has been resolved.
At approximately 9:10am, a server hosting some of your CloudPBX services experienced a hardware failure. Normally, our systems recover from this kind of event automatically — but the nature of this particular failure prevented that from happening. Our engineers identified the issue quickly and began manual recovery. We rebooted the affected server, moved your CloudPBX services to a separate cluster, and confirmed everything was back up and running by approximately 9:53am. We then restarted the connected home servers to make sure no leftover issues from the failure could cause further problems. We've since moved these resources permanently so they're no longer dependent on the hardware that failed. We're sorry for the disruption to your morning. If you're still experiencing any issues, please give us a call on 1300 798 718.
We are currently investigating an issue affecting web hosting on some of our platforms.
The issue has been identified and a fix is being implemented.
This incident has been resolved.
Engineers have identified an issue with some CloudPBX inbound numbers currently failing. Our team is actively working on a resolution and any updates will be provided here.
Engineers have resolved the issue. Any further issues should be reported.
We experienced a disruption to our CloudPBX platform this morning due to a regular database maintenance operation that processed incorrectly. Engineers recovered the database system and returned the system to normal operation. Customers may have been unable to make or receive calls from approximately 1:15am until 1:48am due to this issue. We have identified the issue and will be performing preventative maintenance over the coming days to remove the risk of a reoccurrence.
We are investigating where some calls are failing after ~30 seconds
We've identified an issue affecting calls with certain versions of the CloudPBX App and are working on a fix.
We are continuing to work on a fix for this issue.
What happened: Some voice calls were disconnecting approximately 30 seconds after being answered. Who was affected: A subset of users connecting through certain network configurations (carrier-grade NAT). Root cause: A network address handling routine was not correctly processing connection details for some network topologies, causing call signalling to be misdirected due to a change to enhance logging for certain transactions. Resolution: Configuration updates have been applied to correctly handle all NAT scenarios. Normal service has been restored.
We are currently investigating a service interruption affecting services in our syd02 data hall.
A fix has been implemented, and we are monitoring the results. Some services may require a restart to restore connectivity.
This incident has been resolved.
We have implemented a rolling restart of the affecting infrastructure and restored connectivity. We are now investigating issues relating to individual services.
We have implemented a rolling restart of the affecting infrastructure and restored connectivity. We are now investigating issues relating to individual services.
This incident has been resolved.