<?xml version="1.0" encoding="UTF-8"?>
<feed xml:lang="en-US" xmlns="http://www.w3.org/2005/Atom">
  <id>tag:aatroxcommunications.instatus.com,2005:/history</id>
  <link rel="alternate" type="text/html" href="https://aatroxcommunications.instatus.com"/>
  <link rel="self" type="application/atom+xml" href="https://aatroxcommunications.instatus.com/history.atom"/>
  <title>Aatrox Communications Status - Incident history</title>
  <updated>2026-10-08T20:50:42.425+00:00</updated>
  <author>
    <name>Aatrox Communications</name>
  </author>
  
<entry>
  <id>tag:aatroxcommunications.instatus.com,2005:Incident/cmv00gr6b00cw1bpc5lrsl0l1</id>
  <published>2026-10-08T20:50:42.425+00:00</published>
  <updated>2026-10-09T08:40:33.663+00:00</updated>
  <link rel="alternate" type="text/html" href="https://aatroxcommunications.instatus.com/incident/cmv00gr6b00cw1bpc5lrsl0l1"/>
  <title>NBN POI Incident in NSW, QLD</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> NBN Broadband</p>
    <p><small>Oct <var data-var='date'> 9</var>, <var data-var='time'>08:40:33</var> GMT+0</small><br /><strong>Identified</strong> -
  9 Oct 2026, 19:30 AEDT - Fibre technicians are continuing restoration activities in challenging working conditions. Preparation of one cable is complete, and we are preparing the second cable while daylight remains. Once preparation activities are complete, fibre splicing will commence on both cables, with affected services expected to progressively restore as splicing progresses.  .</p>
<p><small>Oct <var data-var='date'> 9</var>, <var data-var='time'>07:00:56</var> GMT+0</small><br /><strong>Identified</strong> -
  1. 9 Oct 2026, 01:42 pm AEDT  
    
Restoration activities continue to progress slowly, with the repair methodology further revised to require manual excavation to expose the existing cable and obtain additional slack for restoration. Due to the complexity of the work and the revised restoration approach, service restoration is expected to take longer than originally anticipated.
2. 9 Oct 2026, 04:02 pm AEDT  
    
Fibre technicians have successfully hauled the cable and commenced fibre splicing and temporary pit installation activities.
3. 9 Oct 2026, 05:36 pm AEDT  
    
Fibre technicians are continuing to progress restoration activities. Temporary pit installation has been completed, and fibre preparation works are underway, with splicing at the second end of one of the two affected cables scheduled to commence at 18:00 AEDT. Affected services are expected to progressively restore as fibre splicing progresses..</p>
<p><small>Oct <var data-var='date'> 9</var>, <var data-var='time'>03:13:53</var> GMT+0</small><br /><strong>Identified</strong> -
  9 Oct 2026, 01:42 pm AEDT - Restoration activities continue to progress slowly, with the repair methodology further revised to require manual excavation to expose the existing cable and obtain additional slack for restoration. Due to the complexity of the work and the revised restoration approach, service restoration is expected to take longer than originally anticipated..</p>
<p><small>Oct <var data-var='date'> 9</var>, <var data-var='time'>01:18:48</var> GMT+0</small><br /><strong>Identified</strong> -
  9 Oct 2026, 12:11 pm AEDT - Progress continues on the restoration activities; Additional challenges were encountered during the cable remediation activities. To facilitate the restoration of services, an additional temporary joint will now be installed at an additional pit location. Due to the complexity of these works and the revised restoration method, service restoration is expected to take longer than originally anticipated..</p>
<p><small>Oct <var data-var='date'> 9</var>, <var data-var='time'>00:53:40</var> GMT+0</small><br /><strong>Identified</strong> -
    
9 Oct 2026, 11:11 am AEDT - Cable hauling through the pits is progressing; challenges have been encountered, which may delay fibre splicing activities and restoration..</p>
<p><small>Oct <var data-var='date'> 8</var>, <var data-var='time'>22:19:55</var> GMT+0</small><br /><strong>Identified</strong> -
  9 Oct 2026, 09:03 AEDT - Fibre contractors arrived on site and are currently setting up hauling activities to pull the replacement cable in preparation for restoration, after which fibre splicing will commence..</p>
<p><small>Oct <var data-var='date'> 8</var>, <var data-var='time'>20:50:42</var> GMT+0</small><br /><strong>Identified</strong> -
  Our upstream carrier vocus has identified a service disruption affecting Vocus Transmission services located between Sydney, NSW and Brisbane, Queensland on SB1 route due to a potential fibre issue. 

Their engineering teams are actively investigating the issue and working to restore affected services as quickly as possible. Further updates will be provided as they become available.

**1) 9 Oct 2026, 01:02 am**   
Vocus T3 transmission team have confirmed a fibre break between the Somersby (SOMR) and Northville (NORV) CEVs. Our field technician has attended the fault location and successfully identified the exact point of failure. Initial investigations indicate the cable damage is likely the result of vandalism. Fibre contractors and civil crews have been engaged.

**2) 9 Oct 2026, 01:32 am**   
Fibre contractors have been engaged and are expected to arrive on site at approximately 02:00 AEST on 09/10/2026\. Upon arrival, they will commence restoration activities to facilitate service restoration.

**3) 9 Oct 2026, 02:55 am**   
Restoration works have been suspended overnight due to site access and safety constraints and will recommence at first daylight.

**4) 9 Oct 2026, 07:23 am**   
Fibre technicians have arrived at the fault location and commenced fibre preparation works. To work on a fix for this incident..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:aatroxcommunications.instatus.com,2005:Incident/cmths8c9r0cpl1ms25zkjc1dc</id>
  <published>2026-08-31T22:00:41.687+00:00</published>
  <updated>2026-09-01T21:24:26.424+00:00</updated>
  <link rel="alternate" type="text/html" href="https://aatroxcommunications.instatus.com/incident/cmths8c9r0cpl1ms25zkjc1dc"/>
  <title>NBN Outage</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 23 hours and 24 minutes</p>
    <p><strong>Affected Components:</strong> NBN Broadband</p>
    <p><small>Sep <var data-var='date'> 1</var>, <var data-var='time'>21:24:26</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Sep <var data-var='date'> 1</var>, <var data-var='time'>05:37:38</var> GMT+0</small><br /><strong>Monitoring</strong> -
  We implemented a fix and are currently monitoring the result..</p>
<p><small>Sep <var data-var='date'> 1</var>, <var data-var='time'>03:23:15</var> GMT+0</small><br /><strong>Identified</strong> -
  We are continuing to work on a fix for this incident..</p>
<p><small>Aug <var data-var='date'> 31</var>, <var data-var='time'>22:00:41</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are currently investigating this incident..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:aatroxcommunications.instatus.com,2005:Incident/cmtapblyw0c750klgzx8cf88j</id>
  <published>2026-08-26T23:04:51.663+00:00</published>
  <updated>2026-08-26T23:38:32.167+00:00</updated>
  <link rel="alternate" type="text/html" href="https://aatroxcommunications.instatus.com/incident/cmtapblyw0c750klgzx8cf88j"/>
  <title>CloudUC Outage</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 34 minutes</p>
    <p><strong>Affected Components:</strong> Cloud PBX Hosting</p>
    <p><small>Aug <var data-var='date'> 26</var>, <var data-var='time'>23:38:32</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Aug <var data-var='date'> 26</var>, <var data-var='time'>23:04:51</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are currently investigating this incident..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:aatroxcommunications.instatus.com,2005:Incident/cmrmpgjqr04ea1bp0vxf4a07n</id>
  <published>2026-07-15T23:22:31.035+00:00</published>
  <updated>2026-07-16T01:40:12.825+00:00</updated>
  <link rel="alternate" type="text/html" href="https://aatroxcommunications.instatus.com/incident/cmrmpgjqr04ea1bp0vxf4a07n"/>
  <title>CloudUC Outage</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 2 hours and 18 minutes</p>
    <p><strong>Affected Components:</strong> Cloud PBX Hosting</p>
    <p><small>Jul <var data-var='date'> 16</var>, <var data-var='time'>01:40:12</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Jul <var data-var='date'> 16</var>, <var data-var='time'>00:31:53</var> GMT+0</small><br /><strong>Monitoring</strong> -
  We implemented a fix and are currently monitoring the result..</p>
<p><small>Jul <var data-var='date'> 15</var>, <var data-var='time'>23:54:09</var> GMT+0</small><br /><strong>Identified</strong> -
  We have identified the issues and we are continuing to work on a fix for this incident..</p>
