Real World Technology Solutions Outage History

Real World Technology Solutions degraded View live status →

Pingoru has recorded 50 incidents for Real World Technology Solutions: 14 in the last 12 months and 2 in the last 90 days.

Source: status.rwts.com.au

50incidents recorded
14last 12 months
2last 90 days
6 hourstypical duration
Incidents per month
012AprMayJunJulAugSepOct1
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct4%
Pingoru began tracking Real World Technology Solutions in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 202610 of 720 (0%)
May 202612 of 744 (0%)
June 2026113 of 720 (2%)
July 202611 of 744 (0%)
August 202600 of 744 (0%)
September 202600 of 720 (0%)
October 2026123 of 523 (4%)

Incidents, newest first

Notice October 21, 2026 PHP Security Vulnerability CVE-2026-109618 / CVE-2026-109619 22h 34m Virtual Machine Hosting, Web Hosting

Started Oct 21, 2026, 12:46 PM UTC· resolved Oct 22, 2026, 11:21 AM UTC

  1. investigating Oct 21, 2026, 12:46 PM UTC

    We are aware of the widely reported PHP security vulnerability (CVE-2026-109618 / CVE-2026-109619). Where we are aware of systems that are running potential impacted versions of PHP: - we are applying vendor/WAF rule mitigations for current known exploits - we are restricting IP access where this is not possible to prevent exploit - we have confirmed that web hosting services are receiving protection through our partnership with CloudLinux and the Immunify360 services we run. In some cases, we have also taken the proactive step to temporarily disable web services on systems in line with the current practice by several organisations. This is typically on systems where the current version of PHP is not supported, and is not likely to receive patch updates and will require further action to resolve. Customers hosting virtual infrastructure should urgently consider the advice from the ASD at (https://www.cyber.gov.au/alert/critical-vulnerabilities-in-php, though at the time of release this site was offline). We anticipate most services will be restored early morning Sydney time (it will take some time for the updates to be released, applied and tested, and systems to be cleared).

  2. monitoring Oct 21, 2026, 09:27 PM UTC

    Most systems have been patched overnight and there is minimal impact to services ongoing. We are continuing to identify andnnotify clients running systems we consider may be impacted.

  3. resolved Oct 22, 2026, 11:21 AM UTC

    This incident has been resolved.

Read the full incident report →

Major July 30, 2026 CloudPBX Softphone (Desktop) issues 40m CloudPBX

Started Jul 30, 2026, 01:42 AM UTC· resolved Jul 30, 2026, 02:23 AM UTC

  1. investigating Jul 30, 2026, 01:42 AM UTC

    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.

  2. resolved Jul 30, 2026, 02:23 AM UTC

    Engineers have applied a fix and testing shows fully restored performance on the CloudPBX desktop softphone application.

Read the full incident report →

Minor June 11, 2026 CloudPBX intermittent registration issues 13h 6m CloudPBX

Started Jun 11, 2026, 11:29 PM UTC· resolved Jun 12, 2026, 12:36 PM UTC

  1. monitoring Jun 11, 2026, 11:29 PM UTC

    We have resolved a CloudPBX instability that affected client registration for a small number of requests and some data reporting.

  2. resolved Jun 12, 2026, 12:36 PM UTC

    This incident has been resolved.

  3. postmortem Jun 12, 2026, 12:36 PM UTC

    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.

Read the full incident report →

Major May 12, 2026 Managed VPN currently unavailable 1h 31m Managed VPN

Started May 12, 2026, 12:36 AM UTC· resolved May 12, 2026, 02:07 AM UTC

  1. identified May 12, 2026, 12:36 AM UTC

    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.

  2. resolved May 12, 2026, 02:07 AM UTC

    Ivanti has provided a resolution which has now been applied and tested, resolving this incident. We thank you for your patience.

Read the full incident report →

Minor April 6, 2026 CloudPBX Administration Authenticaiton Issues 9m CloudPBX

Started Apr 06, 2026, 11:23 PM UTC· resolved Apr 06, 2026, 11:32 PM UTC

  1. identified Apr 06, 2026, 11:23 PM UTC

    Our team are working to address an issue impacting authentication to the CloudPBX Administration Interface. Next update in approximately 15 minutes.

  2. resolved Apr 06, 2026, 11:32 PM UTC

    CloudPBX Admin Authentication has been restored.

  3. postmortem Apr 06, 2026, 11:44 PM UTC

    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.

Read the full incident report →

Minor March 20, 2026 CloudPBX Desktop Softphone 13m CloudPBX

Started Mar 20, 2026, 12:23 AM UTC· resolved Mar 20, 2026, 12:37 AM UTC

  1. identified Mar 20, 2026, 12:23 AM UTC

    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.

  2. resolved Mar 20, 2026, 12:37 AM UTC

    Engineers have applied a fix and testing shows fully restored performance on the CloudPBX desktop application.

Read the full incident report →

Major February 8, 2026 CloudPBX service disruption 10m CloudPBX, CloudPBX Mobile

Started Feb 08, 2026, 10:51 PM UTC· resolved Feb 08, 2026, 11:02 PM UTC

  1. investigating Feb 08, 2026, 10:51 PM UTC

    Engineers have identified and are investigating a critical hardware failure within our CloudPBX infrastructure.

  2. resolved Feb 08, 2026, 11:02 PM UTC

    This incident has been resolved.

  3. postmortem Feb 08, 2026, 11:02 PM UTC

    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.

Read the full incident report →

Major February 5, 2026 Web Hosting Services Impacted 42m Web Hosting

Started Feb 05, 2026, 07:15 AM UTC· resolved Feb 05, 2026, 07:57 AM UTC

  1. investigating Feb 05, 2026, 07:15 AM UTC

    We are currently investigating an issue affecting web hosting on some of our platforms.

  2. identified Feb 05, 2026, 07:49 AM UTC

    The issue has been identified and a fix is being implemented.

  3. resolved Feb 05, 2026, 07:57 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice January 27, 2026 CloudPBX - Inbound call failures 6h 13m CloudPBX

Started Jan 27, 2026, 01:29 AM UTC· resolved Jan 27, 2026, 07:42 AM UTC

  1. investigating Jan 27, 2026, 01:29 AM UTC

    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.

  2. resolved Jan 27, 2026, 07:42 AM UTC

    Engineers have resolved the issue. Any further issues should be reported.

Read the full incident report →

Major January 22, 2026 CloudPBX service impacted –

Started Jan 22, 2026, 02:00 PM UTC· resolved Jan 22, 2026, 02:00 PM UTC

  1. resolved Jan 22, 2026, 03:19 PM UTC

    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.

Read the full incident report →

Minor January 15, 2026 CloudPBX calls failing after -30 seconds 1h 9m CloudPBX

Started Jan 15, 2026, 02:27 AM UTC· resolved Jan 15, 2026, 03:37 AM UTC

  1. investigating Jan 15, 2026, 02:27 AM UTC

    We are investigating where some calls are failing after ~30 seconds

  2. identified Jan 15, 2026, 03:13 AM UTC

    We've identified an issue affecting calls with certain versions of the CloudPBX App and are working on a fix.

  3. identified Jan 15, 2026, 03:26 AM UTC

    We are continuing to work on a fix for this issue.

  4. resolved Jan 15, 2026, 03:37 AM UTC

    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.

Read the full incident report →

Minor January 12, 2026 Service interuption - syd02 data centre 2h 56m Virtual Machine Hosting, CloudPBX, Managed Backup (Veeam), CloudPBX Mobile and 2 more

Started Jan 12, 2026, 07:41 AM UTC· resolved Jan 12, 2026, 10:37 AM UTC

  1. investigating Jan 12, 2026, 07:41 AM UTC

    We are currently investigating a service interruption affecting services in our syd02 data hall.

  2. monitoring Jan 12, 2026, 09:18 AM UTC

    A fix has been implemented, and we are monitoring the results. Some services may require a restart to restore connectivity.

  3. resolved Jan 12, 2026, 10:37 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor December 14, 2025 Infrastructure Failure - syd02 data centre 1d Virtual Machine Hosting, Private WAN (MPLS VPN), Managed VPN

Started Dec 14, 2025, 07:19 AM UTC· resolved Dec 15, 2025, 08:03 AM UTC

  1. investigating Dec 14, 2025, 07:19 AM UTC

    We have implemented a rolling restart of the affecting infrastructure and restored connectivity. We are now investigating issues relating to individual services.

  2. identified Dec 14, 2025, 07:21 AM UTC

    We have implemented a rolling restart of the affecting infrastructure and restored connectivity. We are now investigating issues relating to individual services.

  3. resolved Dec 15, 2025, 08:03 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor August 10, 2025 CloudPBX - Database 7h 47m CloudPBX

Started Aug 10, 2025, 12:08 AM UTC· resolved Aug 10, 2025, 07:56 AM UTC

  1. monitoring Aug 10, 2025, 12:08 AM UTC

    Early this morning, our engineers responded to alerts related to a database cluster issue on the CloudPBX platform. This issue impacted service registration across the platform. The cause has been identified and resolved, and services are now gradually re-registering as expected. Our team is actively monitoring progress to ensure full restoration.

  2. resolved Aug 10, 2025, 07:56 AM UTC

    Work to the database cluster has been completed and all CloudPBX services have been fully restored.

Read the full incident report →

Minor March 31, 2025 Telstra Ethernet Access Aggregation Outage 130d 12h Ethernet services

Started Mar 31, 2025, 10:09 PM UTC· resolved Aug 09, 2025, 11:05 AM UTC

  1. identified Mar 31, 2025, 10:09 PM UTC

    We have identified a fault affecting some of our Telstra Ethernet Access Services in NSW that terminate on one of our 100G Transmission ports. This is due to a Telstra equipment/network failure. Engineers are working with Telstra Level 3 Engineers to restore services.

  2. monitoring Apr 06, 2025, 10:52 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Aug 09, 2025, 11:05 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice March 28, 2025 NBN Authentication Failures 134d 7h NBN

Started Mar 28, 2025, 03:56 AM UTC· resolved Aug 09, 2025, 11:05 AM UTC

  1. monitoring Mar 28, 2025, 03:56 AM UTC

    We have resolved an issue affecting NBN authentication of services, and believe services are restored. We are now monitoring recovery.

  2. identified Mar 28, 2025, 04:37 AM UTC

    The previous issue with our authentication system (provided by our billing provider) has resurfaced and engineers are working with them to resolve.

  3. monitoring Mar 31, 2025, 10:07 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Aug 09, 2025, 11:05 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor February 23, 2025 Outage for some Darwin services 2h 46m IP Transit, Ethernet services

Started Feb 23, 2025, 11:51 PM UTC· resolved Feb 24, 2025, 02:38 AM UTC

  1. investigating Feb 23, 2025, 11:51 PM UTC

    We have become aware of an issue affecting some services delivered from our Darwin POP. Engineers are currently assessing the impact and possible cause.

  2. monitoring Feb 24, 2025, 12:12 AM UTC

    Services have been restored. We will continue to monitor for any issues. The root case was a crash and reboot of some hardware. We are working on a replacement schedule for this equipment.

  3. resolved Feb 24, 2025, 02:38 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor December 1, 2024 NBN authentication failures 7h 22m NBN, 3G/4G Data Services

Started Dec 01, 2024, 03:17 AM UTC· resolved Dec 01, 2024, 10:39 AM UTC

  1. identified Dec 01, 2024, 03:17 AM UTC

    We're seeing some NBN authentications fail due to a third-party component: we have escalated this with their technical team.

  2. monitoring Dec 01, 2024, 06:10 AM UTC

    A fix has been implemented. All service should authentication normally. Please reboot your modem if you continue to have issues.

  3. resolved Dec 01, 2024, 10:39 AM UTC

    This incident has been resolved.

Read the full incident report →

Major October 22, 2024 SMILE Service Interruption 3d NBN, Billing Systems

Started Oct 22, 2024, 11:17 PM UTC· resolved Oct 25, 2024, 11:34 PM UTC

  1. identified Oct 22, 2024, 11:17 PM UTC

    Our billing and authentication platform, SMILE, is currently offline. The vendor is currently working to restore services. Customers may experience issues with authenticating NBN services or accessing billing details.

  2. identified Oct 23, 2024, 02:27 AM UTC

    The outage is ongoing. Engineers have been able to put in place some workarounds for some customers, however we are still waiting for our upstream vendor to resolve the issue. The next update from them will be provided shortly after 3pm AEDT. We apologise for the inconvenience.

  3. identified Oct 23, 2024, 03:59 AM UTC

    We are continuing to see issues relating to this. Workarounds are available for individual customers who are impacted on a case by case basis, and can be enabled after contacting our support on 1300 798 718.

  4. identified Oct 23, 2024, 08:39 AM UTC

    Our vendor continues to experience issues restoring services, however we have provided workarounds for most customers. Customers who continue to have issues can contact our team on 1300 798 718 or email [email protected].

  5. monitoring Oct 23, 2024, 09:13 AM UTC

    A fix has been implemented for the remaining authentication processes. Our billing system (and associated API calls including provisioning) remains offline.

  6. resolved Oct 25, 2024, 11:34 PM UTC

    This incident has been resolved.

Read the full incident report →