- Detected by Pingoru
- May 12, 2026, 12:36 AM UTC
- Resolved
- May 12, 2026, 02:07 AM UTC
- Duration
- 1h 31m
Affected: Managed VPN
Timeline · 2 updates
-
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.
-
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 →
- Detected by Pingoru
- Apr 06, 2026, 11:23 PM UTC
- Resolved
- Apr 06, 2026, 11:32 PM UTC
- Duration
- 9m
Affected: CloudPBX
Timeline · 3 updates
-
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.
-
resolved Apr 06, 2026, 11:32 PM UTC
CloudPBX Admin Authentication has been restored.
-
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 →
- Detected by Pingoru
- Mar 20, 2026, 12:23 AM UTC
- Resolved
- Mar 20, 2026, 12:37 AM UTC
- Duration
- 13m
Affected: CloudPBX
Timeline · 2 updates
-
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.
-
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 →
- Detected by Pingoru
- Feb 08, 2026, 10:51 PM UTC
- Resolved
- Feb 08, 2026, 11:02 PM UTC
- Duration
- 10m
Affected: CloudPBXCloudPBX Mobile
Timeline · 3 updates
-
investigating Feb 08, 2026, 10:51 PM UTC
Engineers have identified and are investigating a critical hardware failure within our CloudPBX infrastructure.
-
resolved Feb 08, 2026, 11:02 PM UTC
This incident has been resolved.
-
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 →
- Detected by Pingoru
- Feb 05, 2026, 07:15 AM UTC
- Resolved
- Feb 05, 2026, 07:57 AM UTC
- Duration
- 42m
Affected: Web Hosting
Timeline · 3 updates
-
investigating Feb 05, 2026, 07:15 AM UTC
We are currently investigating an issue affecting web hosting on some of our platforms.
-
identified Feb 05, 2026, 07:49 AM UTC
The issue has been identified and a fix is being implemented.
-
resolved Feb 05, 2026, 07:57 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jan 27, 2026, 01:29 AM UTC
- Resolved
- Jan 27, 2026, 07:42 AM UTC
- Duration
- 6h 13m
Affected: CloudPBX
Timeline · 2 updates
-
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.
-
resolved Jan 27, 2026, 07:42 AM UTC
Engineers have resolved the issue. Any further issues should be reported.
Read the full incident report →
- Detected by Pingoru
- Jan 22, 2026, 02:00 PM UTC
- Resolved
- Jan 22, 2026, 02:00 PM UTC
- Duration
- —
Timeline · 1 update
-
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 →
- Detected by Pingoru
- Jan 15, 2026, 02:27 AM UTC
- Resolved
- Jan 15, 2026, 03:37 AM UTC
- Duration
- 1h 9m
Affected: CloudPBX
Timeline · 4 updates
-
investigating Jan 15, 2026, 02:27 AM UTC
We are investigating where some calls are failing after ~30 seconds
-
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.
-
identified Jan 15, 2026, 03:26 AM UTC
We are continuing to work on a fix for this issue.
-
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 →
- Detected by Pingoru
- Jan 12, 2026, 07:41 AM UTC
- Resolved
- Jan 12, 2026, 10:37 AM UTC
- Duration
- 2h 56m
Affected: Virtual Machine HostingCloudPBXManaged Backup (Veeam)CloudPBX MobilePrivate WAN (MPLS VPN)Managed VPN
Timeline · 3 updates
-
investigating Jan 12, 2026, 07:41 AM UTC
We are currently investigating a service interruption affecting services in our syd02 data hall.
-
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.
-
resolved Jan 12, 2026, 10:37 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Dec 14, 2025, 07:19 AM UTC
- Resolved
- Dec 15, 2025, 08:03 AM UTC
- Duration
- 1d
Affected: Virtual Machine HostingPrivate WAN (MPLS VPN)Managed VPN
Timeline · 3 updates
-
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.
-
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.
-
resolved Dec 15, 2025, 08:03 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Aug 10, 2025, 12:08 AM UTC
- Resolved
- Aug 10, 2025, 07:56 AM UTC
- Duration
- 7h 47m
Affected: CloudPBX
Timeline · 2 updates
-
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.
-
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 →
- Detected by Pingoru
- Mar 31, 2025, 10:09 PM UTC
- Resolved
- Aug 09, 2025, 11:05 AM UTC
- Duration
- 130d 12h
Affected: Ethernet services
Timeline · 3 updates
-
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.
-
monitoring Apr 06, 2025, 10:52 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Aug 09, 2025, 11:05 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 28, 2025, 03:56 AM UTC
- Resolved
- Aug 09, 2025, 11:05 AM UTC
- Duration
- 134d 7h
Affected: NBN
Timeline · 4 updates
-
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.
-
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.
-
monitoring Mar 31, 2025, 10:07 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Aug 09, 2025, 11:05 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Feb 23, 2025, 11:51 PM UTC
- Resolved
- Feb 24, 2025, 02:38 AM UTC
- Duration
- 2h 46m
Affected: IP TransitEthernet services
Timeline · 3 updates
-
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.
-
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.
-
resolved Feb 24, 2025, 02:38 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Dec 01, 2024, 03:17 AM UTC
- Resolved
- Dec 01, 2024, 10:39 AM UTC
- Duration
- 7h 22m
Affected: NBN3G/4G Data Services
Timeline · 3 updates
-
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.
-
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.
-
resolved Dec 01, 2024, 10:39 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Oct 22, 2024, 11:17 PM UTC
- Resolved
- Oct 25, 2024, 11:34 PM UTC
- Duration
- 3d
Affected: NBNBilling Systems
Timeline · 6 updates
-
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.
-
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.
-
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.
-
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].
-
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.
-
resolved Oct 25, 2024, 11:34 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Oct 21, 2024, 07:21 AM UTC
- Resolved
- Oct 21, 2024, 08:29 AM UTC
- Duration
- 1h 7m
Affected: CloudPBX
Timeline · 3 updates
-
identified Oct 21, 2024, 07:21 AM UTC
We are currently investigating an outage affecting registration across our CloudPBX platform.
-
monitoring Oct 21, 2024, 08:04 AM UTC
We have restored services following a database cluster stall, and are continuing to monitor systems to ensure that all services are restored.
-
resolved Oct 21, 2024, 08:29 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Oct 08, 2024, 01:31 AM UTC
- Resolved
- Oct 08, 2024, 04:26 AM UTC
- Duration
- 2h 54m
Affected: NBN
Timeline · 4 updates
-
investigating Oct 08, 2024, 01:31 AM UTC
We have received some reports of authentication Failures affecting some NBN services. We are currently investigating the issue and will rectify as soon as possible.
-
investigating Oct 08, 2024, 01:32 AM UTC
We are continuing to investigate this issue.
-
investigating Oct 08, 2024, 04:25 AM UTC
We are continuing to investigate this issue.
-
resolved Oct 08, 2024, 04:26 AM UTC
NBN services should now be restored. We apogise for this inconvenience.
Read the full incident report →
- Detected by Pingoru
- Aug 27, 2024, 02:21 PM UTC
- Resolved
- Aug 27, 2024, 02:47 PM UTC
- Duration
- 25m
Timeline · 3 updates
-
identified Aug 27, 2024, 02:21 PM UTC
We are seeing an un-planned outage impacting Telstra EA service in QLD. Testing indicates an issue in Brisbane on the upstream carrier side effecting an EA headend port. We have lodged a fault with them to assist in investigating.
-
monitoring Aug 27, 2024, 02:37 PM UTC
We are seeing service restored and upstream diagnostics are passing now.
-
resolved Aug 27, 2024, 02:47 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Aug 20, 2024, 03:27 AM UTC
- Resolved
- Aug 31, 2024, 02:57 AM UTC
- Duration
- 10d 23h
Affected: Helpdesk Services
Timeline · 4 updates
-
identified Aug 20, 2024, 03:27 AM UTC
Our help desk provider, Zendesk, is currently experiencing delays with processing inbound emails which is delaying ticket creation and ticket updates. Customers are encouraged to update their tickets from the Web Portal (https://helpdesk.realworld.net.au/). Tickets can also be created from here.
-
identified Aug 20, 2024, 04:14 AM UTC
Zendesk have indicated that they are currently testing a fix for this and expect another update within the next 2 hours.
-
monitoring Aug 20, 2024, 09:47 AM UTC
Zendesk have applied a fix to the inbound mail queue and we have seen a steady improvement of ticket creation over the last two hours.
-
resolved Aug 31, 2024, 02:57 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Aug 12, 2024, 01:08 AM UTC
- Resolved
- Aug 13, 2024, 01:34 AM UTC
- Duration
- 1d
Affected: Helpdesk Services
Timeline · 3 updates
-
identified Aug 12, 2024, 01:08 AM UTC
We've identified an issue causing intermittent ticket submission failures when submitting tickets to us via email. Our engineers are working on resolving this issue as quickly as possible. In the meantime, we ask that if you do not receive an automated reply from our systems after sending us an email, please submit your tickets via the helpdesk at https://helpdesk.realworld.net.au or if the issue is urgent, call us on 1300 798 718
-
monitoring Aug 12, 2024, 02:12 AM UTC
We have implemented a workaround within our email system that has resolved ticket submission via email. Any existing messages may be held by our email delivery partner (Google) for up to 24 hours before being received by our system.
-
resolved Aug 13, 2024, 01:34 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jun 11, 2024, 12:52 AM UTC
- Resolved
- Jun 11, 2024, 02:05 AM UTC
- Duration
- 1h 12m
Affected: NBN3G/4G Data ServicesManaged VPN
Timeline · 2 updates
-
identified Jun 11, 2024, 12:52 AM UTC
NBN and other Data services which need re-authentication will currently be unable to connect due to an outage within an upstream dependent system. Engineers are working with the upstream provider to resolve.
-
resolved Jun 11, 2024, 02:05 AM UTC
Our billing vendor has restored services following a major outage and all systems are now functioning correctly.
Read the full incident report →
- Detected by Pingoru
- Jun 11, 2024, 12:50 AM UTC
- Resolved
- Jun 11, 2024, 02:05 AM UTC
- Duration
- 1h 14m
Affected: Billing Systems
Timeline · 2 updates
-
identified Jun 11, 2024, 12:50 AM UTC
We are aware of an outage affecting our billing system (SMILE) which is impacting a number of services. This includes provisioning requests, number porting requests and other services which depend on this service. Our vendor is aware of the outage and is working on a resolution.
-
resolved Jun 11, 2024, 02:05 AM UTC
Our billing vendor has restored services following a major outage and all systems are now functioning correctly.
Read the full incident report →
- Detected by Pingoru
- May 23, 2024, 05:25 AM UTC
- Resolved
- May 23, 2024, 05:51 AM UTC
- Duration
- 26m
Affected: Ethernet services
Timeline · 2 updates
-
identified May 23, 2024, 05:25 AM UTC
Please be advised we are experiencing an issue with an NBN interconnect in Brisbane that is causing an outage for some services. Staff are currently investigating.
-
resolved May 23, 2024, 05:51 AM UTC
Please be advised this issue is resolved and we do not expect any further impact to service.
Read the full incident report →