<p><small>Jul <var data-var='date'> 15</var>, <var data-var='time'>23:22:31</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are currently investigating this incident and will update this incident as we find out more information..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:aatroxcommunications.instatus.com,2005:Incident/cmrb6ksvd00k50kldwxnh8p6j</id>
  <published>2026-07-07T21:48:28.593+00:00</published>
  <updated>2026-07-09T04:12:35.212+00:00</updated>
  <link rel="alternate" type="text/html" href="https://aatroxcommunications.instatus.com/incident/cmrb6ksvd00k50kldwxnh8p6j"/>
  <title>Telstra Nationwide Mobile Network Outage</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 day, 6 hours and 24 minutes</p>
    <p><strong>Affected Components:</strong> SMS &amp; Mobile</p>
    <p><small>Jul <var data-var='date'> 9</var>, <var data-var='time'>04:12:35</var> GMT+0</small><br /><strong>Resolved</strong> -
  This will be the final update on this outage

Mobile provisioning and APIs remain available and are operating as expected.

As we shared earlier, Telstra identified a subsequent issue affecting some calls, including to Triple Zero. The nature of this issue only became apparent as they resolved the original outage.

In these cases, some people calling Triple Zero received an error message, and their phone would then try to connect to an alternative mobile network.

This was a consequence of the same software defect behind yesterday’s outage. While the original issue was addressed, this one remained ongoing and needed to be fixed in a different way.

Overnight, Telstra made good progress, significantly reducing failed calls to Triple Zero. They have now implemented a fix that has addressed the impact of this issue. 

If you are still experiencing issues, please reach out to our team.</p>
<p><small>Jul <var data-var='date'> 8</var>, <var data-var='time'>20:52:06</var> GMT+0</small><br /><strong>Monitoring</strong> -
  Telstra has largely resolved this issue. Provisioning impacts have been restored, and APIs are now available.

Otherwise, the issue in our network has now mostly been resolved. In our last update, just under 90% of calls and data services were back up and running - since then, we&#039;ve restored more remaining services.

Telstra has also advised of a secondary issue affecting some calls, including Triple Zero. 

You may receive an error message while your phone tries to connect to an alternative network. If affected, wait up to 90 seconds for reconnection, or use a different phone to call. Telstra are working urgently with to resolve this, and they&#039;ll be performing welfare checks where failed 000 calls are detected..</p>
<p><small>Jul <var data-var='date'> 7</var>, <var data-var='time'>23:02:32</var> GMT+0</small><br /><strong>Investigating</strong> -
  We have had reports of devices coming back online; however, this issue is still ongoing.

We will update the outage when we have further updates.</p>
<p><small>Jul <var data-var='date'> 7</var>, <var data-var='time'>21:57:07</var> GMT+0</small><br /><strong>Investigating</strong> -
  Please note, this issue affects the entire Telstra Mobile network .</p>
<p><small>Jul <var data-var='date'> 7</var>, <var data-var='time'>21:48:28</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are aware of a nationwide outage currently affecting the Telstra mobile network.

Customers using Telstra Mobile services, or services delivered via the Telstra Mobile network, may experience issues including:

* Inability to make or receive calls
* Mobile data connectivity issues
* Devices displaying &quot;SOS&quot; or &quot;Emergency Calls Only&quot;

Our team is actively monitoring the situation. At this stage, the issue has been identified as a network-wide fault within the Telstra mobile network and is outside of Aatrox Communications&#039; control.

Telstra is currently investigating and working to restore services as quickly as possible.

We will provide further updates as more information becomes available..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:aatroxcommunications.instatus.com,2005:Incident/cmoqeznpq01bgle3ha552bkjg</id>
  <published>2026-05-03T23:41:25.401+00:00</published>
  <updated>2026-05-04T19:54:50.176+00:00</updated>
  <link rel="alternate" type="text/html" href="https://aatroxcommunications.instatus.com/incident/cmoqeznpq01bgle3ha552bkjg"/>
  <title>NBN Network Outage Fairfield, VIC and Surrounding Areas</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 20 hours and 13 minutes</p>
    <p><strong>Affected Components:</strong> NBN Broadband</p>
    <p><small>May <var data-var='date'> 4</var>, <var data-var='time'>19:54:50</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>May <var data-var='date'> 4</var>, <var data-var='time'>03:54:50</var> GMT+0</small><br /><strong>Monitoring</strong> -
  NBN Co. techncian is at the affect exchange and is currently working to resolve the issue..</p>
<p><small>May <var data-var='date'> 3</var>, <var data-var='time'>23:42:26</var> GMT+0</small><br /><strong>Identified</strong> -
  NBN Co. have identfied the issue and are working to resolve the outage, at this stage there is no ETR..</p>
<p><small>May <var data-var='date'> 3</var>, <var data-var='time'>23:41:25</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are currently investigating this incident..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:aatroxcommunications.instatus.com,2005:Incident/cmoqduxmx0116le3hu1be7usd</id>
  <published>2026-05-03T23:09:44.086+00:00</published>
  <updated>2026-05-04T02:50:08.464+00:00</updated>
  <link rel="alternate" type="text/html" href="https://aatroxcommunications.instatus.com/incident/cmoqduxmx0116le3hu1be7usd"/>
  <title>NBN Network Fault for Glebe, NSW and Surrounding Areas</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 3 hours and 40 minutes</p>
    <p><strong>Affected Components:</strong> NBN Broadband</p>
    <p><small>May <var data-var='date'> 4</var>, <var data-var='time'>02:50:08</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>May <var data-var='date'> 4</var>, <var data-var='time'>00:09:51</var> GMT+0</small><br /><strong>Monitoring</strong> -
  NBN Co. have confirmed that replacement hardware is on the way. At this stage we are still waiting on an ETR from NBN Co..</p>
<p><small>May <var data-var='date'> 3</var>, <var data-var='time'>23:17:30</var> GMT+0</small><br /><strong>Identified</strong> -
  NBN Co. have identified the issue continue to work towards a solution. At this time, there is no ETR. Please continue monitor the status of this outage. .</p>
<p><small>May <var data-var='date'> 3</var>, <var data-var='time'>23:09:44</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are currently investigating this incident..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:aatroxcommunications.instatus.com,2005:Incident/cmmy48df2046za9h4oh7tz827</id>
  <published>2026-03-19T22:30:03.146+00:00</published>
  <updated>2026-03-21T00:50:21.227+00:00</updated>
  <link rel="alternate" type="text/html" href="https://aatroxcommunications.instatus.com/incident/cmmy48df2046za9h4oh7tz827"/>
  <title>Voice - Service Degradation - Investigating</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 day, 2 hours and 20 minutes</p>
    <p><strong>Affected Components:</strong> Cloud PBX Hosting, SIP Trunking (Australia)</p>
    <p><small>Mar <var data-var='date'> 21</var>, <var data-var='time'>00:50:21</var> GMT+0</small><br /><strong>Resolved</strong> -
  Our testing is showing traffic from AAPT/Vocus networks performing as we expect. 

We will continue to monitor traffc coming from their network over the next few days..</p>
<p><small>Mar <var data-var='date'> 20</var>, <var data-var='time'>07:08:06</var> GMT+0</small><br /><strong>Monitoring</strong> -
  Vocus/TPG have identified an issue between their network and several cloud providers, including Amazon Web Services, and this is creating packet loss, causing poor audio quality. Vocus/TPG are aware of the situation since early this morning and have actively been trying to resolve the issue since.

We will update you once resolved..</p>
<p><small>Mar <var data-var='date'> 20</var>, <var data-var='time'>01:25:45</var> GMT+0</small><br /><strong>Identified</strong> -
  We have been in touch with the AWS technical team, and they are looking into this as a priority.

From our monitoring, we are seeing a fair bit of packet loss coming from their network..</p>
<p><small>Mar <var data-var='date'> 19</var>, <var data-var='time'>23:12:03</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Mar <var data-var='date'> 19</var>, <var data-var='time'>22:30:03</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are investigating reports of intermittent call quality issues for inbound/outbound calls.

Initial investigations are pointing towards services hosted with AWS.

The next update will be posted in 30 minutes..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:aatroxcommunications.instatus.com,2005:Incident/cmmnzlrpp014011pq6fen2yif</id>
  <published>2026-03-12T21:35:46.734+00:00</published>
  <updated>2026-03-12T23:31:25.875+00:00</updated>
  <link rel="alternate" type="text/html" href="https://aatroxcommunications.instatus.com/incident/cmmnzlrpp014011pq6fen2yif"/>
  <title>OZICT - CloudPBX Outage</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 56 minutes</p>
    <p><strong>Affected Components:</strong> Cloud PBX Hosting</p>
    <p><small>Mar <var data-var='date'> 12</var>, <var data-var='time'>23:31:25</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Mar <var data-var='date'> 12</var>, <var data-var='time'>22:11:59</var> GMT+0</small><br /><strong>Identified</strong> -
  From our Upstream Provider - At this stage, the issue appears to be with the FortiGate Firewalls cluster (2) that sits in front of the Cloud PBX instances and not the underlying hardware running the Cloud PBX instances, which are still running.  
  
Our Firewall vendor is working on this as a P1, and Fortinet are involved.  
  
Impacts:  
\* Unable to access the Management GUI interfaces  
\* Calls in and out of the system will fail  
\* Handsets will not register.  
\* Softphones will not register.  
  
