<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Interakt IT Status - Incident history</title>
    <link>https://status.interakt.net.au</link>
    <description>Interakt IT</description>
    <pubDate>Fri, 23 Jan 2026 04:30:00 +0000</pubDate>
    
<item>
  <title>Microsoft 365 - Degraded Performance</title>
  <description>
    Type: Incident
    Duration: 18 hours and 11 minutes

    Affected Components: , Email, Teams, 
Microsoft 365 →
    Jan 23, 22:41:08 GMT+0 - Resolved - This incident has been resolved. Jan 23, 06:05:29 GMT+0 - Monitoring - Hi All,

Microsoft have released the latest update 23/01/26 - 3:32pm

**Current status**: We’ve a high level of confidence that the incident is largely resolved. Access to Microsoft Defender for Office, Microsoft Purview, and DNS functionality has been restored, and Exchange Online mail flow remains stable.

We&#039;re continuing to fine tune load balancing adjustments and closely monitor the impact of recent changes to support sustained recovery. While recovery efforts remain ongoing, we are methodically addressing the small number of remaining affected services to ensure full service stability.

**Scope of impact:** Any users served through an affected section of service infrastructure in the North America region may be intermittently impacted. This could affect users located in Asia-Pacific, Europe, or Latin America.

**Root cause:** We identified that the issue was caused by elevated service load resulting from reduced capacity during maintenance for a subset of North America hosted infrastructure.

Kind Regards,

Interakt IT Jan 23, 04:30:00 GMT+0 - Identified - Hi,  
  
Microsoft is currently experiencing a partial outage and degraded performance. They have identified the issue and are actively working to restore services to normal operation.

**Latest Update 23/01/26 - 2:30pm**

**Current status:** We’ve identified elevated service load combined with temporary capacity constraints during maintenance resulted in impact. We’re seeing positive signs of recovery in mail delivery, and mitigation actions are in place to better manage service load. While some connectivity impact remains between Microsoft Defender for Office, Microsoft Purview, and Exchange Online, and DNS lookup failures, engineers are actively working to restore full functionality.

**Scope of impact:** Any users served through an affected section of service infrastructure in the North America region may be intermittently impacted. This could affect users located in Asia-Pacific, Europe, or Latin America.

Live updates can be found through their service page at: [Microsoft service health status](https://status.cloud.microsoft/)

Kind Regards,

Interakt IT 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 18 hours and 11 minutes</p>
    <p><strong>Affected Components:</strong> , , </p>
    <p><small>Jan <var data-var='date'> 23</var>, <var data-var='time'>22:41:08</var> GMT+0</small><br><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Jan <var data-var='date'> 23</var>, <var data-var='time'>06:05:29</var> GMT+0</small><br><strong>Monitoring</strong> -
  Hi All,

Microsoft have released the latest update 23/01/26 - 3:32pm

**Current status**: We’ve a high level of confidence that the incident is largely resolved. Access to Microsoft Defender for Office, Microsoft Purview, and DNS functionality has been restored, and Exchange Online mail flow remains stable.

We&#039;re continuing to fine tune load balancing adjustments and closely monitor the impact of recent changes to support sustained recovery. While recovery efforts remain ongoing, we are methodically addressing the small number of remaining affected services to ensure full service stability.

**Scope of impact:** Any users served through an affected section of service infrastructure in the North America region may be intermittently impacted. This could affect users located in Asia-Pacific, Europe, or Latin America.

**Root cause:** We identified that the issue was caused by elevated service load resulting from reduced capacity during maintenance for a subset of North America hosted infrastructure.

Kind Regards,

Interakt IT.</p>
<p><small>Jan <var data-var='date'> 23</var>, <var data-var='time'>04:30:00</var> GMT+0</small><br><strong>Identified</strong> -
  Hi,  
  
Microsoft is currently experiencing a partial outage and degraded performance. They have identified the issue and are actively working to restore services to normal operation.

**Latest Update 23/01/26 - 2:30pm**

**Current status:** We’ve identified elevated service load combined with temporary capacity constraints during maintenance resulted in impact. We’re seeing positive signs of recovery in mail delivery, and mitigation actions are in place to better manage service load. While some connectivity impact remains between Microsoft Defender for Office, Microsoft Purview, and Exchange Online, and DNS lookup failures, engineers are actively working to restore full functionality.

**Scope of impact:** Any users served through an affected section of service infrastructure in the North America region may be intermittently impacted. This could affect users located in Asia-Pacific, Europe, or Latin America.

Live updates can be found through their service page at: [Microsoft service health status](https://status.cloud.microsoft/)

Kind Regards,

Interakt IT.</p>
]]>
  </content:encoded>
  <pubDate>Fri, 23 Jan 2026 04:30:00 +0000</pubDate>
  <link>https://status.interakt.net.au/incident/cmkqepotu037v8iu9xy3gsbbq</link>
  <guid>https://status.interakt.net.au/incident/cmkqepotu037v8iu9xy3gsbbq</guid>
