<?xml version="1.0" encoding="UTF-8"?>
<feed xml:lang="en-US" xmlns="http://www.w3.org/2005/Atom">
  <id>tag:exeltel.instatus.com,2005:/history</id>
  <link rel="alternate" type="text/html" href="https://exeltel.instatus.com"/>
  <link rel="self" type="application/atom+xml" href="https://exeltel.instatus.com/history.atom"/>
  <title>Exeltel Systems Status - Incident history</title>
  <updated>2026-08-06T10:25:00.000+00:00</updated>
  <author>
    <name>Exeltel Systems</name>
  </author>
  
<entry>
  <id>tag:exeltel.instatus.com,2005:Incident/cmshihcy206v40so31x8ngbbo</id>
  <published>2026-08-06T10:25:00.000+00:00</published>
  <updated>2026-08-06T10:25:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://exeltel.instatus.com/incident/cmshihcy206v40so31x8ngbbo"/>
  <title>Horizon Contact Incident</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 3 hours and 53 minutes</p>
    <p><strong>Affected Components:</strong> Horizon Contact</p>
    <p><small>Aug <var data-var='date'> 6</var>, <var data-var='time'>10:25:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  Dear customer, We have identified issues with users remaining stuck in a busy status post call and users not being able to use the directory transfer capability. Both are under investigation as a priority with our engineering team. We will provide a further update by 3PM. We apologise for the inconvenience at this time..</p>
<p><small>Aug <var data-var='date'> 6</var>, <var data-var='time'>14:00:14</var> GMT+0</small><br /><strong>Identified</strong> -
  Dear customer, We have devised a change for the directory transfer issue. This change will amend the layout for transfers, please use &lt;https://agenthelp-contact.unlimitedhorizon.co.uk/docs/transferring-a-call-to-a-third-party/&gt; for guidance on this. We have not had further reports of the user remaining stuck in busy status post call since the change last night (CC-31839) but are continuing to monitor the situation closely. We will provide a further update at 9AM tomorrow. Thank you for your patience..</p>
<p><small>Aug <var data-var='date'> 6</var>, <var data-var='time'>14:18:03</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>

        ]]>
  </content>
</entry>

</feed>