As calls are not getting through the firewall to the CloudPBX instances, unfortunately, we are also unable to divert calls.  
  
We sincerly apologise for the inconvenience and will continue to provide updates as they become available..</p>
<p><small>Mar <var data-var='date'> 12</var>, <var data-var='time'>21:35:46</var> GMT+0</small><br /><strong>Investigating</strong> -
  Please be advised that our vendor, which hosts the CloudPBX product, is currently experiencing an outage affecting their network.

This has been logged with our vendor and is being investigated as a priority..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:aatroxcommunications.instatus.com,2005:Incident/cmmmo1xwb007voys0etoxrmo1</id>
  <published>2026-03-11T23:24:38.732+00:00</published>
  <updated>2026-03-12T05:18:10.192+00:00</updated>
  <link rel="alternate" type="text/html" href="https://aatroxcommunications.instatus.com/incident/cmmmo1xwb007voys0etoxrmo1"/>
  <title>SMS Messages failing to be sent/received from virtual mobile numbers</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 5 hours and 54 minutes</p>
    <p><strong>Affected Components:</strong> SMS &amp; Mobile</p>
    <p><small>Mar <var data-var='date'> 12</var>, <var data-var='time'>05:18:10</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Mar <var data-var='date'> 12</var>, <var data-var='time'>04:08:06</var> GMT+0</small><br /><strong>Monitoring</strong> -
  We are starting to see SMS messages being delivered to devices via our upstream network provider.

We will monitor this and mark it as resolved once confirmed everything is back to normal..</p>
<p><small>Mar <var data-var='date'> 12</var>, <var data-var='time'>02:19:37</var> GMT+0</small><br /><strong>Monitoring</strong> -
  Our upstream provider is still working on deploying a network fix for outbound SMS.

We will provide another update once the fix has been deployed..</p>
<p><small>Mar <var data-var='date'> 12</var>, <var data-var='time'>00:46:25</var> GMT+0</small><br /><strong>Identified</strong> -
  Our upstream provider is still working on deploying a network fix for outbound SMS. 

We will provide another update once the fix has been deployed..</p>
<p><small>Mar <var data-var='date'> 12</var>, <var data-var='time'>00:01:51</var> GMT+0</small><br /><strong>Identified</strong> -
  Our upstream provider is working on deploying a network fix for outbound sms. Inbound sms are now hitting our network.

We will provide another update once the fix has been deployed..</p>
<p><small>Mar <var data-var='date'> 11</var>, <var data-var='time'>23:24:38</var> GMT+0</small><br /><strong>Investigating</strong> -
  Our monitoring has detected an outage affecting our upstream Tier 1 SMS gateway.

This issue is with our upstream Tier 1 carrier and is impacting both inbound and outbound SMS services.

Our upstream carrier is currently investigating the problem.

The next update will be provided in 30 minutes..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:aatroxcommunications.instatus.com,2005:Incident/cmmchtv3l0086x75glw0u44qj</id>
  <published>2026-03-04T20:32:41.791+00:00</published>
  <updated>2026-03-04T21:21:07.885+00:00</updated>
  <link rel="alternate" type="text/html" href="https://aatroxcommunications.instatus.com/incident/cmmchtv3l0086x75glw0u44qj"/>
  <title>NZ - Broadband speed issues</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 48 minutes</p>
    <p><strong>Affected Components:</strong> New Zealand Ultra-Fast Broadband</p>
    <p><small>Mar <var data-var='date'> 4</var>, <var data-var='time'>21:21:07</var> GMT+0</small><br /><strong>Resolved</strong> -
  An emergency change has been implemented which has resolved the speed issues (download and upload speeds were affected).

Engineers will continue to monitor, however, reports indicate all connections should be operating as expected. Please reach out if there are still issues affecting your connection..</p>
<p><small>Mar <var data-var='date'> 4</var>, <var data-var='time'>20:32:41</var> GMT+0</small><br /><strong>Investigating</strong> -
  We have received reports of broadband connection speed issues across a number of connections.

Engineers are currently investigating, and we will provide updates as more information comes to hand..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:aatroxcommunications.instatus.com,2005:Incident/cmkdlfltg03wbjgz8z3ozmt82</id>
  <published>2026-01-14T05:41:55.629+00:00</published>
  <updated>2026-01-14T07:05:36.099+00:00</updated>
  <link rel="alternate" type="text/html" href="https://aatroxcommunications.instatus.com/incident/cmkdlfltg03wbjgz8z3ozmt82"/>
  <title>Outbound SMS messages failing</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 24 minutes</p>
    <p><strong>Affected Components:</strong> SMS &amp; Mobile</p>
    <p><small>Jan <var data-var='date'> 14</var>, <var data-var='time'>07:05:36</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Jan <var data-var='date'> 14</var>, <var data-var='time'>05:41:55</var> GMT+0</small><br /><strong>Identified</strong> -
  Our monitoring has alerted us to an outage with our Tier1&#039;s SMS gateway.

The outage lies with our upstream Tier 1 carrier. The outage is only affecting inbound and outbound SMS. 

Our upstream carrier is currently investigating the issue.

The next update will be provided in 30 minutes..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:aatroxcommunications.instatus.com,2005:Maintenance/cmj1tas9800aifztcf69iy9a6</id>
  <published>2025-12-17T10:00:00.000+00:00</published>
  <updated>2025-12-17T15:00:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://aatroxcommunications.instatus.com/maintenance/cmj1tas9800aifztcf69iy9a6"/>
  <title>Scheduled Network Outage 2025-12-17 23:00</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 5 hours</p>
    <p><strong>Affected Components:</strong> SMS &amp; Mobile, Microsoft Teams Direct Routing, SIP Trunking (Australia)</p>
    <p><small>Dec <var data-var='date'> 17</var>, <var data-var='time'>15:00:00</var> GMT+0</small><br /><strong>Completed</strong> -
  Maintenance has completed successfully.</p>
<p><small>Dec <var data-var='date'> 17</var>, <var data-var='time'>10:00:01</var> GMT+0</small><br /><strong>Identified</strong> -
  Maintenance is now in progress.</p>
<p><small>Dec <var data-var='date'> 17</var>, <var data-var='time'>10:00:00</var> GMT+0</small><br /><strong>Identified</strong> -
  We are writing to inform you of a scheduled network event. 

As a result, services may experience a disruption of up to 1 Hour for IPv6 Routing within the window advised, due to third-party equipment maintenance.  
  
We apologise for any inconvenience this may cause.  
  
Please note that all times are provided in 24-hour format.

Work Start: 2025-12-17 23:00  
Work End: 2025-12-18 05:00  
Time Zone: Australian Eastern Standard Time (AEST - Australia/Brisbane)  
Outage Duration: 1 Hour for IPv6 Routing  
  
If you have any queries, please reach out to our support team.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:aatroxcommunications.instatus.com,2005:Incident/cmj94pxuu0049z1yletfmrs7j</id>
  <published>2025-12-16T22:03:17.488+00:00</published>
  <updated>2025-12-16T22:53:06.258+00:00</updated>
  <link rel="alternate" type="text/html" href="https://aatroxcommunications.instatus.com/incident/cmj94pxuu0049z1yletfmrs7j"/>
  <title>Unable to connect to the Aatrox SMS API</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 50 minutes</p>
    <p><strong>Affected Components:</strong> SMS &amp; Mobile</p>
    <p><small>Dec <var data-var='date'> 16</var>, <var data-var='time'>22:53:06</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved, and outbound SMS are working correctly now..</p>
<p><small>Dec <var data-var='date'> 16</var>, <var data-var='time'>22:20:58</var> GMT+0</small><br /><strong>Identified</strong> -
  The outage lies between our SMS Gateway and the upstream Tier 1 carrier. The outage is only affecting outbound SMS. Inbound SMS are unaffected.

Our upstream carrier is currently investigating the issue.

The next update will be provided in 30 minutes..</p>
<p><small>Dec <var data-var='date'> 16</var>, <var data-var='time'>22:03:17</var> GMT+0</small><br /><strong>Investigating</strong> -
  We have been made aware that SMS API requests are failing. We are currently investigating this .</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:aatroxcommunications.instatus.com,2005:Incident/cmh12xfja01g3b47cexaqyy1m</id>
  <published>2025-10-21T21:31:33.560+00:00</published>
  <updated>2025-10-22T01:11:56.454+00:00</updated>
  <link rel="alternate" type="text/html" href="https://aatroxcommunications.instatus.com/incident/cmh12xfja01g3b47cexaqyy1m"/>
  <title>UFB - Northpower Whangārei</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 3 hours and 40 minutes</p>
    <p><strong>Affected Components:</strong> New Zealand Ultra-Fast Broadband</p>
    <p><small>Oct <var data-var='date'> 22</var>, <var data-var='time'>01:11:56</var> GMT+0</small><br /><strong>Resolved</strong> -
  The Northpower handover has been stable since the fix was implemented, resolving incident now..</p>