</item>

<item>
  <title>Provider Maintenance - Primary Data Centre</title>
  <description>
    Type: Maintenance
    Duration: 12 hours

    Affected Components: Primary Data Centre
    Oct 29, 07:30:00 GMT+0 - Completed - Maintenance has completed successfully Oct 28, 19:30:01 GMT+0 - Identified - Maintenance is now in progress Oct 28, 19:30:00 GMT+0 - Identified - One of our data centre service providers has scheduled maintenance on redundancy systems. We&#039;ve been advised that no downtime is expected, all critical services will remain online.  
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 12 hours</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Oct <var data-var='date'> 29</var>, <var data-var='time'>07:30:00</var> GMT+0</small><br><strong>Completed</strong> -
  Maintenance has completed successfully.</p>
<p><small>Oct <var data-var='date'> 28</var>, <var data-var='time'>19:30:01</var> GMT+0</small><br><strong>Identified</strong> -
  Maintenance is now in progress.</p>
<p><small>Oct <var data-var='date'> 28</var>, <var data-var='time'>19:30:00</var> GMT+0</small><br><strong>Identified</strong> -
  One of our data centre service providers has scheduled maintenance on redundancy systems. We&#039;ve been advised that no downtime is expected, all critical services will remain online. .</p>
]]>
  </content:encoded>
  <pubDate>Tue, 28 Oct 2025 19:30:00 +0000</pubDate>
  <link>https://status.interakt.net.au/maintenance/cmfbyw5ph001f7o3jvvrcw9js</link>
  <guid>https://status.interakt.net.au/maintenance/cmfbyw5ph001f7o3jvvrcw9js</guid>
</item>

<item>
  <title>Access4 Disaster Recovery Testing</title>
  <description>
    Type: Maintenance
    Duration: 2 hours

    Affected Components: Interakt VOIP/Phone Services
    Oct 23, 17:00:00 GMT+0 - Completed - Maintenance has completed successfully Oct 23, 15:00:01 GMT+0 - Identified - Maintenance is now in progress Oct 23, 15:00:00 GMT+0 - Identified - Our service provider is completing Disaster Recovery Testing during this window. During this maintenance window, there may be a brief service impact if your services are registered to a single node. In such cases, active calls may drop; however, redialling will immediately restore connectivity. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 2 hours</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Oct <var data-var='date'> 23</var>, <var data-var='time'>17:00:00</var> GMT+0</small><br><strong>Completed</strong> -
  Maintenance has completed successfully.</p>
<p><small>Oct <var data-var='date'> 23</var>, <var data-var='time'>15:00:01</var> GMT+0</small><br><strong>Identified</strong> -
  Maintenance is now in progress.</p>
