<?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-09-02T19:00:00.000+00:00</updated>
  <author>
    <name>Exeltel Systems</name>
  </author>
  
<entry>
  <id>tag:exeltel.instatus.com,2005:Maintenance/cmt2sqxa40oxw1ameihwxfdcg</id>
  <published>2026-09-02T19:00:00.000+00:00</published>
  <updated>2026-09-02T23:00:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://exeltel.instatus.com/maintenance/cmt2sqxa40oxw1ameihwxfdcg"/>
  <title>Horizon Portal Planned Maintenance: 2nd September 2026</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 4 hours</p>
    <p><strong>Affected Components:</strong> Horizon</p>
    <p><small>Sep <var data-var='date'> 2</var>, <var data-var='time'>23:00:00</var> GMT+0</small><br /><strong>Completed</strong> -
  Maintenance has completed successfully.</p>
<p><small>Sep <var data-var='date'> 2</var>, <var data-var='time'>19:00:01</var> GMT+0</small><br /><strong>Identified</strong> -
  Maintenance is now in progress.</p>
<p><small>Aug <var data-var='date'> 21</var>, <var data-var='time'>10:18:35</var> GMT+0</small><br /><strong>Identified</strong> -
  The Horizon Portal ([www.unlimitedhorizon.co.uk](http://www.unlimitedhorizon.co.uk)) will be undergoing planned maintenance during the below windows.  
  
02nd September 20:00 - 23:55 to perform server patching  
  
During these planned works, there will be extended periods during which the Horizon Portal is unavailable.  
  
We apologise for any inconvenience..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:exeltel.instatus.com,2005:Maintenance/cmt2sn4jq0a071aplqgjkcjp7</id>
  <published>2026-08-26T19:00:00.000+00:00</published>
  <updated>2026-08-26T23:00:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://exeltel.instatus.com/maintenance/cmt2sn4jq0a071aplqgjkcjp7"/>
  <title>Horizon Portal Planned Maintenance: 26th August 2026</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 4 hours</p>
    <p><strong>Affected Components:</strong> Horizon</p>
    <p><small>Aug <var data-var='date'> 26</var>, <var data-var='time'>23:00:00</var> GMT+0</small><br /><strong>Completed</strong> -
  Maintenance has completed successfully.</p>
<p><small>Aug <var data-var='date'> 26</var>, <var data-var='time'>19:00:01</var> GMT+0</small><br /><strong>Identified</strong> -
  Maintenance is now in progress.</p>
<p><small>Aug <var data-var='date'> 21</var>, <var data-var='time'>10:15:38</var> GMT+0</small><br /><strong>Identified</strong> -
  The Horizon Portal ([www.unlimitedhorizon.co.uk](http://www.unlimitedhorizon.co.uk)) will be undergoing planned maintenance during the below windows.  
  
26th August 20:00 - 23:55 to perform server patching  
  
During these planned works, there will be extended periods during which the Horizon Portal is unavailable.  
  
We apologise for any inconvenience..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:exeltel.instatus.com,2005:Incident/cmt2shf7s0owk0kpbzqy2grjd</id>
  <published>2026-08-21T09:17:00.000+00:00</published>
  <updated>2026-08-21T17:00:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://exeltel.instatus.com/incident/cmt2shf7s0owk0kpbzqy2grjd"/>
  <title>Broadband Incident</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 7 hours and 41 minutes</p>
    <p><strong>Affected Components:</strong> Broadband</p>
    <p><small>Aug <var data-var='date'> 21</var>, <var data-var='time'>17:00:00</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Aug <var data-var='date'> 21</var>, <var data-var='time'>16:58:08</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Aug <var data-var='date'> 21</var>, <var data-var='time'>09:17:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  Good morning, we are currently experiencing issues with testing of broadband lines and may delay resolutions to faults on lines. The underlying broadband service is not impacted and is working as expected. The next update is by 1 pm today. .</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:exeltel.instatus.com,2005:Incident/cmt2ps0io0oik0zme9gej9pi2</id>
  <published>2026-08-21T08:18:00.000+00:00</published>
  <updated>2026-08-21T10:56:50.309+00:00</updated>
  <link rel="alternate" type="text/html" href="https://exeltel.instatus.com/incident/cmt2ps0io0oik0zme9gej9pi2"/>
  <title>Webex </title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 2 hours and 39 minutes</p>
    <p><strong>Affected Components:</strong> Horizon, Webex for Horizon</p>
    <p><small>Aug <var data-var='date'> 21</var>, <var data-var='time'>10:56:50</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Aug <var data-var='date'> 21</var>, <var data-var='time'>08:56:55</var> GMT+0</small><br /><strong>Monitoring</strong> -
  Cisco Engineering has confirmed that remediation activities have been completed and services have been restored to all regions. We apologise for the inconvenience this caused. We will continue to monitor, and should there be no further reports, this notice will be closed at 12:00.</p>
<p><small>Aug <var data-var='date'> 21</var>, <var data-var='time'>08:18:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are aware of an ongoing incident with Cisco which is impacting both Webex and Horizon with Webex. Users will be experiencing issues logging in to the Webex app, those users who are logged in may experience a loss of core functionality such as making and receiving calls and joining meetings. Webex users are currently unable to access the Cisco Control Hub. We will provide a further update at 10:00.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:exeltel.instatus.com,2005:Incident/cmshihcy206v40so31x8ngbbo</id>
  <published>2026-08-06T10:25:00.000+00:00</published>
  <updated>2026-08-06T14:18:03.750+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'>14:18:03</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</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'>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>

        ]]>
  </content>
</entry>

</feed>