<p><small>Oct <var data-var='date'> 21</var>, <var data-var='time'>23:41:20</var> GMT+0</small><br /><strong>Monitoring</strong> -
  The physical issue appears to be resolved, and traffic on the handover link is now looking healthy. 

We’ll continue to closely monitor the situation until we receive full confirmation from our upstream providers.

If you’re still experiencing any issues, please check your equipment and contact our support team as usual so we can assist further..</p>
<p><small>Oct <var data-var='date'> 21</var>, <var data-var='time'>22:06:22</var> GMT+0</small><br /><strong>Identified</strong> -
  Field techs have been dispatched to troubleshoot the physicals further we should have another update in 15-20 minutes..</p>
<p><small>Oct <var data-var='date'> 21</var>, <var data-var='time'>21:52:47</var> GMT+0</small><br /><strong>Identified</strong> -
  Upstream has identified a problem, and engineers are working on a fix. No ETR just yet, we will update as more details come from upstream..</p>
<p><small>Oct <var data-var='date'> 21</var>, <var data-var='time'>21:31:33</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are seeing problems on our Norhtpower UFB handover (Whangārei) This will be impacting UFB services that use Northpower connections. Engineers are currently investigating the root cause and we will update as we have more information..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:aatroxcommunications.instatus.com,2005:Maintenance/cmfegxapj004m9iuvb64t2det</id>
  <published>2025-09-16T13:00:00.000+00:00</published>
  <updated>2025-09-16T13:30:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://aatroxcommunications.instatus.com/maintenance/cmfegxapj004m9iuvb64t2det"/>
  <title>Scheduled SMS API outage 2025-09-17 01:00</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 30 minutes</p>
    <p><strong>Affected Components:</strong> SMS &amp; Mobile</p>
    <p><small>Sep <var data-var='date'> 16</var>, <var data-var='time'>13:30:00</var> GMT+0</small><br /><strong>Completed</strong> -
  Maintenance has completed successfully.</p>
<p><small>Sep <var data-var='date'> 16</var>, <var data-var='time'>13:00:01</var> GMT+0</small><br /><strong>Identified</strong> -
  Maintenance is now in progress.</p>
<p><small>Sep <var data-var='date'> 16</var>, <var data-var='time'>13:00:00</var> GMT+0</small><br /><strong>Identified</strong> -
  We are writing to inform you of a scheduled outage within the Aatrox Network.  
  
Outage and Impacts:  
Expected duration: 30 minutes

Impact:  
During the outage, the SMS API will be unavailable, meaning No Outbound SMS can be sent using our API, and inbound SMS messages will be delayed.  
  
Note: No data loss is expected, and normal operations will resume after the outage.

  
Work Start: 2025-09-17 01:00  
Work End: 2025-09-17 01:30  
Time Zone: Australian Eastern Standard Time (AEST - Australia/Brisbane)  
Outage Duration: 30m.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:aatroxcommunications.instatus.com,2005:Incident/cmbr359k30009r35gpaaqa11m</id>
  <published>2025-06-10T22:21:25.751+00:00</published>
  <updated>2025-06-11T01:29:37.157+00:00</updated>
  <link rel="alternate" type="text/html" href="https://aatroxcommunications.instatus.com/incident/cmbr359k30009r35gpaaqa11m"/>
  <title>Outbound SMS getting - Unknown or 500 server error</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 3 hours and 8 minutes</p>
    <p><strong>Affected Components:</strong> SMS &amp; Mobile</p>
    <p><small>Jun <var data-var='date'> 11</var>, <var data-var='time'>01:29:37</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Jun <var data-var='date'> 10</var>, <var data-var='time'>22:21:25</var> GMT+0</small><br /><strong>Monitoring</strong> -
  We are currently investigating this incident related to outbound SMS messages returning an unknown error or a 500 Internal Server Error. Messages are being received by our gateway, but an upstream provider is failing to process the message. We have reported the error to them and will post updates as they become available. .</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:aatroxcommunications.instatus.com,2005:Incident/cmbjxcxmv001n1149eyvn8qdo</id>
  <published>2025-06-05T22:05:02.426+00:00</published>
  <updated>2025-06-05T22:32:42.458+00:00</updated>
  <link rel="alternate" type="text/html" href="https://aatroxcommunications.instatus.com/incident/cmbjxcxmv001n1149eyvn8qdo"/>
  <title>Broadband outage reported</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 28 minutes</p>
    <p><strong>Affected Components:</strong> New Zealand Ultra-Fast Broadband</p>
    <p><small>Jun <var data-var='date'> 5</var>, <var data-var='time'>22:32:42</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Jun <var data-var='date'> 5</var>, <var data-var='time'>22:05:02</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are currently investigating this incident..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:aatroxcommunications.instatus.com,2005:Maintenance/cmaxcl8cf0024poz0bkk3qr9s</id>
  <published>2025-05-22T11:00:00.000+00:00</published>
  <updated>2025-05-22T14:00:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://aatroxcommunications.instatus.com/maintenance/cmaxcl8cf0024poz0bkk3qr9s"/>
  <title>Planned Hazardous Work Notification - Virtual Mobile Numbers</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 3 hours</p>
    <p><strong>Affected Components:</strong> SIP Trunking (Australia), SMS &amp; Mobile</p>
    <p><small>May <var data-var='date'> 22</var>, <var data-var='time'>14:00:00</var> GMT+0</small><br /><strong>Completed</strong> -
  Maintenance has completed successfully.</p>
<p><small>May <var data-var='date'> 22</var>, <var data-var='time'>11:00:01</var> GMT+0</small><br /><strong>Identified</strong> -
  Maintenance is now in progress.</p>
<p><small>May <var data-var='date'> 22</var>, <var data-var='time'>11:00:00</var> GMT+0</small><br /><strong>Identified</strong> -
  We wish to advise that the following _Planned Hazardous Work_ has been scheduled:

Note - This only affects Virtual Mobile Numbers hosted on `nsip.aatroxcommunications.com.au`

---

**Start Date/Time:**  
May 22nd, 2025 – 23:00 (AEST)

**End Date/Time:**  
May 23ed, 2025 – 02:00 (AEST)

**Location:**  
Nationwide (Affecting only Virtual Mobile Numbers hosted on `nsip.aatroxcommunications.com.au`)

**Impact:**  
Hazardous Work – During the service window, we anticipate that services will experience several outages. 

---

**Description of Work:**  
Capacity upgrades and maintenance will be performed on devices within our upstream provider&#039;s network. These improvements are part of our ongoing efforts to enhance product development, ensure continuity, and support the Aatrox voice portfolio.

During the service window, we anticipate that services will experience several outages. 

For the duration of the works, appropriate Engineers will be onsite managing and monitoring all aspects of the works. 

If you require assistance, please contact us:

Phone: 1300 645 699  
Email: support@aatroxcommunications.com.au.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:aatroxcommunications.instatus.com,2005:Incident/cmax23p8l009reko7h3x9bqlz-9zmmm936gmyv</id>
  <published>2025-04-09T21:16:27.485+00:00</published>
  <updated>2025-04-09T23:02:58.340+00:00</updated>
  <link rel="alternate" type="text/html" href="https://aatroxcommunications.instatus.com/incident/cmax23p8l009reko7h3x9bqlz-9zmmm936gmyv"/>
  <title>SIP tunks Flapping Audio issues on nsip.aatroxcommunications.com.au SIP trunks</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> SIP Trunking (Australia)</p>
    <p><small>Apr <var data-var='date'> 9</var>, <var data-var='time'>23:02:58</var> GMT+0</small><br /><strong>Resolved</strong> -
  We have not seen any further issues related to this outage.

If you continue to experience issues, please reach out to our support team..</p>
<p><small>Apr <var data-var='date'> 9</var>, <var data-var='time'>21:57:37</var> GMT+0</small><br /><strong>Monitoring</strong> -
  Our upstream provider had implemented a fix, and our monitoring is showing that SIP trunks are stable as of 0740 AEST. We also see calls connecting as expected.

Our team will continue to monitor the network.

If you continue to experience issues, please reach out to our support team..</p>
<p><small>Apr <var data-var='date'> 9</var>, <var data-var='time'>21:16:27</var> GMT+0</small><br /><strong>Identified</strong> -
  We have been made aware that SIP trunks are &quot;Flapping&quot; and users are unable to make or receive calls across the nsip.aatroxcommunications.com.au.

This appears to be a core network fault with one of our Tier 1 providers. Our upstream carrier is aware of the issue and is working to resolve this now..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:aatroxcommunications.instatus.com,2005:Incident/cmax23p8l009weko75g19eze3-kk662mfc3y3x</id>
  <published>2025-04-04T07:36:31.009+00:00</published>
  <updated>2025-04-04T07:43:54.005+00:00</updated>
  <link rel="alternate" type="text/html" href="https://aatroxcommunications.instatus.com/incident/cmax23p8l009weko75g19eze3-kk662mfc3y3x"/>
  <title>NBN Outage - VIC, WA, QLD, NT</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> NBN Broadband</p>
    <p><small>Apr <var data-var='date'> 4</var>, <var data-var='time'>07:43:54</var> GMT+0</small><br /><strong>Resolved</strong> -
  Our upstream carrier is reporting that connections are back online now.