<p><small>Oct <var data-var='date'> 23</var>, <var data-var='time'>15:00:00</var> GMT+0</small><br><strong>Identified</strong> -
  Our service provider is completing Disaster Recovery Testing during this window. During this maintenance window, there may be a brief service impact if your services are registered to a single node. In such cases, active calls may drop; however, redialling will immediately restore connectivity..</p>
]]>
  </content:encoded>
  <pubDate>Thu, 23 Oct 2025 15:00:00 +0000</pubDate>
  <link>https://status.interakt.net.au/maintenance/cmgoq47gc00lx8hbqnkyvu0bn</link>
  <guid>https://status.interakt.net.au/maintenance/cmgoq47gc00lx8hbqnkyvu0bn</guid>
</item>

<item>
  <title>Partial Outage</title>
  <description>
    Type: Incident
    Duration: 4 hours and 30 minutes

    Affected Components: Primary Data Centre
    Aug 27, 09:09:43 GMT+0 - Resolved - Thanks for your patience. Maintenance is now complete, and we&#039;ve successfully brought impacted services back online without restoring from backup. We&#039;ll continue monitoring closesly, and complete a post-incident review to provide additional information to impacted customers as soon possible. Aug 27, 06:19:34 GMT+0 - Identified - Thank you for your ongoing patience. We&#039;ve sourced replacement hardware locally and expect repairs to be completed within 3 hours. This timeline is faster than completing a full restore of impacted customer data. The restore is ongoing in the unlikely event that the replacement hardware fails. Further updates will follow when a clearer resolution time is available. Aug 27, 05:36:20 GMT+0 - Identified - We&#039;re continuing to work on a solution to restore impacted services. Estimated time for another update is \~30 minutes. Additional work is being done to pre-stage a restore from backup, if required. Aug 27, 05:19:59 GMT+0 - Identified - This incident has reoccurred. If your services are still available, they will remain online. We&#039;re working on a more reliable solution to bring services back online. Further information will be available in \~15 minutes. Aug 27, 05:10:53 GMT+0 - Resolved - This incident has been resolved. Aug 27, 05:01:19 GMT+0 - Monitoring - We&#039;ve restored services on the impacted host and will continue to monitor for any further instability. Any required maintenance will be scheduled as soon as possible. Aug 27, 04:48:51 GMT+0 - Identified - One physical server has experienced a CPU failure. We&#039;re attempting to bring services back online now without any data loss. Further updates to follow in \~30 minutes. Aug 27, 04:40:05 GMT+0 - Investigating - We are currently investigating an incident impacting several customers in our Data Centre. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 4 hours and 30 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Aug <var data-var='date'> 27</var>, <var data-var='time'>09:09:43</var> GMT+0</small><br><strong>Resolved</strong> -
  Thanks for your patience. Maintenance is now complete, and we&#039;ve successfully brought impacted services back online without restoring from backup. We&#039;ll continue monitoring closesly, and complete a post-incident review to provide additional information to impacted customers as soon possible..</p>
<p><small>Aug <var data-var='date'> 27</var>, <var data-var='time'>06:19:34</var> GMT+0</small><br><strong>Identified</strong> -
  Thank you for your ongoing patience. We&#039;ve sourced replacement hardware locally and expect repairs to be completed within 3 hours. This timeline is faster than completing a full restore of impacted customer data. The restore is ongoing in the unlikely event that the replacement hardware fails. Further updates will follow when a clearer resolution time is available..</p>
<p><small>Aug <var data-var='date'> 27</var>, <var data-var='time'>05:36:20</var> GMT+0</small><br><strong>Identified</strong> -
  We&#039;re continuing to work on a solution to restore impacted services. Estimated time for another update is \~30 minutes. Additional work is being done to pre-stage a restore from backup, if required..</p>
<p><small>Aug <var data-var='date'> 27</var>, <var data-var='time'>05:19:59</var> GMT+0</small><br><strong>Identified</strong> -
  This incident has reoccurred. If your services are still available, they will remain online. We&#039;re working on a more reliable solution to bring services back online. Further information will be available in \~15 minutes..</p>
<p><small>Aug <var data-var='date'> 27</var>, <var data-var='time'>05:10:53</var> GMT+0</small><br><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Aug <var data-var='date'> 27</var>, <var data-var='time'>05:01:19</var> GMT+0</small><br><strong>Monitoring</strong> -
  We&#039;ve restored services on the impacted host and will continue to monitor for any further instability. Any required maintenance will be scheduled as soon as possible..</p>
