<?xml version="1.0" encoding="UTF-8"?>
<feed xml:lang="en-US" xmlns="http://www.w3.org/2005/Atom">
  <id>tag:status.nta.co.uk,2005:/history</id>
  <link rel="alternate" type="text/html" href="https://status.nta.co.uk"/>
  <link rel="self" type="application/atom+xml" href="https://status.nta.co.uk/history.atom"/>
  <title>NTA Status - Incident history</title>
  <updated>2026-04-18T13:00:00.000+00:00</updated>
  <author>
    <name>NTA</name>
  </author>
  
<entry>
  <id>tag:status.nta.co.uk,2005:Maintenance/cmn8xt6i101o5rcyion8em0t9</id>
  <published>2026-04-18T13:00:00.000+00:00</published>
  <updated>2026-04-18T13:00:01.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.nta.co.uk/maintenance/cmn8xt6i101o5rcyion8em0t9"/>
  <title>Planned Maintenance 18/04/26 14:00 - 23:59</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 10 hours</p>
    <p><strong>Affected Components:</strong> NTA Homepage, Outbound Calls, Dialer, Wallboards, UC Integration, MobeX Mobile, API, Web Interface, Cloud phone book, Handset Provisioning, Inbound Calls, Busy Lamps, MobeX Softphone</p>
    <p><small>Apr <var data-var='date'> 18</var>, <var data-var='time'>13:00:01</var> GMT+0</small><br /><strong>Identified</strong> -
  Maintenance is now in progress.</p>
<p><small>Apr <var data-var='date'> 18</var>, <var data-var='time'>23:00:00</var> GMT+0</small><br /><strong>Completed</strong> -
  Maintenance has completed successfully.</p>
<p><small>Apr <var data-var='date'> 18</var>, <var data-var='time'>13:00:00</var> GMT+0</small><br /><strong>Identified</strong> -
  We are performing essential maintenance on our core network to improve the stability of our system.

This maintenance will be carried out on Saturday 18th of April from 2pm to 11:59pm.

There may be disruption to our service during the maintenance window.

This maintenance is classed as high risk..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.nta.co.uk,2005:Maintenance/cmmbyiz44009l1be6ppw1hax7</id>
  <published>2026-04-02T21:00:00.000+00:00</published>
  <updated>2026-04-02T21:00:01.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.nta.co.uk/maintenance/cmmbyiz44009l1be6ppw1hax7"/>
  <title>Planned maintenance 02/04/26</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 7 hours</p>
    <p><strong>Affected Components:</strong> Outbound Calls, MobeX Mobile, Inbound Calls, MobeX Softphone</p>
    <p><small>Apr <var data-var='date'> 2</var>, <var data-var='time'>21:00:01</var> GMT+0</small><br /><strong>Identified</strong> -
  Maintenance is now in progress.</p>
<p><small>Apr <var data-var='date'> 3</var>, <var data-var='time'>04:00:00</var> GMT+0</small><br /><strong>Completed</strong> -
  Maintenance has completed successfully.</p>
<p><small>Apr <var data-var='date'> 2</var>, <var data-var='time'>21:00:00</var> GMT+0</small><br /><strong>Identified</strong> -
  One of our suppliers is performing maintenance on their core network.

The maintenance will be carried out on Thursday 2nd of April from 10pm to 5am.

There may be disruption to our service during the maintenance window.

This maintenance is classed as at low risk..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.nta.co.uk,2005:Maintenance/cmmbyfuup0onfu1ra839sk3ye</id>
  <published>2026-03-12T22:00:00.000+00:00</published>
  <updated>2026-03-12T22:00:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.nta.co.uk/maintenance/cmmbyfuup0onfu1ra839sk3ye"/>
  <title>Planned maintenance 12/03/26</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 7 hours</p>
    <p><strong>Affected Components:</strong> Outbound Calls, MobeX Mobile, Cloud phone book, Inbound Calls, MobeX Softphone</p>
    <p><small>Mar <var data-var='date'> 12</var>, <var data-var='time'>22:00:00</var> GMT+0</small><br /><strong>Identified</strong> -
  One of our suppliers is performing maintenance on their core network.

The maintenance will be carried out on Thursday 12th of March from 10pm to 5am.

There may be disruption to our service during the maintenance window.

This maintenance is classed as at low risk..</p>
<p><small>Mar <var data-var='date'> 12</var>, <var data-var='time'>22:00:01</var> GMT+0</small><br /><strong>Identified</strong> -
  Maintenance is now in progress.</p>
<p><small>Mar <var data-var='date'> 13</var>, <var data-var='time'>05:00:00</var> GMT+0</small><br /><strong>Completed</strong> -
  Maintenance has completed successfully.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.nta.co.uk,2005:Maintenance/cmlz6gnbj00w8d119f4ktn6wf</id>
  <published>2026-02-27T00:00:00.000+00:00</published>
  <updated>2026-02-27T00:00:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.nta.co.uk/maintenance/cmlz6gnbj00w8d119f4ktn6wf"/>
  <title>Planned Maintenance 27/02/2026</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 6 hours</p>
    <p><strong>Affected Components:</strong> NTA Homepage, Outbound Calls, Dialer, Wallboards, UC Integration, MobeX Mobile, API, Web Interface, Cloud phone book, No Service Impact Expected, Handset Provisioning, Inbound Calls, Busy Lamps, MobeX Softphone</p>
    <p><small>Feb <var data-var='date'> 27</var>, <var data-var='time'>00:00:00</var> GMT+0</small><br /><strong>Identified</strong> -
  One of our suppliers is performing maintenance on their core network.

The maintenance will be carried out on Friday 27th of February from midnight to 6am.

We expect there to be no disruption to our service during this time window.

This maintenance is classed as at low risk..</p>
<p><small>Feb <var data-var='date'> 27</var>, <var data-var='time'>00:00:01</var> GMT+0</small><br /><strong>Identified</strong> -
  Maintenance is now in progress.</p>
<p><small>Feb <var data-var='date'> 27</var>, <var data-var='time'>06:00:00</var> GMT+0</small><br /><strong>Completed</strong> -
  Maintenance has completed successfully.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.nta.co.uk,2005:Incident/cmm3mt59m0qdjhrimvwrehtfp</id>
  <published>2026-02-26T15:42:11.143+00:00</published>
  <updated>2026-02-26T16:45:34.795+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.nta.co.uk/incident/cmm3mt59m0qdjhrimvwrehtfp"/>
  <title>Network Issues</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 16 hours and 51 minutes</p>
    <p><strong>Affected Components:</strong> NTA Homepage, Outbound Calls, Dialer, Wallboards, UC Integration, MobeX Mobile, API, Web Interface, Cloud phone book, No Service Impact Expected, Handset Provisioning, Lease Lines, Wireless Internet, Inbound Calls, Busy Lamps, MobeX Softphone</p>
    <p><small>Feb <var data-var='date'> 26</var>, <var data-var='time'>16:45:34</var> GMT+0</small><br /><strong>Identified</strong> -
  Whilst we do have failover mechanisms in place, these only apply when the primary connection is hard down.  
As it currently flapping, this prevents the system moving into failover as the connection is not hard down.  
Unfortunately, this has put the system in a state where we will have to manually disconnect the link in order to utilise the other links. Our engineers are at site at the datacentre and working on the servers.</p>
<p><small>Feb <var data-var='date'> 26</var>, <var data-var='time'>16:55:53</var> GMT+0</small><br /><strong>Monitoring</strong> -
  We now have a restricted service back-up and running, but services such as BLF will not be fully operational for a while as we concentrate on getting things running back as normal.</p>
<p><small>Feb <var data-var='date'> 26</var>, <var data-var='time'>17:38:38</var> GMT+0</small><br /><strong>Monitoring</strong> -
  Whilst services are fully restored, we are waiting for an update from our suppliers as to the reason for the outage. Once we have that,a reason for outage will be issued..</p>
<p><small>Feb <var data-var='date'> 27</var>, <var data-var='time'>16:09:59</var> GMT+0</small><br /><strong>Postmortem</strong> -
  At 15:42, our upstream connectivity supplier experienced a service outage, causing interface instability (“flapping”) and subsequent service disruption within our network environment.  
  
At 15:50, investigations confirmed that the primary customer impact was related to call completion. The instability affected SIP signalling, causing a core service to become unresponsive and preventing calls from completing successfully. Also, preventing access to disable the affected routes and allow the Disaster Recovery to kick in  
  
At 16:21, NTA engineers managed to disable the affected interfaces to stabilise the platform and initiate established disaster recovery procedures.  
  
At 16:55, service stability was progressively restored following supplier recovery actions, and all services were fully operational and performing within normal parameters.  
  
NTA has already scheduled a programme of infrastructure improvements for April, including the migration from the current connectivity supplier to an alternative provider that will deliver enhanced redundancy while improving service resilience. This programme also includes increased rack capacity, deployment of new server infrastructure, and a major platform upgrade to support modern technologies, including AI capabilities and future business growth.</p>
<p><small>Feb <var data-var='date'> 27</var>, <var data-var='time'>08:33:35</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved. If your handset is still offline, please power cycle it. A reason for the outage will be issued after a thorough investigation into the cause has been conducted. Sorry for any inconvenience this may have caused you.</p>
<p><small>Feb <var data-var='date'> 26</var>, <var data-var='time'>15:42:11</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are currently investigating this incident at our datacentres, which is affecting our network and the abilility to make and receive calls..</p>
<p><small>Feb <var data-var='date'> 26</var>, <var data-var='time'>15:50:17</var> GMT+0</small><br /><strong>Identified</strong> -
  We are continuing to work on a fix for this incident..</p>