If you continue to experience issues, please reach out to our support team..</p>
<p><small>Apr <var data-var='date'> 4</var>, <var data-var='time'>07:36:31</var> GMT+0</small><br /><strong>Investigating</strong> -
  Please be advised that we have received reports of an NBN outage affecting customers in VIC, WA, QLD and NT.
Our upstream carrier is aware of the outrage and working to resolve it.

We will keep you updated on when we know more..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:aatroxcommunications.instatus.com,2005:Incident/cmax23p8l00a5eko7796s9am1-1bhjpf0kb09w</id>
  <published>2025-03-24T22:05:07.829+00:00</published>
  <updated>2025-03-25T01:10:58.875+00:00</updated>
  <link rel="alternate" type="text/html" href="https://aatroxcommunications.instatus.com/incident/cmax23p8l00a5eko7796s9am1-1bhjpf0kb09w"/>
  <title>Outbound calls getting a 404 error</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> SIP Trunking (Australia)</p>
    <p><small>Mar <var data-var='date'> 25</var>, <var data-var='time'>01:10:58</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Mar <var data-var='date'> 24</var>, <var data-var='time'>22:48:02</var> GMT+0</small><br /><strong>Monitoring</strong> -
  Our Upstream carrier has implemented a fix and we are now seeing outbound calls connecting correctly.
If you continue to have issues, please reach out to our support team..</p>
<p><small>Mar <var data-var='date'> 24</var>, <var data-var='time'>22:24:06</var> GMT+0</small><br /><strong>Identified</strong> -
  Our upstream carrier is in the process or migrating traffic to an alternative path. This will help to resolve the outbound calling issue. 
Next update is expected within 30 minutes.</p>
<p><small>Mar <var data-var='date'> 24</var>, <var data-var='time'>22:05:07</var> GMT+0</small><br /><strong>Investigating</strong> -
  We have received reports that customers cannot make outbound calls and getting a 404 error from our upstream carrier.

Our upstream carrier is currently investigating this and we will provide an update as soon as we have one.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:aatroxcommunications.instatus.com,2005:Incident/cmax23p8l00a0eko7bg8450ui-b1v15n0m7gzh</id>
  <published>2025-03-23T23:21:18.000+00:00</published>
  <updated>2025-04-04T07:27:19.057+00:00</updated>
  <link rel="alternate" type="text/html" href="https://aatroxcommunications.instatus.com/incident/cmax23p8l00a0eko7bg8450ui-b1v15n0m7gzh"/>
  <title>DrayTek Routers Dropping Connections</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> NBN Broadband, New Zealand Ultra-Fast Broadband</p>
    <p><small>Apr <var data-var='date'> 4</var>, <var data-var='time'>07:27:19</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Mar <var data-var='date'> 23</var>, <var data-var='time'>23:22:08</var> GMT+0</small><br /><strong>Monitoring</strong> -
  We are continuing to monitor for any further issues..</p>
<p><small>Mar <var data-var='date'> 23</var>, <var data-var='time'>23:21:18</var> GMT+0</small><br /><strong>Monitoring</strong> -
  Hello, 

Aatrox Communications and many other ISPs both in AU and internationally have started seeing a couple of DrayTek CVE&#039;s being exploited over the last ~24 hours.

More info can be found here:
https://www.draytek.com/about/security-advisory/buffer-overflow-vulnerabilities-(cve-2024-51138-cve-2024-51139)
https://www.draytek.com/about/security-advisory/denial-of-service,-information-disclosure,-and-code-execution-vulnerabilities

It&#039;s important that if you are using a Draytek router you update the firmware to patch the vulnerabilities as soon as possible. 

Draytek router firmware can be found here - https://www.draytek.com/support/resources/routers#version

Instructions on updating firmware can be found here- https://www.draytek.co.uk/support/guides/kb-firmwareupgrade-webui

Once patched, check that Remote Management and router-side VPNs are turned off.

1) Disable Remote Management by going to [System Maintenance] &gt; [Remote Management].
2) Disable SSL VPN Service by going to [VPN and Remote Access] &gt; [Remote Access Control].
3) Reboot the router and reconnect the WAN cable.
4) Monitor the connection to see if the WAN remains stable.

If you need help, please reach out to our support team..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:aatroxcommunications.instatus.com,2005:Incident/cmax23p8l00aaeko755ow4dn7-86j1z2lbyw07</id>
  <published>2025-01-15T22:20:10.943+00:00</published>
  <updated>2025-01-16T01:21:52.196+00:00</updated>
  <link rel="alternate" type="text/html" href="https://aatroxcommunications.instatus.com/incident/cmax23p8l00aaeko755ow4dn7-86j1z2lbyw07"/>
  <title>NBN Outage affecting NSW and VIC</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> NBN Broadband</p>
    <p><small>Jan <var data-var='date'> 16</var>, <var data-var='time'>01:21:52</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Jan <var data-var='date'> 15</var>, <var data-var='time'>22:37:18</var> GMT+0</small><br /><strong>Monitoring</strong> -
  Our internal network logs show connections coming back online.
We will monitor this and update accordingly.

If you are still experiencing issues, please reboot your router and get in touch with our support team..</p>
<p><small>Jan <var data-var='date'> 15</var>, <var data-var='time'>22:20:11</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are aware of an outage affecting the NBN network in Victoria and New South Wales.
There is no ETA on this and we are awaiting updates from NBN co

Next update will be provided in one hour..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:aatroxcommunications.instatus.com,2005:Incident/cmax23p8l00aeeko7gdhi28pp-rjw9tlnb294l</id>
  <published>2024-12-10T00:50:41.809+00:00</published>
  <updated>2024-12-10T07:07:58.288+00:00</updated>
  <link rel="alternate" type="text/html" href="https://aatroxcommunications.instatus.com/incident/cmax23p8l00aeeko7gdhi28pp-rjw9tlnb294l"/>
  <title>3CX SMTP (Email Server) Outage</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> , 
PABX Hosting →</p>
    <p><small>Dec <var data-var='date'> 10</var>, <var data-var='time'>07:07:58</var> GMT+0</small><br /><strong>Resolved</strong> -
  3CX has resolved this issue..</p>
<p><small>Dec <var data-var='date'> 10</var>, <var data-var='time'>00:50:41</var> GMT+0</small><br /><strong>Investigating</strong> -
  We have seen reports of an outage affecting the 3CX SMTP (Email) service. This means emails coming from 3CX will not reach users.
This has been reported and we will let you know once it&#039;s resolved..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:aatroxcommunications.instatus.com,2005:Incident/cmax23p8l00aieko7b3uxgjn1-ykpm3tpv7n13</id>
  <published>2024-12-04T22:05:24.353+00:00</published>
  <updated>2024-12-04T23:28:35.633+00:00</updated>
  <link rel="alternate" type="text/html" href="https://aatroxcommunications.instatus.com/incident/cmax23p8l00aieko7b3uxgjn1-ykpm3tpv7n13"/>
  <title>Network Outage affecting inbound calls from ONE.NZ</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> SIP Trunking (New Zealand)</p>
    <p><small>Dec <var data-var='date'> 4</var>, <var data-var='time'>23:28:35</var> GMT+0</small><br /><strong>Resolved</strong> -
  The upstream mitigations have fixed all calling issues. Testing and monitoring confirms no further problems. Please open a support ticket via normal support process with examples for any issues going forward..</p>
<p><small>Dec <var data-var='date'> 4</var>, <var data-var='time'>22:46:22</var> GMT+0</small><br /><strong>Monitoring</strong> -
  Upstream mitigations are in place and inbound and outbound calling appear to be operating as expected.
Due to the nature of the mitigation, the occasional call may still be affected.
Works continue to fully resolve the issue.
Please let us know if you continue to experience these calling issues..</p>
<p><small>Dec <var data-var='date'> 4</var>, <var data-var='time'>22:37:44</var> GMT+0</small><br /><strong>Investigating</strong> -
  Emergency mitigation has resolved issues affecting outbound calling. Further mitigation is being implemented to resolve inbound issues..</p>
<p><small>Dec <var data-var='date'> 4</var>, <var data-var='time'>22:24:04</var> GMT+0</small><br /><strong>Investigating</strong> -
  Engineers continue to work with upstream providers to resolve this issue..</p>
<p><small>Dec <var data-var='date'> 4</var>, <var data-var='time'>22:05:48</var> GMT+0</small><br /><strong>Investigating</strong> -
  Inbound calls from the One NZ network appear to be experiencing a very large post-dial delay.

