<?xml version="1.0" encoding="UTF-8"?>
<feed xml:lang="en-US" xmlns="http://www.w3.org/2005/Atom">
  <id>tag:status.haloconnect.io,2005:/history</id>
  <link rel="alternate" type="text/html" href="https://status.haloconnect.io"/>
  <link rel="self" type="application/atom+xml" href="https://status.haloconnect.io/history.atom"/>
  <title>Halo Connect Status - Incident history</title>
  <updated>2026-07-03T18:00:00.000+00:00</updated>
  <author>
    <name>Halo Connect</name>
  </author>
  
<entry>
  <id>tag:status.haloconnect.io,2005:Incident/cmr5z6s0w087x20o46pp5lwz4</id>
  <published>2026-07-03T18:00:00.000+00:00</published>
  <updated>2026-07-04T06:37:50.182+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.haloconnect.io/incident/cmr5z6s0w087x20o46pp5lwz4"/>
  <title>Duplicated immediate queries</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 2 days, 6 hours and 6 minutes</p>
    <p><strong>Affected Components:</strong> Halo API</p>
    <p><small>Jul <var data-var='date'> 4</var>, <var data-var='time'>06:37:50</var> GMT+0</small><br /><strong>Monitoring</strong> -
  We have restarted the impacted Microsoft component which has forced a reconnection of all Halo Link instances. This has resolved the duplicate immediate queries. We are currently monitoring the result..</p>
<p><small>Jul <var data-var='date'> 6</var>, <var data-var='time'>00:05:53</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Jul <var data-var='date'> 3</var>, <var data-var='time'>18:00:00</var> GMT+0</small><br /><strong>Identified</strong> -
  We are aware of an issue impacting around a third of our Halo Link fleet resulting in duplicated immediate queries. This appears to be related to a Microsoft component issue and not a result of our platform. We have raised a ticket with Microsoft and are continuing to work on a fix for this incident..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.haloconnect.io,2005:Incident/cmqfuj4q000bv2pn5aftqbh7w</id>
  <published>2026-06-15T23:00:00.000+00:00</published>
  <updated>2026-06-16T00:54:41.609+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.haloconnect.io/incident/cmqfuj4q000bv2pn5aftqbh7w"/>
  <title>High number of 503 errors</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 6 hours and 31 minutes</p>
    <p><strong>Affected Components:</strong> Halo API</p>
    <p><small>Jun <var data-var='date'> 16</var>, <var data-var='time'>00:54:41</var> GMT+0</small><br /><strong>Monitoring</strong> -
  We experienced a brief disruption to our services caused by an issue with Microsoft Azure, our cloud infrastructure provider. The issue did not originate from our own systems.

Microsoft has since resolved the issue, and we are currently monitoring to ensure services remain stable..</p>
<p><small>Jun <var data-var='date'> 16</var>, <var data-var='time'>05:31:01</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Jun <var data-var='date'> 15</var>, <var data-var='time'>23:00:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are currently investigating this incident..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.haloconnect.io,2005:Incident/cmmk1zayh08vo5hk8yylh2ds8</id>
  <published>2026-03-09T22:10:00.000+00:00</published>
  <updated>2026-03-09T22:10:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.haloconnect.io/incident/cmmk1zayh08vo5hk8yylh2ds8"/>
  <title>Multiple short periods of degraded performance and increased failure rate</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 7 days, 1 hour and 20 minutes</p>
    <p><strong>Affected Components:</strong> Halo API</p>
    <p><small>Mar <var data-var='date'> 9</var>, <var data-var='time'>22:10:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are currently investigating this incident that impacted failure rates from 8:09-8:30am and 1:00-1:30pm AEST..</p>
<p><small>Mar <var data-var='date'> 11</var>, <var data-var='time'>04:13:15</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are currently seeing similar degraded performance from 2:05pm - 2:15 AEST and are investigating..</p>
<p><small>Mar <var data-var='date'> 16</var>, <var data-var='time'>23:29:54</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has now been resolved. The bottleneck that caused degraded performance for short periods on March 10 and 11 has been removed..</p>
<p><small>Mar <var data-var='date'> 12</var>, <var data-var='time'>06:00:00</var> GMT+0</small><br /><strong>Identified</strong> -
  We are continuing to work on a fix for this incident..</p>
<p><small>Mar <var data-var='date'> 14</var>, <var data-var='time'>10:00:00</var> GMT+0</small><br /><strong>Monitoring</strong> -
  We implemented a fix and are currently monitoring the result..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.haloconnect.io,2005:Incident/cmm2ycq7y022c4eya7sinqflk</id>
  <published>2026-02-26T01:00:00.000+00:00</published>
  <updated>2026-02-26T06:17:26.921+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.haloconnect.io/incident/cmm2ycq7y022c4eya7sinqflk"/>
  <title>Multiple short periods of degraded performance and increased failure rate </title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 22 hours and 55 minutes</p>
    <p><strong>Affected Components:</strong> Halo API</p>
    <p><small>Feb <var data-var='date'> 26</var>, <var data-var='time'>06:17:26</var> GMT+0</small><br /><strong>Monitoring</strong> -
  We have identified the component causing the windows of degraded performance and have implemented a mitigation. This appears to have resolved the issue and we are continuing to monitor for any ongoing impacts..</p>
<p><small>Feb <var data-var='date'> 26</var>, <var data-var='time'>23:55:28</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Feb <var data-var='date'> 26</var>, <var data-var='time'>01:00:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are currently investigating the cause of multiple 10-minute windows of elevated failure rates today..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.haloconnect.io,2005:Incident/cmkx8zcik03j0vqph8rpxa4p7</id>
  <published>2026-01-27T23:00:00.000+00:00</published>
  <updated>2026-01-30T05:55:39.435+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.haloconnect.io/incident/cmkx8zcik03j0vqph8rpxa4p7"/>
  <title>ISP outage (AAPT) impacting Halo Link connectivity</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 2 days, 6 hours and 56 minutes</p>
    <p><strong>Affected Components:</strong> Halo API</p>
    <p><small>Jan <var data-var='date'> 30</var>, <var data-var='time'>05:55:39</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Jan <var data-var='date'> 27</var>, <var data-var='time'>23:00:00</var> GMT+0</small><br /><strong>Identified</strong> -
  We are working with practices and IT groups to help resolve issues related to an ISP outage (AAPT) impacting Halo Link connectivity.

If a practice contacts you regarding a connectivity issue after their internet has been restored, please request they restart the Halo Link service or ask them to contact Halo Connect support..</p>
<p><small>Jan <var data-var='date'> 29</var>, <var data-var='time'>05:41:25</var> GMT+0</small><br /><strong>Monitoring</strong> -
  The majority of sites have been resolved and we are working with site IT to resolve the small number remaining..</p>

        ]]>
  </content>
</entry>

</feed>