<p><small>Feb <var data-var='date'> 26</var>, <var data-var='time'>16:21:34</var> GMT+0</small><br /><strong>Identified</strong> -
  Engineers have been dispatched to one of the datacentres to work on the issue.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.nta.co.uk,2005:Incident/cmju2bn8807g4oby6uxnd5hnv</id>
  <published>2025-12-31T13:39:22.049+00:00</published>
  <updated>2025-12-31T13:39:22.049+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.nta.co.uk/incident/cmju2bn8807g4oby6uxnd5hnv"/>
  <title>Outage</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 2 hours and 7 minutes</p>
    <p><strong>Affected Components:</strong> Outbound Calls, Inbound Calls, Dialer, UC Integration, MobeX Mobile, API, Web Interface, No Service Impact Expected, Handset Provisioning, Busy Lamps, MobeX Softphone</p>
    <p><small>Dec <var data-var='date'> 31</var>, <var data-var='time'>13:39:22</var> GMT+0</small><br /><strong>Investigating</strong> -
  We have become aware of an outage on one of the upstream providers. We are currently investigating this incident..</p>
<p><small>Dec <var data-var='date'> 31</var>, <var data-var='time'>13:51:45</var> GMT+0</small><br /><strong>Identified</strong> -
  We are continuing to work on a fix for this incident..</p>
<p><small>Dec <var data-var='date'> 31</var>, <var data-var='time'>13:55:11</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are currently investigating this incident..</p>
<p><small>Dec <var data-var='date'> 31</var>, <var data-var='time'>14:21:47</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are currently investigating this incident..</p>
<p><small>Dec <var data-var='date'> 31</var>, <var data-var='time'>14:45:22</var> GMT+0</small><br /><strong>Identified</strong> -
  While the service is now working, we are continuing to work on a fix for this incident. .</p>
<p><small>Dec <var data-var='date'> 31</var>, <var data-var='time'>15:21:56</var> GMT+0</small><br /><strong>Monitoring</strong> -
  We implemented a fix and are currently monitoring the result..</p>
<p><small>Dec <var data-var='date'> 31</var>, <var data-var='time'>15:46:07</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved. The system is now up and working. A reason for outage will be issued after a thorough investigation.</p>
<p><small>Jan <var data-var='date'> 2</var>, <var data-var='time'>14:30:35</var> GMT+0</small><br /><strong>Postmortem</strong> -
  **RFO – Wednesday 31st December**  
At **13:39**, our primary service provider experienced extremely high latency on the connections supplying our network. While this caused service degradation, the connections did not go fully offline, which prevented automatic disaster recovery from initiating.  
  
At **13:51**, we manually shut down the affected interfaces, allowing disaster recovery procedures to begin. Due to the nature of the fault, services on the impacted connections then had to be manually terminated in order to fully restore service.  
  
At **14:21**, we identified that the primary impact was on call completion. One service was becoming stuck as SIP signalling was adversely affected by the high latency, preventing calls from completing successfully.  
  
By **14:35**, all services were fully restored and operating normally..</p>
<p><small>Jan <var data-var='date'> 2</var>, <var data-var='time'>08:46:59</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.nta.co.uk,2005:Incident/cmgkmu30g0120qio6y5144f6s</id>
  <published>2025-10-10T09:16:45.317+00:00</published>
  <updated>2025-10-10T09:16:45.317+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.nta.co.uk/incident/cmgkmu30g0120qio6y5144f6s"/>
  <title>Web Server &amp; API Issue</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 32 minutes</p>
    <p><strong>Affected Components:</strong> Wallboards, API, UC Integration, MobeX Softphone</p>
    <p><small>Oct <var data-var='date'> 10</var>, <var data-var='time'>09:16:45</var> GMT+0</small><br /><strong>Monitoring</strong> -
  This morning, we had a brief issue with our Web Server and APIs, which caused a temporary disruption to services such as Wallboards and MobeX Web. We implemented an immediate fix; therefore, these services are now operational. We are currently monitoring the result..</p>
<p><small>Oct <var data-var='date'> 10</var>, <var data-var='time'>09:49:03</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved, and we will continue to monitor our servers..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.nta.co.uk,2005:Maintenance/cmewk22bg0064xe2aptznxcn8</id>
  <published>2025-09-03T20:00:00.000+00:00</published>
  <updated>2025-09-03T23:00:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.nta.co.uk/maintenance/cmewk22bg0064xe2aptznxcn8"/>
  <title>Planned Maintenance 03 September 2025</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 3 hours</p>
    <p><strong>Affected Components:</strong> Outbound Calls, Inbound Calls, Busy Lamps</p>
    <p><small>Sep <var data-var='date'> 3</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'> 3</var>, <var data-var='time'>20:00:00</var> GMT+0</small><br /><strong>Identified</strong> -
  Wednesday, 03 September 2025 between 21:00 - 00:00

Work is required in order to improve our systems.

Wednesday night between 21:00 - 00:00 we will be carrying out essential systems work.