The issue appears to be upstream - engineers are working with upstream providers to resolve it..</p>
<p><small>Dec <var data-var='date'> 4</var>, <var data-var='time'>22:05:24</var> GMT+0</small><br /><strong>Investigating</strong> -
  We have received reports of calls from the One NZ network not being received. Engineers are currently investigating.

The update will follow as more information becomes available.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:aatroxcommunications.instatus.com,2005:Incident/cmax23p8l00aqeko74vyi738u-mdkdmspbdnxs</id>
  <published>2024-12-02T22:47:28.000+00:00</published>
  <updated>2024-12-03T03:17:42.458+00:00</updated>
  <link rel="alternate" type="text/html" href="https://aatroxcommunications.instatus.com/incident/cmax23p8l00aqeko74vyi738u-mdkdmspbdnxs"/>
  <title>Voice - Service Degradation - Investigating</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> SIP Trunking (Australia)</p>
    <p><small>Dec <var data-var='date'> 3</var>, <var data-var='time'>03:17:42</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Dec <var data-var='date'> 3</var>, <var data-var='time'>00:46:22</var> GMT+0</small><br /><strong>Monitoring</strong> -
  Our upstream provider has implemented a fix for this and we are seeing an improvement in call quality across the network.

We will monitor this and post a PIR once this comes in.

If you continue to have issues, please email support@aatroxcommunications.com.au.</p>
<p><small>Dec <var data-var='date'> 2</var>, <var data-var='time'>23:47:57</var> GMT+0</small><br /><strong>Investigating</strong> -
  Our upstream provider is still investigating the root cause of this.
The next update will be in 30 minutes.</p>
<p><small>Dec <var data-var='date'> 2</var>, <var data-var='time'>22:47:28</var> GMT+0</small><br /><strong>Investigating</strong> -
  Please be advised that we are receiving reports that some voice services are currently experiencing call quality issues on the nsip.aatroxcommunications.com.au network.

Our upstream engineers are working to establish the cause of this and we will update you shortly.

Further updates will be provided shortly..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:aatroxcommunications.instatus.com,2005:Incident/cmax23p8l00aveko74cm40kf3-4l81s1fqywms</id>
  <published>2024-11-24T22:26:54.485+00:00</published>
  <updated>2024-12-02T22:45:17.539+00:00</updated>
  <link rel="alternate" type="text/html" href="https://aatroxcommunications.instatus.com/incident/cmax23p8l00aveko74cm40kf3-4l81s1fqywms"/>
  <title>[Security Alert] - Grandstream GDMS Portal Compromised</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> SIP Trunking (Australia)</p>
    <p><small>Dec <var data-var='date'> 2</var>, <var data-var='time'>22:45:17</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Nov <var data-var='date'> 24</var>, <var data-var='time'>22:26:54</var> GMT+0</small><br /><strong>Monitoring</strong> -
  Note: This is only applicable if you use the Grandstream GDMS Portal to manage your Grandstream hardware.

This is a courtesy email to inform all of our customers and partners utilising the Grandstream GDMS system to provision their equipment that the GDMS system itself has been compromised in the last few days. Grandstream has sent out an advisory which we have linked to in the image below:

We recommend that any partners who use the GDMS system immediately update all their passwords as they have likely been compromised. There is some discussion on the forum post below if you want more information. 

https://www.reddit.com/r/VOIP/comments/1gxp29l/grandstream_sends_notice_of_gdms_security_incident/

Please be assured that our Aatrox systems have not been compromised in any way and this exploit is specific to the Grandstream GDMS platform which we are not affiliated with in any way. 

However, we do know that many of our partners prefer to use GDMS instead of their PBX phone provisioning system. We advise that customers who are concerned about the security of the GDMS system switch to using their PBX phone provisioning system instead. We cannot comment on the current state of GDMS or whether it is safe to continue using it going forward. Unless there is a specific reason to continue using GDMS, we recommend that affected customers update their account passwords and switch to using our provisioning systems instead.

If you have any questions feel free to reach out to our team but keep in mind that we do not have any more information on the Grandstream Portal compromise other than what has been reported above..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:aatroxcommunications.instatus.com,2005:Maintenance/cmax23p8m00bpeko72wrj6fmu-1xrz3kdvdsdx</id>
  <published>2023-11-18T01:00:00.000+00:00</published>
  <updated>2023-11-18T04:00:22.908+00:00</updated>
  <link rel="alternate" type="text/html" href="https://aatroxcommunications.instatus.com/maintenance/cmax23p8m00bpeko72wrj6fmu-1xrz3kdvdsdx"/>
  <title>App Portal System Maintenance.</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 3 hours</p>
    <p><strong>Affected Components:</strong> App Portal</p>
    <p><small>Nov <var data-var='date'> 18</var>, <var data-var='time'>04:00:22</var> GMT+0</small><br /><strong>Completed</strong> -
  The scheduled maintenance has been completed..</p>
<p><small>Nov <var data-var='date'> 18</var>, <var data-var='time'>01:00:25</var> GMT+0</small><br /><strong>Identified</strong> -
  Scheduled maintenance is currently in progress. We will provide updates as necessary..</p>
<p><small>Nov <var data-var='date'> 17</var>, <var data-var='time'>23:59:59</var> GMT+0</small><br /><strong>Identified</strong> -
  Maintenance will begin as scheduled in 60 minutes..</p>
<p><small>Nov <var data-var='date'> 14</var>, <var data-var='time'>01:49:39</var> GMT+0</small><br /><strong>Identified</strong> -
  We will be undergoing scheduled maintenance during this time..</p>
<p><small>Nov <var data-var='date'> 14</var>, <var data-var='time'>01:48:49</var> GMT+0</small><br /><strong>Identified</strong> -
  We will be undergoing scheduled maintenance during this time..</p>
<p><small>Nov <var data-var='date'> 14</var>, <var data-var='time'>01:47:17</var> GMT+0</small><br /><strong>Identified</strong> -
  Please be aware that the App Portal will be unavailable for approximately 3 hours on Saturday Nov 18th between 11am AEST / 12pm AEDT and 5pm AEST / 6PM AEDT while we conduct system maintenance..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:aatroxcommunications.instatus.com,2005:Maintenance/cmax23p8m00c6eko71airav8k-xjyzftn424zz</id>
  <published>2023-02-09T14:00:00.000+00:00</published>
  <updated>2023-02-09T18:00:21.400+00:00</updated>
  <link rel="alternate" type="text/html" href="https://aatroxcommunications.instatus.com/maintenance/cmax23p8m00c6eko71airav8k-xjyzftn424zz"/>
  <title>Aatrox Communications - Digital Fax - Upcoming Planned Works - 10/02/2023</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 4 hours</p>
    <p><strong>Affected Components:</strong> Digital Fax</p>
    <p><small>Feb <var data-var='date'> 9</var>, <var data-var='time'>18:00:21</var> GMT+0</small><br /><strong>Completed</strong> -
  The scheduled maintenance has been completed..</p>
<p><small>Feb <var data-var='date'> 9</var>, <var data-var='time'>14:00:19</var> GMT+0</small><br /><strong>Identified</strong> -
  Scheduled maintenance is currently in progress. We will provide updates as necessary..</p>
<p><small>Feb <var data-var='date'> 9</var>, <var data-var='time'>12:59:59</var> GMT+0</small><br /><strong>Identified</strong> -
  Maintenance will begin as scheduled in 60 minutes..</p>
<p><small>Feb <var data-var='date'> 7</var>, <var data-var='time'>00:04:24</var> GMT+0</small><br /><strong>Identified</strong> -
  We wish to advise the following planned work has been scheduled for our Digital Fax Platform.

Start Date/Time: 10/02/23 - 01:00 AM AEDT
End Date/Time: 10/02/23 - 05:00 AM AEDT
Location: Nationwide, Only affecting mobile number hosting on our Digital Fax platform.

Impact: Service Impacting.

Expected Outage: 10/02/23 - 02:00 AM to 4:00 AM AEDT

Description of Work: Interruption for short periods during the planned work window.

We are making physical changes to Fibre paths between data centres and upgrades to Network Devices. The upgrades will improve network connectivity to the Digital Fax product and increase capacity for future growth.

Capacity upgrades and maintenance to our platforms is an important step to allow product development, continuity and support of the Aatrox portfolio.

There will be service interruption for short periods during the planned work window and it may trigger alerts for any customers monitoring the platform connectivity and response times. The interruptions will be kept to a minimum.

We apologise for any inconvenience this work may cause.

If you require assistance, please do not hesitate to call us on 0383972990 or email support@aatroxcommunications.com.au.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:aatroxcommunications.instatus.com,2005:Maintenance/cmax23p8m00cceko73cfodzvw-8ws5htp842y7</id>
  <published>2022-08-03T13:00:00.000+00:00</published>
  <updated>2022-08-03T18:00:35.075+00:00</updated>
  <link rel="alternate" type="text/html" href="https://aatroxcommunications.instatus.com/maintenance/cmax23p8m00cceko73cfodzvw-8ws5htp842y7"/>
  <title>Core Network Maintenance - (nsip.aatroxcommunications.com.au Only)</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 5 hours</p>
    <p><strong>Affected Components:</strong> SIP Trunking (Australia)</p>
    <p><small>Aug <var data-var='date'> 3</var>, <var data-var='time'>18:00:35</var> GMT+0</small><br /><strong>Completed</strong> -
  The scheduled maintenance has been completed..</p>