<p><small>Aug <var data-var='date'> 27</var>, <var data-var='time'>04:48:51</var> GMT+0</small><br><strong>Identified</strong> -
  One physical server has experienced a CPU failure. We&#039;re attempting to bring services back online now without any data loss. Further updates to follow in \~30 minutes..</p>
<p><small>Aug <var data-var='date'> 27</var>, <var data-var='time'>04:40:05</var> GMT+0</small><br><strong>Investigating</strong> -
  We are currently investigating an incident impacting several customers in our Data Centre..</p>
]]>
  </content:encoded>
  <pubDate>Wed, 27 Aug 2025 04:40:05 +0000</pubDate>
  <link>https://status.interakt.net.au/incident/cmethktce003rz4qt4vvajlcg</link>
  <guid>https://status.interakt.net.au/incident/cmethktce003rz4qt4vvajlcg</guid>
</item>

<item>
  <title>Interakt Data Centre Maintenance</title>
  <description>
    Type: Maintenance
    Duration: 30 minutes

    Affected Components: Primary Data Centre
    Aug 25, 10:30:00 GMT+0 - Completed - Maintenance has completed successfully Aug 25, 10:00:01 GMT+0 - Identified - Maintenance is now in progress Aug 25, 10:00:00 GMT+0 - Identified - Routine maintenance. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 30 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Aug <var data-var='date'> 25</var>, <var data-var='time'>10:30:00</var> GMT+0</small><br><strong>Completed</strong> -
  Maintenance has completed successfully.</p>
<p><small>Aug <var data-var='date'> 25</var>, <var data-var='time'>10:00:01</var> GMT+0</small><br><strong>Identified</strong> -
  Maintenance is now in progress.</p>
<p><small>Aug <var data-var='date'> 25</var>, <var data-var='time'>10:00:00</var> GMT+0</small><br><strong>Identified</strong> -
  Routine maintenance..</p>
]]>
  </content:encoded>
  <pubDate>Mon, 25 Aug 2025 10:00:00 +0000</pubDate>
  <link>https://status.interakt.net.au/maintenance/cmemikrt90001ie1usi1hn03u</link>
  <guid>https://status.interakt.net.au/maintenance/cmemikrt90001ie1usi1hn03u</guid>
</item>

<item>
  <title>Scheduled Maintenance – BNE Network structure</title>
  <description>
    Type: Maintenance
    Duration: 2 hours and 7 minutes

    Affected Components: Primary Data Centre
    Apr 30, 15:35:56 GMT+0 - Completed - Maintenance has completed successfully. Apr 30, 13:29:00 GMT+0 - Identified - Maintenance is currently scheduled on 30/04/2025 starting at 11:30pm. During that time, you might feel connectivity disruptions or unavailability of the service.

We will provide updates as necessary.

Kind regards,

Network engineer - Interakt IT 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 2 hours and 7 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Apr <var data-var='date'> 30</var>, <var data-var='time'>15:35:56</var> GMT+0</small><br><strong>Completed</strong> -
  Maintenance has completed successfully..</p>
<p><small>Apr <var data-var='date'> 30</var>, <var data-var='time'>13:29:00</var> GMT+0</small><br><strong>Identified</strong> -
  Maintenance is currently scheduled on 30/04/2025 starting at 11:30pm. During that time, you might feel connectivity disruptions or unavailability of the service.

We will provide updates as necessary.

Kind regards,

Network engineer - Interakt IT.</p>
]]>
  </content:encoded>
  <pubDate>Wed, 30 Apr 2025 13:29:00 +0000</pubDate>
  <link>https://status.interakt.net.au/maintenance/cma3k6z7900204pck953lgpsv</link>
  <guid>https://status.interakt.net.au/maintenance/cma3k6z7900204pck953lgpsv</guid>
</item>

  </channel>
  </rss>