This maintenance is classed as at low risk..</p>
<p><small>Sep <var data-var='date'> 3</var>, <var data-var='time'>20:00:01</var> GMT+0</small><br /><strong>Identified</strong> -
  Maintenance is now in progress.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.nta.co.uk,2005:Incident/cmf0y3lcx00mw6f7s1yob63vc</id>
  <published>2025-09-01T09:56:59.025+00:00</published>
  <updated>2025-09-01T09:56:59.025+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.nta.co.uk/incident/cmf0y3lcx00mw6f7s1yob63vc"/>
  <title>Invoice Generation</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 4 hours and 39 minutes</p>
    
    <p><small>Sep <var data-var='date'> 1</var>, <var data-var='time'>09:56:59</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are currently investigating a fault with invoice generation on [ntalk.co.uk](http://ntalk.co.uk). All invoices are now being regenerated. This could take up to the end of the business day. Any invoices dated 01/09/2025 will be replaced with a new invoice.  
Please email [accounts@nta.co.uk](mailto:accounts@nta.co.uk) for any questions. Updates will be available on this status page when available.  
We apologise for any inconvenience caused..</p>
<p><small>Sep <var data-var='date'> 1</var>, <var data-var='time'>10:48:43</var> GMT+0</small><br /><strong>Identified</strong> -
  The invoice generation has been restarted.</p>
<p><small>Sep <var data-var='date'> 1</var>, <var data-var='time'>14:35:35</var> GMT+0</small><br /><strong>Resolved</strong> -
  All 01/09/2025 invoices have now been generated. Please go to Reports &gt; Invoices on the portal. Thank you for your patience..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.nta.co.uk,2005:Maintenance/cmd63hmxt006q2i4z0h50bibr</id>
  <published>2025-07-19T18:00:00.000+00:00</published>
  <updated>2025-07-19T18:00:01.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.nta.co.uk/maintenance/cmd63hmxt006q2i4z0h50bibr"/>
  <title>Planned Maintenance 19 July 2025</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 4 hours</p>
    <p><strong>Affected Components:</strong> Outbound Calls, Dialer, Inbound Calls, Wallboards, Web Interface, API, Handset Provisioning, MobeX Mobile, UC Integration, MobeX Softphone, Cloud phone book, Busy Lamps</p>
    <p><small>Jul <var data-var='date'> 19</var>, <var data-var='time'>18:00:01</var> GMT+0</small><br /><strong>Identified</strong> -
  Maintenance is now in progress.</p>
<p><small>Jul <var data-var='date'> 19</var>, <var data-var='time'>18:00:00</var> GMT+0</small><br /><strong>Identified</strong> -
  Work is required to replace one of our routers.

This maintenance will take place between 7PM and 11PM Saturday 19th of July 2025.

This maintenance is classed as high risk..</p>
<p><small>Jul <var data-var='date'> 19</var>, <var data-var='time'>22:00:00</var> GMT+0</small><br /><strong>Completed</strong> -
  Maintenance has completed successfully.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.nta.co.uk,2005:Incident/cmcyn8sq0002s12evehh74jm5</id>
  <published>2025-07-11T09:58:09.631+00:00</published>
  <updated>2025-07-11T09:58:09.631+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.nta.co.uk/incident/cmcyn8sq0002s12evehh74jm5"/>
  <title>Telephone Lines</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 2 days, 22 hours and 22 minutes</p>
    <p><strong>Affected Components:</strong> Outbound Calls, Wallboards, No Service Impact Expected, Inbound Calls, NTA Homepage, Dialer, Lease Lines, Wireless Internet, Web Interface, API, Handset Provisioning, MobeX Mobile, UC Integration, MobeX Softphone, Cloud phone book, Busy Lamps</p>
    <p><small>Jul <var data-var='date'> 11</var>, <var data-var='time'>09:58:09</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are currently aware of an incident affecting the telephone lines. We are currently investigating the cause. We will send out further updates when we find out more information..</p>
<p><small>Jul <var data-var='date'> 11</var>, <var data-var='time'>10:33:05</var> GMT+0</small><br /><strong>Identified</strong> -
  BLF&#039;s have temporarily been disabled while service is fully restored.</p>
<p><small>Jul <var data-var='date'> 11</var>, <var data-var='time'>11:08:13</var> GMT+0</small><br /><strong>Identified</strong> -
  The outage has been identified as a network issue, which is being fully investigated. All services have been restored to normal, apart from the BLFs, which will be restored later today. An RFO will be issued following the investigation has been completed.</p>
<p><small>Jul <var data-var='date'> 11</var>, <var data-var='time'>13:54:31</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'> 14</var>, <var data-var='time'>08:19:39</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved and the BLF lights have been re-enabled. An RFO will be issued later.</p>
<p><small>Jul <var data-var='date'> 14</var>, <var data-var='time'>11:42:38</var> GMT+0</small><br /><strong>Resolved</strong> -
   RFO Friday 11th July

10:13 A router card failure was identified at one of our Datacentres in Enfield. Although the router failure was only for 10 minutes and returned to service at 10:23, it caused an issue with the routing of calls whereby either the call was terminated or it made the call became unanswerable.   
10:50 After identifying the cause of the failure, the affected card was removed from service and the BLFs were disabled, to allow the routing to stabilise.  
11.42 The fault was resolved, with services being fully restored, apart from BLFs, due to the load that would suddenly be added to the servers  
  
Weekend of 12.07.25 to 13.07.25 - BLFs were switched back on and all services to the network made fully active  
  
To prevent this incident from reoccurring, the affected router will be replaced on the weekend starting 19.07.25.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.nta.co.uk,2005:Maintenance/cmbyzv2yw000p6ungbgi0drp8</id>
  <published>2025-06-18T20:00:00.000+00:00</published>
  <updated>2025-06-18T23:00:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.nta.co.uk/maintenance/cmbyzv2yw000p6ungbgi0drp8"/>
  <title>Planned Maintenance 18 June 2025</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 3 hours</p>
    <p><strong>Affected Components:</strong> Handset Provisioning, MobeX Mobile, MobeX Softphone, Cloud phone book</p>
    <p><small>Jun <var data-var='date'> 18</var>, <var data-var='time'>23:00:00</var> GMT+0</small><br /><strong>Completed</strong> -
  Maintenance has completed successfully.</p>
<p><small>Jun <var data-var='date'> 18</var>, <var data-var='time'>20:00:00</var> GMT+0</small><br /><strong>Identified</strong> -
  Wednesday, 18 June 2025 between 21:00 - 00:00

Work is required in order to improve our systems.

Wednesday night between 21:00 - 00:00 we will be carrying out essential work on Cloud phone book and provisioning systems.

This maintenance is classed as at low risk..</p>
<p><small>Jun <var data-var='date'> 18</var>, <var data-var='time'>20:00:01</var> GMT+0</small><br /><strong>Identified</strong> -
  Maintenance is now in progress.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.nta.co.uk,2005:Maintenance/cmb950i6w000vcatxzkc5guyc</id>
  <published>2025-06-02T21:00:00.000+00:00</published>
  <updated>2025-06-02T21:00:01.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.nta.co.uk/maintenance/cmb950i6w000vcatxzkc5guyc"/>
  <title>Planned Maintenance 2 June 2025 - Migration to Ntalk</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 2 hours</p>
    <p><strong>Affected Components:</strong> Web Interface, API, Handset Provisioning, MobeX Mobile, UC Integration, MobeX Softphone</p>
    <p><small>Jun <var data-var='date'> 2</var>, <var data-var='time'>21:00:01</var> GMT+0</small><br /><strong>Identified</strong> -
  Maintenance is now in progress.</p>
<p><small>Jun <var data-var='date'> 2</var>, <var data-var='time'>21:00:00</var> GMT+0</small><br /><strong>Identified</strong> -
  Monday, 2 June 2025 between 22:00 - 00:00

Work is required in order to improve our systems.

Monday night between 22:00 - 00:00 we will be deploying the new Ntalk portal that will replace the current Hosted portal.

This maintenance is classed as at low risk..</p>
<p><small>Jun <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>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.nta.co.uk,2005:Maintenance/cm9sh94nc00as10b5rma7pml7</id>
  <published>2025-06-02T20:00:00.000+00:00</published>
  <updated>2025-06-02T23:00:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.nta.co.uk/maintenance/cm9sh94nc00as10b5rma7pml7"/>
  <title>Planned Maintenance 02 June 2025 - New web portal interface</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 3 hours</p>
    <p><strong>Affected Components:</strong> Web Interface, API, Handset Provisioning, MobeX Mobile, MobeX Softphone</p>
    <p><small>Jun <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>Jun <var data-var='date'> 2</var>, <var data-var='time'>20:00:01</var> GMT+0</small><br /><strong>Identified</strong> -
  Maintenance is now in progress.</p>
<p><small>Jun <var data-var='date'> 2</var>, <var data-var='time'>20:00:00</var> GMT+0</small><br /><strong>Identified</strong> -
  Monday, 02 June 2025 between 21:00 - 00:00

Work is required in order to improve our systems.

Monday night between 21:00 - 00:00 we will be updating our portal to use the new web interface (the one being tested on https://ntalk.co.uk).

This maintenance is classed as at low risk..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.nta.co.uk,2005:Incident/cmbgemul70008p8oll1vh0cwi</id>
  <published>2025-06-02T10:00:00.000+00:00</published>
  <updated>2025-06-04T10:28:34.136+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.nta.co.uk/incident/cmbgemul70008p8oll1vh0cwi"/>
  <title>C30 Rebooting and Cloud Phonebook</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 2 days and 29 minutes</p>
    <p><strong>Affected Components:</strong> Handset Provisioning</p>
    <p><small>Jun <var data-var='date'> 4</var>, <var data-var='time'>10:28:34</var> GMT+0</small><br /><strong>Resolved</strong> -
  Whilst we are aware there are a few extensions with problems still, we will resolve those shortly. Please see below the RFO

In the new implementation of our Cloud Phonebook we decided to use some proxies to improve its availability and also add a few new features. We opted for using HAProxy, a well-known open-source project, that has been in use for many years (it is responsible for handling provisioning, wallboards, MobeX plus many internal projects). We also developed an LDAP Proxy to allow us to add a cache to improve the responses and sorting (something that models like C30 and below cannot do).

The solution was tested internally and worked fine. Unfortunately, while moving it to production, we started to receive reports that the Cloud Phonebook was failing and some devices (A10, B20 plus C30) were rebooting.

After the initial investigation, we found that some of the behaviours were causing the connections to be denied, so we improved it to handle an increase in traffic that we couldn&#039;t reproduce during the internal tests. However, the rebooting of the devices was unexpected and the only real hypothesis was that something in the middle between the LDAP servers and the devices was creating packets that the devices couldn&#039;t handle.

Initially, we decided to stop using the LDAP Proxy as it could be sending the wrong packets which started to reprovision the devices. This is a process that could take several hours because it would not be good to have all the devices coming to the system at the same time. 

After the C30 devices were reprovisioned, we kept monitoring the systems and took notes of reports. There was also a possibility that the devices that were still rebooting were the ones we could not reach for reprovisioning because they were in use at the time that we sent the requests.

After more internal checks we noticed that this was not the case, so the only other piece of software that could be causing the reboots was the HAProxy itself. The fact that it was affecting only the old Hosted models probably meant that they couldn&#039;t handle some packets that were being sent to them.

We started to reprovision all devices to connect directly to the LDAP servers, avoiding any proxies in the middle, after this was done no more reboots were detected. This means that we can&#039;t use the HAProxy with the LDAP servers.

However, it doesn&#039;t mean that we will not be implementing our LDAP Proxy again in the near future, since the LDAP Proxy was behind the HAProxy, it is possible that the LDAP Proxy was not failing, but just facing the same issues with the HAProxy too.

This implementation will be done in a slow-paced rollout to avoid causing more issues with the cloud phonebook access in the future. The new LDAP Proxy is a really important part of our new cloud phonebook strategy because it will make the Dir requests much quicker and it&#039;ll add sorting support for models A, B plus C30.

We really do apologize for this unexpected issue and will keep you updated on our plans in the future.</p>
<p><small>Jun <var data-var='date'> 2</var>, <var data-var='time'>10:00:00</var> GMT+0</small><br /><strong>Identified</strong> -
  We are aware of the C30 handsets rebooting/cutting off. This has been identified as an issue with LDAP. Please reset thee handset by pressing the OK button for 10 seconds to clear the configuration out of the handset to clear this. This is also causing Cloud Phonebook issues on other handsets, we are continuing to work on a fix for this incident..</p>
<p><small>Jun <var data-var='date'> 3</var>, <var data-var='time'>11:16:59</var> GMT+0</small><br /><strong>Identified</strong> -
  We will be reprovisioning the C30 devices, after that it will be A, B, E, F, and then C33 and Ds which will take one hour per group

After this,the number of entries in the Cloud Phonebook will be worked on followed by the ringtones.</p>
<p><small>Jun <var data-var='date'> 3</var>, <var data-var='time'>13:46:36</var> GMT+0</small><br /><strong>Monitoring</strong> -
  We implemented a fix and are currently monitoring the result. We are sending the connections directly to the LDAP server therefore bypassing the haproxy now and removing anything obstruction in the chain.</p>
<p><small>Jun <var data-var='date'> 3</var>, <var data-var='time'>15:14:14</var> GMT+0</small><br /><strong>Monitoring</strong> -
  Yealink handsets will be reprovisioned after 18:00 tonight which should resolve the ringtone issues.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.nta.co.uk,2005:Incident/cm8mvipsf000tsvdytfy07h5s</id>
  <published>2025-03-24T09:37:45.109+00:00</published>
  <updated>2025-03-24T10:47:45.996+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.nta.co.uk/incident/cm8mvipsf000tsvdytfy07h5s"/>
  <title>Internet &amp; Telephone Connection Dropping</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 5 hours and 1 minute</p>
    <p><strong>Affected Components:</strong> Web Interface, Outbound Calls, Inbound Calls</p>
    <p><small>Mar <var data-var='date'> 24</var>, <var data-var='time'>10:47:45</var> GMT+0</small><br /><strong>Identified</strong> -
  Please see the inserted link for further information on this matter &lt;https://www.ispreview.co.uk/index.php/2025/03/broadband-isps-report-uk-connectivity-problems-with-vulnerable-draytek-routers.html&gt;.</p>
<p><small>Mar <var data-var='date'> 24</var>, <var data-var='time'>14:38:51</var> GMT+0</small><br /><strong>Resolved</strong> -
  As the issue is down to the use of the Draytek routers and not a direct NTA issue this is deemed to be a non-NTA incident and only an advisory notification and therefore the issue will be closed.</p>
<p><small>Mar <var data-var='date'> 24</var>, <var data-var='time'>13:07:02</var> GMT+0</small><br /><strong>Monitoring</strong> -
  We have been advised of a fix for the current issue with the Draytek routers. Please disable SSL VPN and Remote management on the router.</p>
<p><small>Mar <var data-var='date'> 24</var>, <var data-var='time'>09:37:45</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are currently investigating this incident. However, we have been advised that this is due to firmware changes on Draytek routers. Please contact your IT team for assistance.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.nta.co.uk,2005:Maintenance/cm6zaccwy0027sfngw8425izo</id>
  <published>2025-03-15T14:00:00.000+00:00</published>
  <updated>2025-03-15T14:00:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.nta.co.uk/maintenance/cm6zaccwy0027sfngw8425izo"/>
  <title>Planned Maintenance 15th of March 2025</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 3 hours</p>
    <p><strong>Affected Components:</strong> Web Interface, API, MobeX Softphone, Outbound Calls, Lease Lines, Dialer, Wallboards, Handset Provisioning, Busy Lamps, Inbound Calls, NTA Homepage, MobeX Mobile</p>
    <p><small>Mar <var data-var='date'> 15</var>, <var data-var='time'>14:00:00</var> GMT+0</small><br /><strong>Identified</strong> -
  Maintenance is required to improve our network infrastructure.

The maintenance is planned for Saturday 15th of March.

This maintenance is classed as high risk..</p>
<p><small>Mar <var data-var='date'> 15</var>, <var data-var='time'>14:00:01</var> GMT+0</small><br /><strong>Identified</strong> -
  Maintenance is now in progress.</p>
<p><small>Mar <var data-var='date'> 15</var>, <var data-var='time'>17:00:00</var> GMT+0</small><br /><strong>Completed</strong> -
  Maintenance has completed successfully.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.nta.co.uk,2005:Maintenance/cm5mitesk0001b92mazrbdssa</id>
  <published>2025-02-16T20:00:00.000+00:00</published>
  <updated>2025-02-16T22:00:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.nta.co.uk/maintenance/cm5mitesk0001b92mazrbdssa"/>
  <title>Planned Network Maintenance 16th February 2025</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 2 hours</p>
    <p><strong>Affected Components:</strong> Web Interface, API, MobeX Softphone, Outbound Calls, Lease Lines, UC Integration, Dialer, Wallboards, Handset Provisioning, Busy Lamps, Inbound Calls, NTA Homepage, MobeX Mobile</p>
    <p><small>Feb <var data-var='date'> 16</var>, <var data-var='time'>22:00:00</var> GMT+0</small><br /><strong>Completed</strong> -
  Maintenance has completed successfully.</p>
<p><small>Feb <var data-var='date'> 16</var>, <var data-var='time'>20:00:00</var> GMT+0</small><br /><strong>Identified</strong> -
  Work is required in order to update our systems.

This work will take place Sunday 16th February 2025 between 20:00 - 22:00.

This maintenance is classed as low risk..</p>
<p><small>Feb <var data-var='date'> 16</var>, <var data-var='time'>20:00:01</var> GMT+0</small><br /><strong>Identified</strong> -
  Maintenance is now in progress.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.nta.co.uk,2005:Maintenance/cm6s02eh1000o111h5phesugv</id>
  <published>2025-02-11T21:00:00.000+00:00</published>
  <updated>2025-02-11T21:00:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.nta.co.uk/maintenance/cm6s02eh1000o111h5phesugv"/>
  <title>Planned Maintenance 11 February 2025</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 1 hour</p>
    <p><strong>Affected Components:</strong> MobeX Softphone, MobeX Mobile</p>
    <p><small>Feb <var data-var='date'> 11</var>, <var data-var='time'>21:00:00</var> GMT+0</small><br /><strong>Identified</strong> -
  Tuesday, 11 February 2025 between 21:00 - 22:00.

Work is required in order to improve our MobeX systems.

Tuesday night between 21:00 - 22:00 we will be carrying out essential systems update.

This maintenance is classed as at low risk..</p>
<p><small>Feb <var data-var='date'> 11</var>, <var data-var='time'>21:00:01</var> GMT+0</small><br /><strong>Identified</strong> -
  Maintenance is now in progress.</p>
<p><small>Feb <var data-var='date'> 11</var>, <var data-var='time'>22:00:00</var> GMT+0</small><br /><strong>Completed</strong> -
  Maintenance has completed successfully.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.nta.co.uk,2005:Maintenance/cm67t3rkt000p5pbju05m1v7f</id>
  <published>2025-02-06T21:00:00.000+00:00</published>
  <updated>2025-02-06T22:00:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.nta.co.uk/maintenance/cm67t3rkt000p5pbju05m1v7f"/>
  <title>Planned Maintenance 6th February 2025</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 1 hour</p>
    <p><strong>Affected Components:</strong> Web Interface, API, MobeX Softphone, Outbound Calls, Dialer, Wallboards, Handset Provisioning, Busy Lamps, Inbound Calls, NTA Homepage, MobeX Mobile</p>
    <p><small>Feb <var data-var='date'> 6</var>, <var data-var='time'>22:00:00</var> GMT+0</small><br /><strong>Completed</strong> -
  Maintenance has completed successfully.</p>
<p><small>Feb <var data-var='date'> 6</var>, <var data-var='time'>21:00:01</var> GMT+0</small><br /><strong>Identified</strong> -
  Maintenance is now in progress.</p>
<p><small>Feb <var data-var='date'> 6</var>, <var data-var='time'>21:00:00</var> GMT+0</small><br /><strong>Identified</strong> -
  Work is required in order to update our systems.

This work will take place Thursday 6th February 2025 between 21:00 - 22:00.

This maintenance is classed as low risk..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.nta.co.uk,2005:Maintenance/cm5miprhz0001lo3e0xl77gqo</id>
  <published>2025-01-19T20:00:00.000+00:00</published>
  <updated>2025-01-19T20:00:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.nta.co.uk/maintenance/cm5miprhz0001lo3e0xl77gqo"/>
  <title>Planned Network Maintenance 19th January 2025</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 1 hour</p>
    <p><strong>Affected Components:</strong> No Service Impact Expected</p>
    <p><small>Jan <var data-var='date'> 19</var>, <var data-var='time'>20:00:00</var> GMT+0</small><br /><strong>Identified</strong> -
  Work is required in order to update our systems.

This work will take place Sunday 19th January 2025 between 20:00 - 21:00.

This maintenance is classed as low risk..</p>
<p><small>Jan <var data-var='date'> 19</var>, <var data-var='time'>21:00:00</var> GMT+0</small><br /><strong>Completed</strong> -
  Maintenance has completed successfully.</p>
<p><small>Jan <var data-var='date'> 19</var>, <var data-var='time'>20:00:01</var> GMT+0</small><br /><strong>Identified</strong> -
  Maintenance is now in progress.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.nta.co.uk,2005:Maintenance/cm28y9nmp002mfafqc9zizfvg</id>
  <published>2024-11-16T22:00:00.000+00:00</published>
  <updated>2024-11-16T22:00:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.nta.co.uk/maintenance/cm28y9nmp002mfafqc9zizfvg"/>
  <title>Planned Network Maintenance 16 November 2024</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 3 hours</p>
    <p><strong>Affected Components:</strong> Web Interface, API, MobeX Softphone, Outbound Calls, Lease Lines, Dialer, Wallboards, Handset Provisioning, Busy Lamps, Inbound Calls, NTA Homepage, MobeX Mobile</p>
    <p><small>Nov <var data-var='date'> 16</var>, <var data-var='time'>22:00:00</var> GMT+0</small><br /><strong>Identified</strong> -
  Work is required in order to update our systems.

This work will take place Saturday 30th of November between 22:00 - 01:00.

This maintenance is classed as medium risk..</p>
<p><small>Nov <var data-var='date'> 17</var>, <var data-var='time'>01:00:00</var> GMT+0</small><br /><strong>Completed</strong> -
  Maintenance has completed successfully.</p>
<p><small>Nov <var data-var='date'> 16</var>, <var data-var='time'>22:00:01</var> GMT+0</small><br /><strong>Identified</strong> -
  Maintenance is now in progress.</p>
<p><small>Nov <var data-var='date'> 17</var>, <var data-var='time'>01:00:00</var> GMT+0</small><br /><strong>Completed</strong> -
  Maintenance has completed successfully.</p>
<p><small>Oct <var data-var='date'> 18</var>, <var data-var='time'>09:20:12</var> GMT+0</small><br /><strong>Identified</strong> -
  The planned maintenance for the 30th of November has been moved to the 16th of November (10PM to 1AM.)

This maintenance is classed as medium risk..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.nta.co.uk,2005:Incident/cm2st8oae0002ldoigq226ovf</id>
  <published>2024-10-28T09:22:20.250+00:00</published>
  <updated>2024-10-28T09:22:20.250+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.nta.co.uk/incident/cm2st8oae0002ldoigq226ovf"/>
  <title>Incorrect Time on Handsets</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 2 hours and 20 minutes</p>
    <p><strong>Affected Components:</strong> No Service Impact Expected</p>
    <p><small>Oct <var data-var='date'> 28</var>, <var data-var='time'>09:22:20</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are aware that some of the handsets are showing the incorrect time. We are currently investigating to resolve this issue. Sorry for any inconvenience this may cause..</p>
<p><small>Oct <var data-var='date'> 28</var>, <var data-var='time'>09:53:21</var> GMT+0</small><br /><strong>Identified</strong> -
  The issue has been identified and a resolution is being put in place..</p>
<p><small>Oct <var data-var='date'> 28</var>, <var data-var='time'>10:31:22</var> GMT+0</small><br /><strong>Identified</strong> -
  The issue will be rectified within the next 30 minutes, you may see your handset being reprovisioned during this time.</p>
<p><small>Oct <var data-var='date'> 28</var>, <var data-var='time'>11:42:38</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved. If your handset is still showing the incorrect time please reboot the device.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.nta.co.uk,2005:Incident/cm1rtfn7a000do8yxxkkrd05s</id>
  <published>2024-10-02T12:00:17.764+00:00</published>
  <updated>2024-10-02T12:00:17.764+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.nta.co.uk/incident/cm1rtfn7a000do8yxxkkrd05s"/>
  <title>Broadband Outage</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 2 hours and 19 minutes</p>
    <p><strong>Affected Components:</strong> Lease Lines, Wireless Internet</p>
    <p><small>Oct <var data-var='date'> 2</var>, <var data-var='time'>12:00:17</var> GMT+0</small><br /><strong>Identified</strong> -
  We are aware that some broadband services are not in service. We are continuing to work with our suppliers on a fix for this incident..</p>
<p><small>Oct <var data-var='date'> 2</var>, <var data-var='time'>12:27:06</var> GMT+0</small><br /><strong>Monitoring</strong> -
  A fix has been implemented by the supplier and whilst this seems to have resolved the situation we will continue to monitor it.</p>
<p><small>Oct <var data-var='date'> 2</var>, <var data-var='time'>14:18:55</var> GMT+0</small><br /><strong>Resolved</strong> -
  Although the issue now appears to be resolved and was due to a DNS issue with the supplier we will continue to monitor the situation. We apologise for any inconvenience caused.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.nta.co.uk,2005:Maintenance/clywwmyxp44834i9n7iswgnvej</id>
  <published>2024-09-14T20:00:00.000+00:00</published>
  <updated>2024-09-14T20:00:01.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.nta.co.uk/maintenance/clywwmyxp44834i9n7iswgnvej"/>
  <title>Planned Network Maintenance 14 September 2024</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 3 hours</p>
    <p><strong>Affected Components:</strong> Web Interface, API, MobeX Softphone, Outbound Calls, UC Integration, Dialer, Wallboards, Handset Provisioning, Busy Lamps, Inbound Calls, NTA Homepage, MobeX Mobile</p>
    <p><small>Sep <var data-var='date'> 14</var>, <var data-var='time'>20:00:01</var> GMT+0</small><br /><strong>Identified</strong> -
  Maintenance is now in progress.</p>
<p><small>Sep <var data-var='date'> 14</var>, <var data-var='time'>20:00:00</var> GMT+0</small><br /><strong>Identified</strong> -
  Work is required in order to improve our systems.

Saturday night between 21:00 - 23:59 we will be carrying out essential systems update.

This maintenance is classed as at medium risk..</p>
<p><small>Sep <var data-var='date'> 14</var>, <var data-var='time'>23:00:00</var> GMT+0</small><br /><strong>Completed</strong> -
  Maintenance has completed successfully.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.nta.co.uk,2005:Maintenance/cm0kx5rp0003ess7f2uo6sw63</id>
  <published>2024-09-04T20:00:00.000+00:00</published>
  <updated>2024-09-04T20:00:01.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.nta.co.uk/maintenance/cm0kx5rp0003ess7f2uo6sw63"/>
  <title>Planned Maintenance 04 September 2024</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 3 hours</p>
    <p><strong>Affected Components:</strong> Web Interface, API</p>
    <p><small>Sep <var data-var='date'> 4</var>, <var data-var='time'>20:00:01</var> GMT+0</small><br /><strong>Identified</strong> -
  Maintenance is now in progress.</p>
<p><small>Sep <var data-var='date'> 4</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'> 4</var>, <var data-var='time'>20:00:00</var> GMT+0</small><br /><strong>Identified</strong> -
  Wednesday, 04 September 2024 between 21:00 - 00:00

Work is required in order to improve our portal.

Wednesday night between 21:00 - 00:00 we will be carrying out essential portal update.

This maintenance is classed as at low risk..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.nta.co.uk,2005:Incident/cm0ksfd100007j4bhc6usqgh5</id>
  <published>2024-09-02T09:17:59.381+00:00</published>
  <updated>2024-09-02T09:17:59.381+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.nta.co.uk/incident/cm0ksfd100007j4bhc6usqgh5"/>
  <title>UC+ Licensing issue</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 4 days, 8 hours and 27 minutes</p>
    <p><strong>Affected Components:</strong> UC Integration</p>
    <p><small>Sep <var data-var='date'> 2</var>, <var data-var='time'>09:17:59</var> GMT+0</small><br /><strong>Identified</strong> -
  We are currently investigating an issue with the UC+ server where clients are showing that the server is unlicensed..</p>
<p><small>Sep <var data-var='date'> 2</var>, <var data-var='time'>11:02:26</var> GMT+0</small><br /><strong>Resolved</strong> -
  We implemented a fix and are currently monitoring the result. Some UC+ clients are not automatically reconnecting, please close and reopen the application to reconnect to the server..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.nta.co.uk,2005:Incident/clzr1zn75732027ifohtk1w3zrh</id>
  <published>2024-08-12T13:52:36.414+00:00</published>
  <updated>2024-08-12T14:06:36.465+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.nta.co.uk/incident/clzr1zn75732027ifohtk1w3zrh"/>
  <title>Broadband Outages</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 27 minutes</p>
    <p><strong>Affected Components:</strong> Lease Lines, Wireless Internet</p>
    <p><small>Aug <var data-var='date'> 12</var>, <var data-var='time'>14:06:36</var> GMT+0</small><br /><strong>Identified</strong> -
  The issue appears to an issue with Google DNS resolution on the router.</p>
<p><small>Aug <var data-var='date'> 12</var>, <var data-var='time'>13:52:36</var> GMT+0</small><br /><strong>Investigating</strong> -
  We have identified that numerous broadbands are currently offline nationally. We are currently investigating this incident..</p>
<p><small>Aug <var data-var='date'> 12</var>, <var data-var='time'>14:32:47</var> GMT+0</small><br /><strong>Monitoring</strong> -
  Although the incident now appears to be resolved we will continue to monitor the situation.</p>
<p><small>Aug <var data-var='date'> 12</var>, <var data-var='time'>15:19:30</var> GMT+0</small><br /><strong>Resolved</strong> -
  The incident now appears to be resolved. We will continue to monitor still though.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.nta.co.uk,2005:Maintenance/clz6w41an2035763hodl00r4zic</id>
  <published>2024-07-31T20:00:00.000+00:00</published>
  <updated>2024-07-31T20:00:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.nta.co.uk/maintenance/clz6w41an2035763hodl00r4zic"/>
  <title>Planned Maintenance 31 July 2024</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 2 hours</p>
    <p><strong>Affected Components:</strong> Outbound Calls, Inbound Calls</p>
    <p><small>Jul <var data-var='date'> 31</var>, <var data-var='time'>20:00:00</var> GMT+0</small><br /><strong>Identified</strong> -
  Wednesday, 31 July 2024 between 21:00 - 23:00

Work is required in order to improve our systems.

Wednesday night between 21:00 - 23:00 we will be carrying out essential system upgrade.

This maintenance is classed as at low risk..</p>
<p><small>Jul <var data-var='date'> 31</var>, <var data-var='time'>20:00:01</var> GMT+0</small><br /><strong>Identified</strong> -
  Maintenance is now in progress.</p>
<p><small>Jul <var data-var='date'> 31</var>, <var data-var='time'>22:00:00</var> GMT+0</small><br /><strong>Completed</strong> -
  Maintenance has completed successfully.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.nta.co.uk,2005:Incident/clyztxw4d870692hjn3urc1d0gh</id>
  <published>2024-07-24T12:37:30.952+00:00</published>
  <updated>2024-07-24T16:10:11.463+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.nta.co.uk/incident/clyztxw4d870692hjn3urc1d0gh"/>
  <title>Broadband Issues</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 17 hours and 46 minutes</p>
    <p><strong>Affected Components:</strong> Lease Lines</p>
    <p><small>Jul <var data-var='date'> 24</var>, <var data-var='time'>16:10:11</var> GMT+0</small><br /><strong>Monitoring</strong> -
  We are aware that some broadbands are still offline. If possible can you please power down the router for 20 minutes to try and kill any stale sessions it may have which was caused by the outage..</p>
<p><small>Jul <var data-var='date'> 24</var>, <var data-var='time'>12:37:30</var> GMT+0</small><br /><strong>Investigating</strong> -
  One of our upstream broadband suppliers is having issues affecting some of customers. We are currently investigating this incident..</p>
<p><small>Jul <var data-var='date'> 24</var>, <var data-var='time'>13:37:12</var> GMT+0</small><br /><strong>Identified</strong> -
  The supplier is still working on a resolution to the issue and hopes to have it resolved as soon as possible.</p>
<p><small>Jul <var data-var='date'> 25</var>, <var data-var='time'>06:23:51</var> GMT+0</small><br /><strong>Resolved</strong> -
  Whilst the incident is now resolved we are waiting for a Reason For Outage from the supplier. As soon as we have this we will update this page.</p>
<p><small>Jul <var data-var='date'> 25</var>, <var data-var='time'>08:58:14</var> GMT+0</small><br /><strong>Resolved</strong> -
  Reason For Outage on 24.07.24

The supplier has informed us that they had a power issue on a bank of servers at one of their data centres. This caused stale sessions on the broadband connections. If you still do not have any service, please power down the router for 30 minutes..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.nta.co.uk,2005:Maintenance/clxekdzhg2573b0oeo6nvjwef</id>
  <published>2024-07-19T20:00:00.000+00:00</published>
  <updated>2024-07-19T20:00:01.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.nta.co.uk/maintenance/clxekdzhg2573b0oeo6nvjwef"/>
  <title>Planned Network Maintenance 19 July 2024</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 3 hours</p>
    <p><strong>Affected Components:</strong> Web Interface, API, MobeX Softphone, Outbound Calls, Lease Lines, UC Integration, Dialer, Wallboards, Handset Provisioning, Wireless Internet, Busy Lamps, Inbound Calls, NTA Homepage, MobeX Mobile</p>
    <p><small>Jul <var data-var='date'> 19</var>, <var data-var='time'>20:00:01</var> GMT+0</small><br /><strong>Identified</strong> -
  Maintenance is now in progress.</p>
<p><small>Jul <var data-var='date'> 19</var>, <var data-var='time'>20:00:00</var> GMT+0</small><br /><strong>Identified</strong> -
  Friday, 19 July 2024 between 21:00 - 23:59

Work is required in order to improve our systems.

Friday night between 21:00 - 23:59 we will be carrying out essential systems update.

This maintenance is classed as at medium risk..</p>
<p><small>Jul <var data-var='date'> 19</var>, <var data-var='time'>23:00:00</var> GMT+0</small><br /><strong>Completed</strong> -
  Maintenance has completed successfully.</p>
<p><small>Jul <var data-var='date'> 19</var>, <var data-var='time'>23:00:00</var> GMT+0</small><br /><strong>Completed</strong> -
  Maintenance has completed successfully.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.nta.co.uk,2005:Maintenance/clyfzc6kg94431gvohqlth047t</id>
  <published>2024-07-12T20:00:00.000+00:00</published>
  <updated>2024-07-12T20:00:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.nta.co.uk/maintenance/clyfzc6kg94431gvohqlth047t"/>
  <title>Planned Maintenance 12 July 2024</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 3 hours</p>
    <p><strong>Affected Components:</strong> MobeX Softphone, Outbound Calls, Busy Lamps, Inbound Calls, MobeX Mobile</p>
    <p><small>Jul <var data-var='date'> 12</var>, <var data-var='time'>20:00:00</var> GMT+0</small><br /><strong>Identified</strong> -
  Friday, 12 July 2024 between 21:00 - 00:00

Work is required in order to improve our systems.

Friday night between 21:00 - 00:00 we will be carrying out essential systems update.

This maintenance is classed as at low risk..</p>
<p><small>Jul <var data-var='date'> 12</var>, <var data-var='time'>20:00:01</var> GMT+0</small><br /><strong>Identified</strong> -
  Maintenance is now in progress.</p>
<p><small>Jul <var data-var='date'> 12</var>, <var data-var='time'>23:00:00</var> GMT+0</small><br /><strong>Completed</strong> -
  Maintenance has completed successfully.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.nta.co.uk,2005:Maintenance/clxek9mcc1981b7oe74rxyl9c</id>
  <published>2024-07-05T18:00:00.000+00:00</published>
  <updated>2024-07-05T18:00:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.nta.co.uk/maintenance/clxek9mcc1981b7oe74rxyl9c"/>
  <title>Planned Network Maintenance 5 July 2024</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 3 hours</p>
    <p><strong>Affected Components:</strong> Wireless Internet</p>
    <p><small>Jul <var data-var='date'> 5</var>, <var data-var='time'>18:00:00</var> GMT+0</small><br /><strong>Identified</strong> -
  Friday, 5 July 2024 between 19:00 - 22:00

Work is required in order to improve our systems.

Friday night between 19:00 - 22:00 we will be carrying out essential systems update.

This maintenance is classed as at low risk..</p>
<p><small>Jul <var data-var='date'> 5</var>, <var data-var='time'>21:00:00</var> GMT+0</small><br /><strong>Completed</strong> -
  Maintenance has completed successfully.</p>
<p><small>Jul <var data-var='date'> 5</var>, <var data-var='time'>18:00:01</var> GMT+0</small><br /><strong>Identified</strong> -
  Maintenance is now in progress.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.nta.co.uk,2005:Maintenance/clxmzferg123085b8olr0n4jsx4</id>
  <published>2024-06-24T17:00:00.000+00:00</published>
  <updated>2024-06-24T23:00:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.nta.co.uk/maintenance/clxmzferg123085b8olr0n4jsx4"/>
  <title>Planned Network Maintenance 24 June 2024</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 6 hours</p>
    <p><strong>Affected Components:</strong> Lease Lines</p>
    <p><small>Jun <var data-var='date'> 24</var>, <var data-var='time'>23:00:00</var> GMT+0</small><br /><strong>Completed</strong> -
  Maintenance has completed successfully.</p>
<p><small>Jun <var data-var='date'> 24</var>, <var data-var='time'>17:00:01</var> GMT+0</small><br /><strong>Identified</strong> -
  Maintenance is now in progress.</p>
<p><small>Jun <var data-var='date'> 24</var>, <var data-var='time'>17:00:00</var> GMT+0</small><br /><strong>Identified</strong> -
  Work is required on our network to improve our service.

Monday night between 18:00 - 00:00 we will be carrying out essential network maintenance.

This maintenance will only effect layer 2 lease lines..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.nta.co.uk,2005:Maintenance/clxejo5zd233291bcoeac70qjz8</id>
  <published>2024-06-18T20:00:00.000+00:00</published>
  <updated>2024-06-18T20:00:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.nta.co.uk/maintenance/clxejo5zd233291bcoeac70qjz8"/>
  <title>Planned Maintenance 18 June 2024</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 3 hours</p>
    <p><strong>Affected Components:</strong> MobeX Softphone, Outbound Calls, Busy Lamps, Inbound Calls, MobeX Mobile</p>
    <p><small>Jun <var data-var='date'> 18</var>, <var data-var='time'>20:00:00</var> GMT+0</small><br /><strong>Identified</strong> -
  Tuesday, 18 June 2024 between 21:00 - 00:00

Work is required in order to improve our systems.

Tuesday night between 21:00 - 00:00 we will be carrying out essential systems update.

This maintenance is classed as at low risk..</p>
<p><small>Jun <var data-var='date'> 18</var>, <var data-var='time'>23:00:00</var> GMT+0</small><br /><strong>Completed</strong> -
  Maintenance has completed successfully.</p>
<p><small>Jun <var data-var='date'> 18</var>, <var data-var='time'>20:00:01</var> GMT+0</small><br /><strong>Identified</strong> -
  Maintenance is now in progress.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.nta.co.uk,2005:Incident/clxajvsoz139444beofvq2xcb40</id>
  <published>2024-06-11T15:22:00.784+00:00</published>
  <updated>2024-06-11T15:22:00.784+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.nta.co.uk/incident/clxajvsoz139444beofvq2xcb40"/>
  <title>Wallboards</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 42 minutes</p>
    <p><strong>Affected Components:</strong> Wallboards</p>
    <p><small>Jun <var data-var='date'> 11</var>, <var data-var='time'>15:22:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are aware that there is currently an issue with the wallboards. We are currently investigating this incident..</p>
<p><small>Jun <var data-var='date'> 11</var>, <var data-var='time'>15:34:58</var> GMT+0</small><br /><strong>Monitoring</strong> -
  This incident has been resolved. However, we will still keep monitoring the situation.</p>
<p><small>Jun <var data-var='date'> 11</var>, <var data-var='time'>16:03:31</var> GMT+0</small><br /><strong>Resolved</strong> -
  Although this incident has been resolved we will keep monitoring the situation.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.nta.co.uk,2005:Incident/clvgiwq4t66343b4ol04dubdze</id>
  <published>2024-04-26T10:21:56.479+00:00</published>
  <updated>2024-04-26T10:21:56.479+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.nta.co.uk/incident/clvgiwq4t66343b4ol04dubdze"/>
  <title>Cloud phonebook</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 11 hours and 7 minutes</p>
    <p><strong>Affected Components:</strong> Handset Provisioning, No Service Impact Expected</p>
    <p><small>Apr <var data-var='date'> 26</var>, <var data-var='time'>10:21:56</var> GMT+0</small><br /><strong>Identified</strong> -
  We are aware of a cloud phonebook issue that is affecting some of our customers and we are working to resolve it..</p>
<p><small>Apr <var data-var='date'> 26</var>, <var data-var='time'>21:28:40</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident regarding the Cloud phonebook and BLF parking has now been resolved. We apologise for any inconvenience caused.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.nta.co.uk,2005:Incident/clv6fpeql145155bfoe6l32qc3z</id>
  <published>2024-04-19T08:54:34.496+00:00</published>
  <updated>2024-04-19T08:54:34.496+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.nta.co.uk/incident/clv6fpeql145155bfoe6l32qc3z"/>
  <title>BLF  Lights</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 7 days, 1 hour and 23 minutes</p>
    <p><strong>Affected Components:</strong> Busy Lamps</p>
    <p><small>Apr <var data-var='date'> 19</var>, <var data-var='time'>08:54:34</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are aware of the issue with BLF lights and are currently working on a resolution to this.</p>
<p><small>Apr <var data-var='date'> 19</var>, <var data-var='time'>12:27:28</var> GMT+0</small><br /><strong>Identified</strong> -
  We are still working on a resolution to the BLF issue and will update you again in due course.</p>
<p><small>Apr <var data-var='date'> 20</var>, <var data-var='time'>07:31:49</var> GMT+0</small><br /><strong>Monitoring</strong> -
  We are still working towards a full resolution to the BLF issue and will update you accordingly.</p>
<p><small>Apr <var data-var='date'> 22</var>, <var data-var='time'>11:17:16</var> GMT+0</small><br /><strong>Monitoring</strong> -
  Over the weekend we implemented a solution and are currently monitoring the outcome. If you are still experiencing an issue please advise us..</p>
<p><small>Apr <var data-var='date'> 26</var>, <var data-var='time'>10:17:51</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.nta.co.uk,2005:Incident/clv1z418t68117b4o9p8cmy29u</id>
  <published>2024-04-16T05:58:59.092+00:00</published>
  <updated>2024-04-16T05:58:59.092+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.nta.co.uk/incident/clv1z418t68117b4o9p8cmy29u"/>
  <title>Call &amp; Registration issues</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 3 days, 2 hours and 51 minutes</p>
    <p><strong>Affected Components:</strong> Outbound Calls, Inbound Calls</p>
    <p><small>Apr <var data-var='date'> 16</var>, <var data-var='time'>05:58:59</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are aware of an issue with BLFs and are currently investigating this incident..</p>
<p><small>Apr <var data-var='date'> 16</var>, <var data-var='time'>10:53:55</var> GMT+0</small><br /><strong>Identified</strong> -
  We have discovered some unusual traffic that overloaded the server which we are investigating. This is causing the call issues you may be experiencing.</p>
<p><small>Apr <var data-var='date'> 16</var>, <var data-var='time'>12:50:34</var> GMT+0</small><br /><strong>Identified</strong> -
  We are aware that there are still issues with calls and registrations on our service. We are working hard to resolve these and hope to have an outcome soon. Sorry for any inconvenience.</p>
<p><small>Apr <var data-var='date'> 16</var>, <var data-var='time'>14:37:37</var> GMT+0</small><br /><strong>Monitoring</strong> -
  We are still monitoring the calls and registrations and will update this page when we have further information.</p>
<p><small>Apr <var data-var='date'> 17</var>, <var data-var='time'>11:47:05</var> GMT+0</small><br /><strong>Monitoring</strong> -
  Although the services appear to have returned to normal we are still monitoring the situation.</p>
<p><small>Apr <var data-var='date'> 18</var>, <var data-var='time'>10:01:56</var> GMT+0</small><br /><strong>Monitoring</strong> -
  Although the calling issues have been resolved we are still seeing issues with the BLFs for some models of phones. We are investigating the cause of this.</p>
<p><small>Apr <var data-var='date'> 19</var>, <var data-var='time'>08:50:06</var> GMT+0</small><br /><strong>Resolved</strong> -
  The issue regarding calls &amp; registrations is now resolved and this ticket closed.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.nta.co.uk,2005:Maintenance/clv0vsfk527411w4lvrnrl5zii</id>
  <published>2024-04-15T23:00:00.000+00:00</published>
  <updated>2024-04-15T23:00:01.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.nta.co.uk/maintenance/clv0vsfk527411w4lvrnrl5zii"/>
  <title>Emergency Maintenance 16 April 2024</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 3 hours</p>
    <p><strong>Affected Components:</strong> MobeX Softphone, Outbound Calls, Busy Lamps, Inbound Calls, MobeX Mobile</p>
    <p><small>Apr <var data-var='date'> 15</var>, <var data-var='time'>23:00:01</var> GMT+0</small><br /><strong>Identified</strong> -
  Maintenance is now in progress.</p>
<p><small>Apr <var data-var='date'> 16</var>, <var data-var='time'>02:00:00</var> GMT+0</small><br /><strong>Completed</strong> -
  Maintenance has completed successfully.</p>
<p><small>Apr <var data-var='date'> 15</var>, <var data-var='time'>23:00:00</var> GMT+0</small><br /><strong>Identified</strong> -
  Tuesday, 16 April 2024 between 00:00 - 03:00

Work is required in order to improve our systems.

Tuesday between 00:00 - 03:00 we will be carrying out essential updates.

This maintenance is classed as at medium risk..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.nta.co.uk,2005:Incident/clv129dms4888bbn3hji8r6l3</id>
  <published>2024-04-15T14:39:20.636+00:00</published>
  <updated>2024-04-16T05:38:26.215+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.nta.co.uk/incident/clv129dms4888bbn3hji8r6l3"/>
  <title>Registration of Gigaset Phones</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 19 hours and 19 minutes</p>
    <p><strong>Affected Components:</strong> Handset Provisioning, Inbound Calls</p>
    <p><small>Apr <var data-var='date'> 16</var>, <var data-var='time'>05:38:26</var> GMT+0</small><br /><strong>Monitoring</strong> -
  While doing the emergency maintenance last night we implemented a fix for the Gigaset manufactured handsets. If your handset is still not registered please powercycle the handset. We are currently monitoring the result..</p>
<p><small>Apr <var data-var='date'> 15</var>, <var data-var='time'>14:39:20</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are aware of an issue with the registration and ringing of Gigaset handsets. We are currently investigating this issue.</p>
<p><small>Apr <var data-var='date'> 15</var>, <var data-var='time'>18:23:04</var> GMT+0</small><br /><strong>Identified</strong> -
  The investigation into Gigaset registrations is still ongoing and we will advise as soon as we have any further information.</p>
<p><small>Apr <var data-var='date'> 16</var>, <var data-var='time'>09:58:29</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved. However, should you still experience any issues with these phones please advise the support team. We apologise for any inconvenience caused.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.nta.co.uk,2005:Maintenance/cluuzg6bm444633j3ocg7y73n5n</id>
  <published>2024-04-13T21:00:00.000+00:00</published>
  <updated>2024-04-13T23:00:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.nta.co.uk/maintenance/cluuzg6bm444633j3ocg7y73n5n"/>
  <title>Planned Maintenance 13 April 2024</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 2 hours</p>
    <p><strong>Affected Components:</strong> MobeX Softphone, Outbound Calls, Busy Lamps, Inbound Calls, MobeX Mobile</p>
    <p><small>Apr <var data-var='date'> 13</var>, <var data-var='time'>23:00:00</var> GMT+0</small><br /><strong>Completed</strong> -
  Maintenance has completed successfully.</p>
<p><small>Apr <var data-var='date'> 13</var>, <var data-var='time'>21:00:01</var> GMT+0</small><br /><strong>Identified</strong> -
  Maintenance is now in progress.</p>
<p><small>Apr <var data-var='date'> 13</var>, <var data-var='time'>21:00:00</var> GMT+0</small><br /><strong>Identified</strong> -
  On Saturday 13th April 2024 from 10:00pm to midnight, essential system maintenance is scheduled to enhance our systems&#039; performance.  
  
During this upgrade, we will be improving the system reliability following the issues identified on 25th March 2024\. The enhancements will not only optimise performance but also ensure swift recovery in the event of future complications.  
  
This maintenance is classed as medium risk. .</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.nta.co.uk,2005:Incident/clul7vmex117082baou5rdkm8du</id>
  <published>2024-04-04T12:32:17.737+00:00</published>
  <updated>2024-04-04T12:32:17.737+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.nta.co.uk/incident/clul7vmex117082baou5rdkm8du"/>
  <title>internet Issues</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 23 hours and 45 minutes</p>
    <p><strong>Affected Components:</strong> Lease Lines, Wireless Internet</p>
    <p><small>Apr <var data-var='date'> 4</var>, <var data-var='time'>12:32:17</var> GMT+0</small><br /><strong>Identified</strong> -
  We are aware that the issue with the DNS of some of the circuits we provide is having issues again. We are working with the provider to resolve this and will give another update as soon as we have more information.</p>
<p><small>Apr <var data-var='date'> 4</var>, <var data-var='time'>13:03:11</var> GMT+0</small><br /><strong>Monitoring</strong> -
  The outage is believed to be linked to a global DNS amplification attack being broadcast at multiple networks..</p>
<p><small>Apr <var data-var='date'> 4</var>, <var data-var='time'>14:07:45</var> GMT+0</small><br /><strong>Monitoring</strong> -
  We have seen traffic levels return to normal following mitigating actions by our supplier&#039;s networks teams. This situation is continuing to be investigated and monitored.</p>
<p><small>Apr <var data-var='date'> 4</var>, <var data-var='time'>16:05:07</var> GMT+0</small><br /><strong>Monitoring</strong> -
  Although the issue appears to be resolved we will continue to monitor the service.</p>
<p><small>Apr <var data-var='date'> 5</var>, <var data-var='time'>12:17:20</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved. The outage was caused by a Global Dos attack on networks.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.nta.co.uk,2005:Incident/clui806208404bfofkc5el43y</id>
  <published>2024-04-02T10:12:31.480+00:00</published>
  <updated>2024-04-02T15:21:41.045+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.nta.co.uk/incident/clui806208404bfofkc5el43y"/>
  <title>Internet</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 21 days, 18 hours and 9 minutes</p>
    <p><strong>Affected Components:</strong> Lease Lines, Wireless Internet</p>
    <p><small>Apr <var data-var='date'> 2</var>, <var data-var='time'>15:21:41</var> GMT+0</small><br /><strong>Monitoring</strong> -
  We are still monitoring for any further issues..</p>
<p><small>Apr <var data-var='date'> 3</var>, <var data-var='time'>07:18:39</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved. We will issue an RFO as soon as we have the confirmed information from our suppliers.</p>
<p><small>Apr <var data-var='date'> 2</var>, <var data-var='time'>10:12:31</var> GMT+0</small><br /><strong>Identified</strong> -
  We are aware of an issue nationally with Internet services where although phone services do work the associated Internet service is not working. We are currently investigating this with our suppliers, but please check with your supplier should it not be supplied by us..</p>
<p><small>Apr <var data-var='date'> 2</var>, <var data-var='time'>10:36:16</var> GMT+0</small><br /><strong>Identified</strong> -
  We are continuing to work on a fix for this incident..</p>
<p><small>Apr <var data-var='date'> 2</var>, <var data-var='time'>11:29:03</var> GMT+0</small><br /><strong>Identified</strong> -
  We are continuing to work on a fix for this incident. The issue is indicating to be a national DNS and our suppliers are working to resolve this.</p>
<p><small>Apr <var data-var='date'> 2</var>, <var data-var='time'>12:50:47</var> GMT+0</small><br /><strong>Monitoring</strong> -
  We are seeing traffic levels return to normal and getting reports that normal service is resuming. We are awaiting for an all clear from networks teams and monitoring the situation.   .</p>
<p><small>Apr <var data-var='date'> 2</var>, <var data-var='time'>13:57:16</var> GMT+0</small><br /><strong>Monitoring</strong> -
  No further issues are being identified. We will continue to monitor the situation for any changes..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.nta.co.uk,2005:Incident/clu6zerag109549b9onbyqyur7s</id>
  <published>2024-03-25T13:26:28.079+00:00</published>
  <updated>2024-03-25T15:28:31.308+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.nta.co.uk/incident/clu6zerag109549b9onbyqyur7s"/>
  <title>Network issue</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 23 hours and 12 minutes</p>
    <p><strong>Affected Components:</strong> Web Interface, API, MobeX Softphone, Outbound Calls, Lease Lines, UC Integration, Dialer, Wallboards, Handset Provisioning, Wireless Internet, No Service Impact Expected, Busy Lamps, Inbound Calls, NTA Homepage, MobeX Mobile</p>
    <p><small>Mar <var data-var='date'> 25</var>, <var data-var='time'>15:28:31</var> GMT+0</small><br /><strong>Identified</strong> -
  Unfortunately the resolution found has not cleared the issue. We are working to resolve the issue and apologise again for any inconvenience.</p>
<p><small>Mar <var data-var='date'> 25</var>, <var data-var='time'>13:26:28</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are aware of an issue affecting our network. We are currently working to resolve this and apologise for any issue this is causing you.</p>
<p><small>Mar <var data-var='date'> 25</var>, <var data-var='time'>13:46:11</var> GMT+0</small><br /><strong>Identified</strong> -
  The BLF monitoring will shortly be disabled, the connections will then be momentarily dropped and then the servers restarted to resolve the issue.</p>
<p><small>Mar <var data-var='date'> 25</var>, <var data-var='time'>14:32:56</var> GMT+0</small><br /><strong>Identified</strong> -
  We are continuing to work on a fix for this incident. The network is slowly returning to normal and hopefully will be fully functioning shortly.</p>
<p><small>Mar <var data-var='date'> 25</var>, <var data-var='time'>15:40:06</var> GMT+0</small><br /><strong>Monitoring</strong> -
  The system is now back and working, however, the BLF function will remain off until this evening so that it can be brought back online when the traffic is lower and the network has fully stabilised.</p>
<p><small>Mar <var data-var='date'> 25</var>, <var data-var='time'>17:20:36</var> GMT+0</small><br /><strong>Monitoring</strong> -
  We implemented a fix and are currently monitoring the result. There are a few calls that are stuck and are being cleared as soon as possible.</p>
<p><small>Mar <var data-var='date'> 26</var>, <var data-var='time'>08:12:21</var> GMT+0</small><br /><strong>Monitoring</strong> -
  We now believe the issue to be resolved but will keep monitoring. An RFO will be issued in due course.</p>
<p><small>Mar <var data-var='date'> 26</var>, <var data-var='time'>12:38:48</var> GMT+0</small><br /><strong>Resolved</strong> -
  **Incident Resolution and Future Plans**  
  
On the morning of 25/03, we encountered issues with our SIP server as multiple extensions were unable to register due to a memory leak. After migrating to our secondary server and rebooting the main server, a deadlock situation arose, preventing either server from providing services. To address this, we performed a quick reboot of both servers, with our Disaster Recovery solution effectively redirecting inbound calls during the process.  
  
Upon bringing the SIP servers back online, we encountered a recurrence of the issues due to an overwhelming number of BLF requests bombarding the server, causing system instability. This highlighted the need for a more robust solution to handle such scenarios in the future.  
  
We are currently in the process of updating the SIP server and transitioning to a more advanced version of our redundancy software, with a particular focus on efficiently handling BLF requests. As a result, the new BLF approach and the updated SIP servers will take precedence as critical projects, undergoing extensive testing and meticulous attention.  
  
We plan to implement these updates on a Saturday night after 10PM to minimize potential minor instability during the transition, and we will provide advance notification before proceeding. We sincerely apologize for the inconvenience caused and assure you that we are leveraging this experience to enhance the redundancy and reliability of our systems, delivering a solution that meets your expectations..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.nta.co.uk,2005:Incident/clvxv8tgg5120bbonh75nckq8</id>
  <published>2024-03-25T10:31:00.000+00:00</published>
  <updated>2024-03-25T10:31:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.nta.co.uk/incident/clvxv8tgg5120bbonh75nckq8"/>
  <title>RFO and Update for 25.03.24 </title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> MobeX Softphone, Outbound Calls, Handset Provisioning, No Service Impact Expected, Busy Lamps, Inbound Calls, MobeX Mobile</p>
    <p><small>Mar <var data-var='date'> 25</var>, <var data-var='time'>10:31:00</var> GMT+0</small><br /><strong>Resolved</strong> -
  After the recent system outage on 25/03, we encountered a surge of requests from our users, particularly regarding BLF subscriptions. This uptake in BLF usage has been remarkable, showcasing the growing demand for our services. Recognising this shift, we developed a new and robust solution to effectively manage the current and future influx of BLFs within our system.  
  
**Incremental Implementation for Enhanced Performance**  
  
Beginning on 13/04, we initiated the implementation of our new solutions daily, carefully orchestrating this process during off-peak hours to ensure seamless service for our users. While this approach initially posed challenges in testing the solution in real-time scenarios, it allowed us to meticulously fine-tune our processes, guaranteeing a smooth transition without compromising the quality of our services.  
  
**Confidence in Future Network Growth**  
  
Following several days of meticulous development and deployment, we are now extremely confident in our ability to accommodate the anticipated growth of our network. Our new solution, a robust distributed cluster of servers dedicated solely to handling BLF subscriptions, marks a pivotal advancement.  
By segregating BLFs from other SIP packets and enabling on-demand server scaling, we have fortified our infrastructure to swiftly adapt to any unforeseen traffic spikes and effectively reduce any potential &quot;DDOS&quot; attacks.  
  
We are proud to have established an enhanced system that ensures the seamless management of BLFs and provides a secure and adaptable framework for our network&#039;s future growth..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.nta.co.uk,2005:Incident/clrrppde523845baoc9yffu9ko</id>
  <published>2024-01-24T11:38:49.380+00:00</published>
  <updated>2024-01-24T11:38:49.380+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.nta.co.uk/incident/clrrppde523845baoc9yffu9ko"/>
  <title>Mobex+ on Android</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 2 days, 1 hour and 36 minutes</p>
    <p><strong>Affected Components:</strong> MobeX Mobile</p>
    <p><small>Jan <var data-var='date'> 24</var>, <var data-var='time'>11:38:49</var> GMT+0</small><br /><strong>Identified</strong> -
  We have been made aware that we are getting warnings about the safety of the Mobex+ app on Android, while it is still safe to use we are continuing to work on a fix for this notification..</p>
<p><small>Jan <var data-var='date'> 26</var>, <var data-var='time'>13:14:51</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved and Google has accepted our policies for Mobex+ certification.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.nta.co.uk,2005:Incident/clr93dqmk224951bqoeqik2cfee</id>
  <published>2024-01-11T10:54:04.024+00:00</published>
  <updated>2024-01-11T10:54:04.024+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.nta.co.uk/incident/clr93dqmk224951bqoeqik2cfee"/>
  <title>Mobex+ on Android</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 22 hours and 12 minutes</p>
    <p><strong>Affected Components:</strong> MobeX Mobile</p>
    <p><small>Jan <var data-var='date'> 11</var>, <var data-var='time'>10:54:04</var> GMT+0</small><br /><strong>Identified</strong> -
  Google has again deemed some of the components for the certification of Mobex+ on Android to be invalid and you may get a security notification, this is despite them agreeing it was safe back in July 2023. The app is perfectly safe to use but at the moment you will not be able to download it from the Play Store. We are continuing to work on a fix for this incident and apologise for any inconvenience it may cause you..</p>
<p><small>Jan <var data-var='date'> 12</var>, <var data-var='time'>09:06:11</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved and Mobex+ is now available in Play Store..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.nta.co.uk,2005:Incident/clr0dehoh35479ban783iulm9e</id>
  <published>2024-01-05T08:24:40.021+00:00</published>
  <updated>2024-01-06T17:43:28.525+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.nta.co.uk/incident/clr0dehoh35479ban783iulm9e"/>
  <title>Mobex+ On Android</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 day, 9 hours and 19 minutes</p>
    <p><strong>Affected Components:</strong> MobeX Mobile</p>
    <p><small>Jan <var data-var='date'> 6</var>, <var data-var='time'>17:43:28</var> GMT+0</small><br /><strong>Resolved</strong> -
  This has now been resolved and Mobex+ is now back available on the Play Store.</p>
<p><small>Jan <var data-var='date'> 5</var>, <var data-var='time'>08:24:40</var> GMT+0</small><br /><strong>Identified</strong> -
  Google has again deemed some of the components for the certification of Mobex+ on Android to be invalid and you may get a security notification, this is despite them agreeing it was safe. The app is perfectly safe to use but at the moment you will not be able to download it from the Play Store. We are continuing to work on a fix for this incident and apologise for any inconvenience it may cause you.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.nta.co.uk,2005:Incident/clqnma1cj13149b3n50zjtsdjh</id>
  <published>2023-12-27T10:12:08.140+00:00</published>
  <updated>2023-12-28T09:36:24.240+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.nta.co.uk/incident/clqnma1cj13149b3n50zjtsdjh"/>
  <title>Mobex on Android</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> MobeX Mobile</p>
    <p><small>Dec <var data-var='date'> 28</var>, <var data-var='time'>09:36:24</var> GMT+0</small><br /><strong>Resolved</strong> -
  The incident has now been resolved and the app is available on Playstore now.</p>
<p><small>Dec <var data-var='date'> 27</var>, <var data-var='time'>10:12:08</var> GMT+0</small><br /><strong>Identified</strong> -
  Android users of Mobex may see a notification on their devices that the app is harmful to their device and to uninstall it. Please advise them **not** to do so as it is an error on Google&#039;s part with their certification. We are working with Google to get a quick resolution and apologise for any confusion this may be causing.</p>

        ]]>
  </content>
</entry>

</feed>