<p><small>Aug <var data-var='date'> 3</var>, <var data-var='time'>13:00:37</var> GMT+0</small><br /><strong>Identified</strong> -
  Scheduled maintenance is currently in progress. We will provide updates as necessary..</p>
<p><small>Aug <var data-var='date'> 3</var>, <var data-var='time'>12:00:22</var> GMT+0</small><br /><strong>Identified</strong> -
  Maintenance will begin as scheduled in 60 minutes..</p>
<p><small>Aug <var data-var='date'> 3</var>, <var data-var='time'>08:20:37</var> GMT+0</small><br /><strong>Identified</strong> -
  We wish to advise the following Planned Hazardous Work has been scheduled.

Start Date/Time: 03-08-2022 23:00:00 AEDT
End Date/Time: 04-08-2022 06:00:00 AEDT
Location: Nationwide

Impact: Hazardous.
Expected Outage: No Service Impact

Description of Work:
Third party equipment maintenance.
Only affecting numbers hosted on nsip.aatroxcommunications.com.au

This work is not expected to be service affecting, and you should not notice any change in the behaviour of your services.

We apologise for any inconvenience this work may cause.

If you require assistance, please do not hesitate to call us on 0383972990 or email support@aatroxcommunications.com.au.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:aatroxcommunications.instatus.com,2005:Maintenance/cmax23p8m00cieko72gvvbg8x-q6385gf869vp</id>
  <published>2022-01-28T10:00:00.000+00:00</published>
  <updated>2022-01-28T19:00:30.793+00:00</updated>
  <link rel="alternate" type="text/html" href="https://aatroxcommunications.instatus.com/maintenance/cmax23p8m00cieko72gvvbg8x-q6385gf869vp"/>
  <title>Core Network Maintenance - (sip.aatroxcommunications.com.au Only)</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 9 hours</p>
    <p><strong>Affected Components:</strong> SIP Trunking (Australia)</p>
    <p><small>Jan <var data-var='date'> 28</var>, <var data-var='time'>19:00:30</var> GMT+0</small><br /><strong>Completed</strong> -
  The scheduled maintenance has been completed..</p>
<p><small>Jan <var data-var='date'> 28</var>, <var data-var='time'>10:01:37</var> GMT+0</small><br /><strong>Identified</strong> -
  Scheduled maintenance is currently in progress. We will provide updates as necessary..</p>
<p><small>Jan <var data-var='date'> 28</var>, <var data-var='time'>08:59:31</var> GMT+0</small><br /><strong>Identified</strong> -
  Maintenance will begin as scheduled in 60 minutes..</p>
<p><small>Jan <var data-var='date'> 27</var>, <var data-var='time'>08:30:26</var> GMT+0</small><br /><strong>Identified</strong> -
  We wish to advise the following Planned Hazardous Work has been scheduled.

Start Date/Time: 28-01-2022 21:00:00 AEDT
End Date/Time: 29-01-2022 06:00:00 AEDT
Location: Nationwide, Only affecting hosting on sip.aatroxcommunications.com.au

Impact: Hazardous.
Expected Outage: No Service Impact

Description of Work:
Regular patching four our sip.aatroxcommunications.com.au Application server.

The application server (AS) will be locked as per our maintenance plan. This will force registrations to move to the secondary AS.

Capacity upgrades and maintenance to our platforms is an important step to allow product development, continuity and support of the Aatrox voice portfolio.

This work is not expected to be service affecting, and you should not notice any change in the behaviour of your services.

We apologise for any inconvenience this work may cause.

If you require assistance, please do not hesitate to call us on 0383972990 or email support@aatroxcommunications.com.au.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:aatroxcommunications.instatus.com,2005:Maintenance/cmax23p8m00cneko70emqccr9-qnsnfhkw1kds</id>
  <published>2021-12-07T10:00:00.000+00:00</published>
  <updated>2021-12-07T12:00:30.025+00:00</updated>
  <link rel="alternate" type="text/html" href="https://aatroxcommunications.instatus.com/maintenance/cmax23p8m00cneko70emqccr9-qnsnfhkw1kds"/>
  <title>Core Network Capacity Upgrades &amp; Maintenance - (Mobile Hosting Only)</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 2 hours</p>
    <p><strong>Affected Components:</strong> SMS &amp; Mobile</p>
    <p><small>Dec <var data-var='date'> 7</var>, <var data-var='time'>12:00:30</var> GMT+0</small><br /><strong>Completed</strong> -
  The scheduled maintenance has been completed..</p>
<p><small>Dec <var data-var='date'> 7</var>, <var data-var='time'>10:00:41</var> GMT+0</small><br /><strong>Identified</strong> -
  Scheduled maintenance is currently in progress. We will provide updates as necessary..</p>
<p><small>Dec <var data-var='date'> 7</var>, <var data-var='time'>08:59:31</var> GMT+0</small><br /><strong>Identified</strong> -
  Maintenance will begin as scheduled in 60 minutes..</p>
<p><small>Dec <var data-var='date'> 6</var>, <var data-var='time'>23:14:37</var> GMT+0</small><br /><strong>Identified</strong> -
  We wish to advise the following Planned Hazardous Work has been scheduled.

Start Date/Time:  2021-12-07 21:00 AET
End Date/Time:  2021-12-07 23:00 AET

Location: Nationwide, Only affecting outbount mobile hosting on nsip.aatroxcommunications.com.au

Impact: Hazardous.

Expected Outage: No Service Impact

Description of Work:

Capacity upgrades and maintenance will be performed on devices within our network between 21:00 and 23:00 (AEST), commencing on December the 7th, 2021.

Capacity upgrades and maintenance to our platforms is an important step to allow product development, continuity and support of the Aatrox voice portfolio.

The change has been performed in our lab with no impact and significant regression testing has been completed.

This work is not expected to be service affecting, and you should not notice any change in the behaviour of your services.

We apologise for any inconvenience this work may cause.

If you require assistance, please do not hesitate to call us on 0383972990 or email support@aatroxcommunications.com.au.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:aatroxcommunications.instatus.com,2005:Maintenance/cmax23p8n00cteko7cjxy2h1b-13brm1sqk691</id>
  <published>2021-11-10T10:00:00.000+00:00</published>
  <updated>2021-11-10T13:00:35.497+00:00</updated>
  <link rel="alternate" type="text/html" href="https://aatroxcommunications.instatus.com/maintenance/cmax23p8n00cteko7cjxy2h1b-13brm1sqk691"/>
  <title>Core Network Capacity Upgrades &amp; Maintenance - (Mobile Hosting Only)</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 3 hours</p>
    <p><strong>Affected Components:</strong> SMS &amp; Mobile</p>
    <p><small>Nov <var data-var='date'> 10</var>, <var data-var='time'>13:00:35</var> GMT+0</small><br /><strong>Completed</strong> -
  The scheduled maintenance has been completed..</p>
<p><small>Nov <var data-var='date'> 10</var>, <var data-var='time'>10:02:08</var> GMT+0</small><br /><strong>Identified</strong> -
  Scheduled maintenance is currently in progress. We will provide updates as necessary..</p>
<p><small>Nov <var data-var='date'> 9</var>, <var data-var='time'>04:36:55</var> GMT+0</small><br /><strong>Identified</strong> -
  We will be undergoing scheduled maintenance during this time..</p>
<p><small>Nov <var data-var='date'> 9</var>, <var data-var='time'>04:36:27</var> GMT+0</small><br /><strong>Identified</strong> -
  We wish to advise the following Planned Hazardous Work has been scheduled.

Start Date/Time: 10-11-2021 21:00:00 AEST
End Date/Time: 10-11-2021 03:59:00 AEST
Location: Nationwide, Only affecting mobile number hosting on nsip.aatroxcommunications.com.au
Impact: Hazardous

Expected Outage: No Service Impact

Description of Work:

Capacity upgrades and maintenance will be performed on devices within our network between 21:00 and 23:00 (AEST), commencing on November the 10th, 2021.

Capacity upgrades and maintenance to our platforms is an important step to allow product development, continuity and support of the Aatrox voice portfolio.

The change has been performed in our lab with no impact and significant regression testing has been completed.

This work is not expected to be service affecting, and you should not notice any change in the behaviour of your services.

We apologise for any inconvenience this work may cause.

If you require assistance, please do not hesitate to call us on 0383972990 or email support@aatroxcommunications.com.au.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:aatroxcommunications.instatus.com,2005:Maintenance/cmax23p8n00cyeko78hds56mt-c7xpktsk7h4w</id>
  <published>2021-06-25T10:00:00.000+00:00</published>
  <updated>2021-06-25T20:00:29.998+00:00</updated>
  <link rel="alternate" type="text/html" href="https://aatroxcommunications.instatus.com/maintenance/cmax23p8n00cyeko78hds56mt-c7xpktsk7h4w"/>
  <title>Planned Hazardous Work - 25-06-2021</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 10 hours</p>
    <p><strong>Affected Components:</strong> SIP Trunking (Australia)</p>
    <p><small>Jun <var data-var='date'> 25</var>, <var data-var='time'>20:00:29</var> GMT+0</small><br /><strong>Completed</strong> -
  The scheduled maintenance has been completed..</p>
<p><small>Jun <var data-var='date'> 25</var>, <var data-var='time'>10:00:36</var> GMT+0</small><br /><strong>Identified</strong> -
  Scheduled maintenance is currently in progress. We will provide updates as necessary..</p>
<p><small>Jun <var data-var='date'> 25</var>, <var data-var='time'>09:00:32</var> GMT+0</small><br /><strong>Identified</strong> -
  Maintenance will begin as scheduled in 60 minutes..</p>
<p><small>Jun <var data-var='date'> 16</var>, <var data-var='time'>04:58:34</var> GMT+0</small><br /><strong>Identified</strong> -
  We wish to advise the following Planned Hazardous Work has been scheduled.

Start Date/Time: 25-06-2021 20:00:00 AEST
End Date/Time: 26-06-2021 06:00:00 AEST
Location: Nationwide
Impact: Hazardous

Expected Outage: No Service Impact

Description of Work:

Please be advised that we will be updating software on core voice platform between 20:00 and 06:00 (AEST), commencing on June the 25th, 2021.

Software updates to our platforms is an important step to allow product development, continuity and support of the Aatrox voice portfolio.

The change has been performed in our lab with no impact and significant regression testing has been completed.

This work is not expected to be service affecting, and you should not notice any change in the behaviour of your services.

We apologise for any inconvenience this work may cause.

If you require assistance, please do not hesitate to call us on 0383972990 or email support@aatroxcommunications.com.au.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:aatroxcommunications.instatus.com,2005:Maintenance/cmax23p8n00d3eko7hhc57i07-yt36j72t376c</id>
  <published>2021-05-06T11:00:00.000+00:00</published>
  <updated>2021-05-06T20:00:32.598+00:00</updated>
  <link rel="alternate" type="text/html" href="https://aatroxcommunications.instatus.com/maintenance/cmax23p8n00d3eko7hhc57i07-yt36j72t376c"/>
  <title>Planned Hazardous Work - 06-05-2021</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 9 hours</p>
    <p><strong>Affected Components:</strong> SIP Trunking (Australia)</p>
    <p><small>May <var data-var='date'> 6</var>, <var data-var='time'>20:00:32</var> GMT+0</small><br /><strong>Completed</strong> -
  The scheduled maintenance has been completed..</p>
<p><small>May <var data-var='date'> 6</var>, <var data-var='time'>11:00:48</var> GMT+0</small><br /><strong>Identified</strong> -
  Scheduled maintenance is currently in progress. We will provide updates as necessary..</p>
<p><small>May <var data-var='date'> 6</var>, <var data-var='time'>10:00:30</var> GMT+0</small><br /><strong>Identified</strong> -
  Maintenance will begin as scheduled in 60 minutes..</p>
<p><small>Apr <var data-var='date'> 30</var>, <var data-var='time'>01:09:52</var> GMT+0</small><br /><strong>Identified</strong> -
  We wish to advise the following Planned Hazardous Work has been scheduled by one of our upstream providers.

Start Date/Time: 06-05-2021 21:00:00 AEST
End Date/Time: 07-05-2021 06:00:00 AEST
Location: Nationwide
Impact: Hazardous

Expected Outage: No Service Impact

Description of Work:

Please be advised that one of our upstream providers will be updating software on core Session Border Controllers (SBC) between 21:00 and 06:00 (AEST), commencing on the night of May the 6th, 2021.

Updating session border controllers is an important step to allow product development, continuity and support of the Aatrox voice portfolio.

The change has been performed in our upstream provider&#039;s lab with no impact and significant regression testing has been completed.

This work is not expected to be service affecting, and you should not notice any change in the behaviour of your services.

We apologise for any inconvenience this work may cause.

If you require assistance, please do not hesitate to call us on 0383972990 or email support@aatroxcommunications.com.au.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:aatroxcommunications.instatus.com,2005:Maintenance/cmax23p8n00d8eko7d4486oj6-3prp1m62ssp4</id>
  <published>2021-03-26T13:01:00.000+00:00</published>
  <updated>2021-03-26T19:01:29.778+00:00</updated>
  <link rel="alternate" type="text/html" href="https://aatroxcommunications.instatus.com/maintenance/cmax23p8n00d8eko7d4486oj6-3prp1m62ssp4"/>
  <title>Planned Hazardous Work - 27-03-2021</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 6 hours</p>
    <p><strong>Affected Components:</strong> SIP Trunking (Australia)</p>
    <p><small>Mar <var data-var='date'> 26</var>, <var data-var='time'>19:01:29</var> GMT+0</small><br /><strong>Completed</strong> -
  The scheduled maintenance has been completed..</p>
<p><small>Mar <var data-var='date'> 26</var>, <var data-var='time'>13:01:32</var> GMT+0</small><br /><strong>Identified</strong> -
  Scheduled maintenance is currently in progress. We will provide updates as necessary..</p>
<p><small>Mar <var data-var='date'> 26</var>, <var data-var='time'>12:00:40</var> GMT+0</small><br /><strong>Identified</strong> -
  Maintenance will begin as scheduled in 60 minutes..</p>
<p><small>Mar <var data-var='date'> 10</var>, <var data-var='time'>01:29:37</var> GMT+0</small><br /><strong>Identified</strong> -
  We wish to advise the following Planned maintance has been scheduled by one of our upstream providers.

Work Start Date/Time: 27/03/2021 00:00 AEDT
Work End Date/Time: 27/03/2021 06:00 AEDT

Location of Work: Sydney
Impact: Hazardous

Description of Work:
One of our upstream providers is performing software upgrades to their voice infrastructure during the above change window.
Network infrastructure will be monitored during and after the change and it is not expected that there will be any customer impact during this time.

If you have any questions, please emial support@aatroxcommunications.com.au or call 0383972990.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:aatroxcommunications.instatus.com,2005:Maintenance/cmax23p8n00dheko78pcqa5mb-lfnwvmh1fq1j</id>
  <published>2021-01-29T11:00:00.000+00:00</published>
  <updated>2021-01-29T14:00:31.741+00:00</updated>
  <link rel="alternate" type="text/html" href="https://aatroxcommunications.instatus.com/maintenance/cmax23p8n00dheko78pcqa5mb-lfnwvmh1fq1j"/>
  <title>Planned Hazardous Work - 29-01-2021</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 3 hours</p>
    <p><strong>Affected Components:</strong> SIP Trunking (Australia)</p>
    <p><small>Jan <var data-var='date'> 29</var>, <var data-var='time'>14:00:31</var> GMT+0</small><br /><strong>Completed</strong> -
  The scheduled maintenance has been completed..</p>
<p><small>Jan <var data-var='date'> 29</var>, <var data-var='time'>11:00:36</var> GMT+0</small><br /><strong>Identified</strong> -
  Scheduled maintenance is currently in progress. We will provide updates as necessary..</p>
<p><small>Jan <var data-var='date'> 29</var>, <var data-var='time'>10:00:31</var> GMT+0</small><br /><strong>Identified</strong> -
  Maintenance will begin as scheduled in 60 minutes..</p>
<p><small>Jan <var data-var='date'> 24</var>, <var data-var='time'>22:49:59</var> GMT+0</small><br /><strong>Identified</strong> -
  We wish to advise the following Planned Hazardous Work has been scheduled by one of our upstream providers.

Start Date/Time:             29-01-2021 22:00:00 AEDT
End Date/Time:              30-01-2021 02:00:00 AEDT
Location:                         Nationwide
Impact:                            Hazardous

Expected Outage:            No Service Impact

Description of Work:

Please be advised that one of our upstream providers will be patching a core Session Border Controller (SBC) between 22:00 and 02:00 (AEDT), commencing on the night of January 29th, 2021.

Patching session border controller is an important step to allow product development, continuity and support of the Aatrox Voice portfolio.

The change has been performed in our upstream provider&#039;s lab with no impact and significant regression testing is currently underway to ensure there are no adverse effects resulting from the change.

This work is not expected to be service affecting, and you should not notice any change in the behaviour of your services.

We apologise for any inconvenience this work may cause.

If you require assistance, please do not hesitate to call us on 0383972990 or email support@aatroxcommunications.com.au.</p>

        ]]>
  </content>
</entry>

</feed>