<?xml version="1.0" encoding="UTF-8"?>
<feed xml:lang="en-US" xmlns="http://www.w3.org/2005/Atom">
  <id>tag:status.elite.uk,2005:/history</id>
  <link rel="alternate" type="text/html" href="https://status.elite.uk"/>
  <link rel="self" type="application/atom+xml" href="https://status.elite.uk/history.atom"/>
  <title>Elite Limited Status - Incident history</title>
  <updated>2026-05-25T00:46:00.000+00:00</updated>
  <author>
    <name>Elite Limited</name>
  </author>
  
<entry>
  <id>tag:status.elite.uk,2005:Incident/cmpkvpcit00unqnmjvikb2wlm</id>
  <published>2026-05-25T00:46:00.000+00:00</published>
  <updated>2026-05-25T00:46:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.elite.uk/incident/cmpkvpcit00unqnmjvikb2wlm"/>
  <title>IXN POP Connectivity Outage</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 7 hours and 18 minutes</p>
    <p><strong>Affected Components:</strong> Wavelength Services, Colocation Services</p>
    <p><small>May <var data-var='date'> 25</var>, <var data-var='time'>00:46:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are investigating a loss of resilience affecting our IXN POP.

At 01:46 BST, one side of the IXN DWDM connectivity path reported both associated interfaces down. Services remain operational at this stage, but the site is operating with reduced resilience.

Further updates will be provided as the investigation progresses..</p>
<p><small>May <var data-var='date'> 25</var>, <var data-var='time'>01:39:00</var> GMT+0</small><br /><strong>Identified</strong> -
  The issue has been identified as a loss of both DWDM connectivity paths into the IXN POP.

At 02:39 BST, the remaining DWDM path also went down, causing a loss of connectivity to the IXN POP.

Initial optical diagnostics indicate receive signal loss on the affected DWDM interfaces. We are aware of unauthorised activity by a data centre engineer in our rack involving cable movement, which is considered the most likely cause.

A case has been raised with DC Techs to investigate and restore the affected connectivity and outstanding resilience as soon as possible..</p>
<p><small>May <var data-var='date'> 25</var>, <var data-var='time'>01:51:00</var> GMT+0</small><br /><strong>Monitoring</strong> -
  Connectivity to the IXN POP was restored at 02:51 BST.

The confirmed full outage window was from 02:39:35 BST to 02:51:02 BST, with a total impact duration of 11 minutes and 27 seconds.

Services are operational again; however, the POP remains in a reduced-resilience state while DC Techs continue work to restore the outstanding DWDM path.

We are continuing to monitor the site until full resilience is restored..</p>
<p><small>May <var data-var='date'> 25</var>, <var data-var='time'>04:51:00</var> GMT+0</small><br /><strong>Monitoring</strong> -
  We are continuing to monitor the IXN POP following the earlier restoration of connectivity.

Services remain operational; however, the POP is still operating in a reduced-resilience state while we await DC Techs restoring the outstanding affected DWDM path.

This has been chased with DC Techs on multiple occasions. We will also be raising this incident, along with previous issues observed at this POP, with the account manager for further review and escalation..</p>
<p><small>May <var data-var='date'> 25</var>, <var data-var='time'>07:04:00</var> GMT+0</small><br /><strong>Monitoring</strong> -
  The outstanding IXN DWDM resilience issue appears to have been restored.

At 08:04 BST, the previously affected DWDM interfaces returned to an UP state following work by data centre technicians. This indicates the downed DWDM link has been repatched/restored.

IXN POP connectivity and path resilience are currently operational again. We are continuing to monitor for stability before marking this incident as resolved..</p>
<p><small>May <var data-var='date'> 25</var>, <var data-var='time'>08:04:00</var> GMT+0</small><br /><strong>Resolved</strong> -
  IXN POP connectivity and DWDM path resilience have remained stable following restoration of the affected DWDM link at 08:04 BST.

This incident is now resolved.

The confirmed full service outage lasted from 02:39:35 BST to 02:51:02 BST, with a customer-impacting duration of 11 minutes and 27 seconds.

The reduced-resilience period lasted from 01:46:44 BST to 08:04:51 BST, with a total duration of 6 hours, 18 minutes and 7 seconds.

We will be escalating this incident with the POP account manager and requesting a full Reason for Outage report from the data centre regarding the unauthorised rack access and disconnection/disturbance of patch leads within our rack..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.elite.uk,2005:Maintenance/cmp5oj9u702b9qqnjsod9zmrd</id>
  <published>2026-05-22T23:00:00.000+00:00</published>
  <updated>2026-05-22T23:00:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.elite.uk/maintenance/cmp5oj9u702b9qqnjsod9zmrd"/>
  <title>Verne Global - Planned Maintenance</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 1 hour and 26 minutes</p>
    <p><strong>Affected Components:</strong> Colocation Services, Carrier Interconnects, Shared Web Hosting Services, Backup Services, Email Services, Monitoring Portals, ns1.elite.uk, Carrier Interconnects, resolver100.elite.net.uk, Ethernet Switching</p>
    <p><small>May <var data-var='date'> 22</var>, <var data-var='time'>23:00:00</var> GMT+0</small><br /><strong>Identified</strong> -
  We will be carrying out emergency maintenance to apply updates to our switching infrastructure.

**Maintenance Window**  
00:00 BST – 02:00 BST

**Services Affected**

* IP Transit Services
* Layer 2 Services
* Ethernet Services
* Hosting Services
* Broadband Interconnects
* Ethernet Interconnects

During the maintenance window, two devices will be upgraded. Each device is expected to cause approximately **10 minutes of service interruption** while it is upgraded.

Customers with **redundant services** should only experience impact to **one service at a time**.

Although the maintenance window is scheduled for two hours, the **expected outage per device is approximately 10 minutes**, and services will be restored as quickly as possible once upgrades are completed..</p>
<p><small>May <var data-var='date'> 22</var>, <var data-var='time'>23:00:01</var> GMT+0</small><br /><strong>Identified</strong> -
  Maintenance is now in progress.</p>
<p><small>May <var data-var='date'> 23</var>, <var data-var='time'>00:26:13</var> GMT+0</small><br /><strong>Completed</strong> -
  Maintenance has been completed successfully.

We apologise for any outages that you may have experienced..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.elite.uk,2005:Maintenance/cmpf9g94n01bopdjpxtptlwlt</id>
  <published>2026-05-22T18:00:00.000+00:00</published>
  <updated>2026-05-22T18:00:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.elite.uk/maintenance/cmpf9g94n01bopdjpxtptlwlt"/>
  <title>DWDM Wavelength Services &amp; DCIs (Interxion LON)</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 5 hours and 30 minutes</p>
    <p><strong>Affected Components:</strong> Wavelength Services, Carrier Interconnects</p>
    <p><small>May <var data-var='date'> 22</var>, <var data-var='time'>18:00:00</var> GMT+0</small><br /><strong>Identified</strong> -
  A planned maintenance will take place from **19:00 to 21:00** for DWDM wavelength services and associated hardware upgrades.

During this window:

* Some wavelength services will be **fully unavailable** for periods within the duration of the maintenance.
* Some NNI services will be **fully unavailable** for periods within the maintenance window.
* **Dual-homed services** will operate with **reduced resiliency** and may experience **minor service disruption**.

We will work to minimise impact and restore full service promptly following completion..</p>
<p><small>May <var data-var='date'> 22</var>, <var data-var='time'>18:00:01</var> GMT+0</small><br /><strong>Identified</strong> -
  Maintenance is now in progress.</p>
<p><small>May <var data-var='date'> 22</var>, <var data-var='time'>19:47:21</var> GMT+0</small><br /><strong>Identified</strong> -
  Unfortunately, we have had to extend the maintenance window by an additional 2 hours due to an issue currently affecting the DCI services.

At present, only a single wavelength service is impacted.

Our on-site engineers are currently working with the data centre technicians to investigate and resolve issues relating to the pre-cabling within the facility..</p>
<p><small>May <var data-var='date'> 22</var>, <var data-var='time'>21:43:34</var> GMT+0</small><br /><strong>Identified</strong> -
  We have now confirmed with the data centre technicians that the issue relates to an incorrect patching matrix within the data centre pre-cabling, and is not caused by Elite equipment or services.

The data centre team is currently correcting the patching, and we are awaiting confirmation before proceeding further with the planned maintenance activities..</p>
<p><small>May <var data-var='date'> 22</var>, <var data-var='time'>22:06:43</var> GMT+0</small><br /><strong>Identified</strong> -
  Please disregard any previous completion notice; this maintenance is still open and has been extended further.

At present, only a single-wavelength service is still impacted.

We are still awaiting confirmation from the data centre before proceeding further with the planned maintenance activities..</p>
<p><small>May <var data-var='date'> 22</var>, <var data-var='time'>22:24:12</var> GMT+0</small><br /><strong>Identified</strong> -
  The data centre technicians have now correctly patched the affected wavelength service and successfully restored service.

They are currently verifying the remaining patching before we proceed with the next stage of the planned migrations..</p>
<p><small>May <var data-var='date'> 22</var>, <var data-var='time'>23:30:00</var> GMT+0</small><br /><strong>Completed</strong> -
  Maintenance has completed successfully..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.elite.uk,2005:Maintenance/cmok6xif10046qaetj1af3u4i</id>
  <published>2026-04-29T19:00:00.000+00:00</published>
  <updated>2026-04-29T19:00:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.elite.uk/maintenance/cmok6xif10046qaetj1af3u4i"/>
  <title>Harbour Exchange (LD8) - Emergency Maintenance</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 4 hours</p>
    <p><strong>Affected Components:</strong> Carrier Interconnects</p>
    <p><small>Apr <var data-var='date'> 29</var>, <var data-var='time'>19:00:00</var> GMT+0</small><br /><strong>Identified</strong> -
  We will be carrying out emergency maintenance to apply critical updates to our switching infrastructure.

**Maintenance Window**  
20:00 BST – 00:00 BST

**Services Affected**

* Ethernet Services

During the maintenance window, two devices will be upgraded. Each device is expected to cause approximately **10 minutes of service interruption** during its upgrade.

Customers with **redundant services** should only experience impact to **one service at a time**.

Although the maintenance window is scheduled for two hours, the **expected outage per device is approximately 10 minutes**, and services will be restored as quickly as possible once upgrades are completed..</p>
<p><small>Apr <var data-var='date'> 29</var>, <var data-var='time'>19:00:01</var> GMT+0</small><br /><strong>Identified</strong> -
  Maintenance is now in progress.</p>
<p><small>Apr <var data-var='date'> 29</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.elite.uk,2005:Maintenance/cmok758g5005owmslbh2dd2xe</id>
  <published>2026-04-29T19:00:00.000+00:00</published>
  <updated>2026-04-29T19:00:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.elite.uk/maintenance/cmok758g5005owmslbh2dd2xe"/>
  <title>IX Peering Maintenance – AS29611 (LINX LON1 &amp; LON2)</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 2 hours</p>
    <p><strong>Affected Components:</strong> Core Routing</p>
    <p><small>Apr <var data-var='date'> 29</var>, <var data-var='time'>19:00:00</var> GMT+0</small><br /><strong>Identified</strong> -
  **Description:**  
Elite will be performing planned maintenance that will affect peering sessions at LINX LON1 and LON2.

During this window, peering sessions will be temporarily shut down, and traffic may reroute via alternative paths where available.

**Impact:**

* Temporary loss of peering at LINX LON1 and LON2

**Additional Information:**  
If sessions do not automatically re-establish after the maintenance window, peers should verify that prefix limits align with our PeeringDB entry:  
&lt;https://www.peeringdb.com/net/1759&gt;

* IPv4: 150 prefixes
* IPv6: 30 prefixes.</p>
<p><small>Apr <var data-var='date'> 29</var>, <var data-var='time'>19:00:01</var> GMT+0</small><br /><strong>Identified</strong> -
  Maintenance is now in progress.</p>
<p><small>Apr <var data-var='date'> 29</var>, <var data-var='time'>21:00:00</var> GMT+0</small><br /><strong>Completed</strong> -
  Maintenance has completed successfully.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.elite.uk,2005:Maintenance/cmmj3gu200022hc1eadpsle26</id>
  <published>2026-03-10T01:00:00.000+00:00</published>
  <updated>2026-03-10T01:00:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.elite.uk/maintenance/cmmj3gu200022hc1eadpsle26"/>
  <title>Telehouse North - Emergency Maintenance</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 2 hours</p>
    <p><strong>Affected Components:</strong> Carrier Interconnects, LNS/Radius Services, Ethernet Switching, Wavelength Services, Colocation Services, Carrier Interconnects</p>
    <p><small>Mar <var data-var='date'> 10</var>, <var data-var='time'>01:00:00</var> GMT+0</small><br /><strong>Identified</strong> -
  We will be carrying out emergency maintenance to apply critical updates to our switching infrastructure. 

**Maintenance Window**  
01:00 GMT – 03:00 GMT

**Services Affected**

* Ethernet Services
* Broadband Services
* LNS / RADIUS Services
* Ethernet Interconnects
* Broadband Interconnects

During the maintenance window, two devices will be upgraded. Each device is expected to cause approximately **10 minutes of service interruption** while it is upgraded.

Customers with **redundant services** should only experience impact to **one service at a time**.

Although the maintenance window is scheduled for two hours, the **expected outage per device is approximately 10 minutes**, and services will be restored as quickly as possible once upgrades are completed..</p>
<p><small>Mar <var data-var='date'> 10</var>, <var data-var='time'>01:00:01</var> GMT+0</small><br /><strong>Identified</strong> -
  Maintenance is now in progress.</p>
<p><small>Mar <var data-var='date'> 10</var>, <var data-var='time'>03:00:00</var> GMT+0</small><br /><strong>Completed</strong> -
  Maintenance has completed successfully.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.elite.uk,2005:Incident/cmmc1rocq02gjhzbykztnwhqi</id>
  <published>2026-03-04T10:45:00.000+00:00</published>
  <updated>2026-03-05T04:38:25.027+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.elite.uk/incident/cmmc1rocq02gjhzbykztnwhqi"/>
  <title>Degraded Optical Levels on Inter-Datacentre Metro Fibre Link</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 17 hours and 53 minutes</p>
    <p><strong>Affected Components:</strong> , Wavelength Services, 
Datacenter Services →</p>
    <p><small>Mar <var data-var='date'> 5</var>, <var data-var='time'>04:38:25</var> GMT+0</small><br /><strong>Resolved</strong> -
  The issue affecting the metro fibre link between our datacentres has now been resolved, and optical levels have returned to normal operating ranges.

Services across the link remain fully operational, and no further issues are currently being observed.

We are currently awaiting **RFOs** from the relevant fibre providers to confirm the underlying cause of the degradation.

Further information will be shared if additional details become available..</p>
<p><small>Mar <var data-var='date'> 4</var>, <var data-var='time'>10:45:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are currently investigating degraded optical receive levels in one direction of a metro fibre link between two of our datacentres.

At this time, **no service outage or traffic impact** has been observed, and network services across the link remain operational.

Monitoring has identified that the received light level in one direction is **significantly lower than the corresponding transmit level in the opposite direction**. Our network engineering team is reviewing the circuit and monitoring the link closely.

Further updates will be provided as the investigation progresses..</p>
<p><small>Mar <var data-var='date'> 4</var>, <var data-var='time'>11:00:00</var> GMT+0</small><br /><strong>Identified</strong> -
  The issue has been identified as degraded optical receive levels in one direction of the metro fibre link between our datacentres.

While services remain operational with **no current outage**, the fibre provider has been engaged to investigate the underlying infrastructure and determine the cause of the degraded light levels.

During this investigation, there **may be brief periods of disruption** while testing or maintenance activities are carried out on the circuit.

Further updates will be provided as more information becomes available..</p>
<p><small>Mar <var data-var='date'> 4</var>, <var data-var='time'>13:36:31</var> GMT+0</small><br /><strong>Identified</strong> -
  The fibre provider is actively investigating the degraded optical levels on the metro fibre link between our datacentres.

Services across the link remain operational with **no current outage observed**. Our network engineering team continues to monitor the circuit closely while the provider conducts its investigation.

Further updates will be provided as soon as additional information becomes available..</p>
<p><small>Mar <var data-var='date'> 4</var>, <var data-var='time'>15:06:55</var> GMT+0</small><br /><strong>Identified</strong> -
  The fibre provider is actively investigating the degraded optical levels on the metro fibre link between our datacentres.

Services across the link remain operational with **no current outage observed**. Our network engineering team continues to monitor the circuit closely while the provider conducts its investigation.

We are currently working with the fibre provider to organise a suitable maintenance window so that a **full outage of the fibre path can be taken with the least possible impact**, allowing further testing and investigation to take place.

Further updates will be provided as soon as additional information becomes available..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.elite.uk,2005:Maintenance/cmlarb9jk01jt11whp04ln9hn</id>
  <published>2026-02-09T18:00:00.000+00:00</published>
  <updated>2026-02-09T18:00:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.elite.uk/maintenance/cmlarb9jk01jt11whp04ln9hn"/>
  <title>DWDM Wavelength Services and Hardware Upgrade (Interxion LON)</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 4 hours and 30 minutes</p>
    <p><strong>Affected Components:</strong> Wavelength Services, Colocation Services, Carrier Interconnects</p>
    <p><small>Feb <var data-var='date'> 9</var>, <var data-var='time'>18:00:00</var> GMT+0</small><br /><strong>Identified</strong> -
  A planned maintenance will take place from **18:00 to 04:00** for DWDM wavelength services and associated hardware upgrades.

During this window:

* Some wavelength services will be **fully unavailable** for periods within the duration of the maintenance.
* **Dual-homed services** will operate with **reduced resiliency** and may experience **minor service disruption**.

We will work to minimise impact and restore full service promptly following completion..</p>
<p><small>Feb <var data-var='date'> 9</var>, <var data-var='time'>18:00:01</var> GMT+0</small><br /><strong>Identified</strong> -
  Maintenance is now in progress.</p>
<p><small>Feb <var data-var='date'> 9</var>, <var data-var='time'>20:00:00</var> GMT+0</small><br /><strong>Identified</strong> -
  All services have been migrated and upgraded successfully. We will verify all services have resumed and continue to monitor for the next hour..</p>
<p><small>Feb <var data-var='date'> 9</var>, <var data-var='time'>21:30:00</var> GMT+0</small><br /><strong>Identified</strong> -
  We have been monitoring the services and are happy that all services are operating as expected. 

If you are experiencing any issues, please do not hesitate to contact us via Phone on 0330 122 0300 or by raising a ticket by emailing noc@elite.uk..</p>
<p><small>Feb <var data-var='date'> 9</var>, <var data-var='time'>22:30:00</var> GMT+0</small><br /><strong>Completed</strong> -
  Maintenance has been completed successfully.

If you are experiencing any issues, please do not hesitate to contact us via Phone on 0330 122 0300 or by raising a ticket by emailing noc@elite.uk..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.elite.uk,2005:Incident/cmc4uel1w0004ed34dvesj7yl</id>
  <published>2025-06-20T12:40:00.000+00:00</published>
  <updated>2025-06-20T12:40:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.elite.uk/incident/cmc4uel1w0004ed34dvesj7yl"/>
  <title>Upstream Traffic Routing Issues (Cogent)</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 10 hours and 34 minutes</p>
    <p><strong>Affected Components:</strong> Core Routing</p>
    <p><small>Jun <var data-var='date'> 20</var>, <var data-var='time'>12:40:00</var> GMT+0</small><br /><strong>Identified</strong> -
  We (along with many other service providers) seem to have been affected by an issue on Cogent&#039;s network. Cogent supply Elite with one of its transit feeds. Routes traversing Cogent in its path are experiencing issues. We have lowered our transit feed to Cogent whilst they get to the bottom of the issue. At this stage information is limited but we will update this incident accordingly. Our peering on all the major peering exchanges and our other diverse Transit feeds appear at this stage unaffected. However if a path somewhere along the line traverses any Cogent network there could be some disruption there. This unfortunately is out of our control but we are monitoring closely..</p>
<p><small>Jun <var data-var='date'> 20</var>, <var data-var='time'>13:26:00</var> GMT+0</small><br /><strong>Monitoring</strong> -
  We implemented a fix by expunging our transit feed to Cogent whilst they get to the bottom of the issue. We are currently monitoring the result; however, routing performance is degraded during this time until we are happy that Cogent have implemented a fix..</p>
<p><small>Jun <var data-var='date'> 20</var>, <var data-var='time'>14:31:00</var> GMT+0</small><br /><strong>Monitoring</strong> -
  Cogent have confirmed the issue is resolved. 

Elite will keep the peer down until low traffic hours to minimise any potential disruption during route convergence..</p>
<p><small>Jun <var data-var='date'> 20</var>, <var data-var='time'>23:13:57</var> GMT+0</small><br /><strong>Resolved</strong> -
  Elite have re-established the peer facing Cogent, and we are now receiving full routing from the peer. 

Traffic levels have normalised, and routing resiliency has been fully restored. We will continue to monitor for stability, but no further disruption is expected.

This incident is now resolved. 

We will update this incident with the RFO from the transit provider once it has been received..</p>
<p><small>Jun <var data-var='date'> 24</var>, <var data-var='time'>09:20:11</var> GMT+0</small><br /><strong>Postmortem</strong> -
  The issue affecting connectivity via Cogent on June 20th has been fully resolved.

We have received the following RFO (Reason for Outage) from Cogent:

&gt; _“Customers in or transiting Slough may have experienced severe service degradation on June 20th between 12:18 and 13:32 GMT._
&gt; 
&gt; _During a routine configuration change on one of our core routers in Slough, unexpected behavior occurred resulting in entirely unexpected side effects._
&gt; 
&gt; _As soon as the issue was noticed, our IP Engineering department was involved to urgently resolve the issue._
&gt; 
&gt; _Please note that as a result of this issue, internal processes are being carefully reviewed to identify areas for improvement and help prevent similar occurrences in the future._
&gt; 
&gt; _We sincerely apologize for the inconvenience and appreciate your patience and understanding during this time.”_

### Actions Taken by Elite

* The affected peer was taken down promptly to prevent routing instability and protect service performance.
* Traffic was rerouted to ensure continuity for customers during the outage.
* Once Cogent confirmed the issue was resolved, Elite delayed re-enabling the peer until off-peak hours to avoid route convergence disruption.
* The peer was re-established during low traffic hours, with routing verified as stable.

We appreciate your understanding and patience while we worked to mitigate the impact of this incident.

Kind Regards 

Elite NOC.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.elite.uk,2005:Incident/cmb972nmb001acgxduliqjx6u</id>
  <published>2025-05-29T09:51:32.469+00:00</published>
  <updated>2025-05-29T09:51:32.469+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.elite.uk/incident/cmb972nmb001acgxduliqjx6u"/>
  <title>Fibre outage - Telehouse North to Interxion</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 57 minutes</p>
    <p><strong>Affected Components:</strong> Core Routing, Ethernet Switching, Wavelength Services</p>
    <p><small>May <var data-var='date'> 29</var>, <var data-var='time'>09:51:32</var> GMT+0</small><br /><strong>Identified</strong> -
  We have identified a fibre outage on one of our paths from Telehouse North to Interxion.

We are raising the issue with our fibre provider.

All traffic is flowing on our other diverse fibre runs and is unaffected. However services traversing Interxion are currently deemed &#039;at risk&#039;..</p>
<p><small>May <var data-var='date'> 29</var>, <var data-var='time'>11:01:50</var> GMT+0</small><br /><strong>Identified</strong> -
  The fibre provider has identified the fault and are working on a resolution.

We will update in due course once resolved..</p>
<p><small>May <var data-var='date'> 29</var>, <var data-var='time'>11:49:00</var> GMT+0</small><br /><strong>Resolved</strong> -
  The fibre provider has resolved the issue and we have seen services return.

We will close off this issue. Services are no longer at risk..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.elite.uk,2005:Incident/cmafg4pii000461trnqh5sqc7</id>
  <published>2025-05-08T14:11:59.396+00:00</published>
  <updated>2025-05-08T14:11:59.396+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.elite.uk/incident/cmafg4pii000461trnqh5sqc7"/>
  <title>Datacenter Power Feed Issue</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 2 days, 6 hours and 24 minutes</p>
    <p><strong>Affected Components:</strong> Colocation Services</p>
    <p><small>May <var data-var='date'> 8</var>, <var data-var='time'>14:11:59</var> GMT+0</small><br /><strong>Identified</strong> -
  We are aware of an ongoing issue that has caused loss of power to a single power feed in one of our co-locations.

We’re waiting further updates regarding this. .</p>
<p><small>May <var data-var='date'> 8</var>, <var data-var='time'>14:40:23</var> GMT+0</small><br /><strong>Identified</strong> -
  We have had the following from the Datacentre operator:

\--

  
The manufacturer is aware of the fault and they will send an engineer to the site.  
Identified  
  
UPS C2 fuse issue triggered the evacuation system; engineers investigated immediately and found no signs of fire. The faulty UPS was isolated, and the load was transferred to the remaining UPS. The site remained stable and is operating on N+1 in UPS C. The Manufacturer was notified and en route to the site.

\--

We will update in due course..</p>
<p><small>May <var data-var='date'> 8</var>, <var data-var='time'>17:33:36</var> GMT+0</small><br /><strong>Monitoring</strong> -
  Although we saw power return at circa 4pm to the affected feed, we are keeping this incident open, as the datacentre still has engineers on site. We will close this once they confirm to us the all clear..</p>
<p><small>May <var data-var='date'> 8</var>, <var data-var='time'>15:14:37</var> GMT+0</small><br /><strong>Monitoring</strong> -
  We are starting to see power return to the affected feed.

We are monitoring this and liaising with the datacentre.

We will update asap..</p>
<p><small>May <var data-var='date'> 9</var>, <var data-var='time'>09:59:27</var> GMT+0</small><br /><strong>Monitoring</strong> -
  We have received the following update from the Datacenter:  
  
&quot;Replacement part required for UPS C, module 2\. ETA to be confirmed. Load is currently supported across modules C1 and C3 at N+1 redundancy.

Update will be sent out as soon as the part is replaced and the module is back online.&quot;  
  
As full functionality has not been restored, we will continue to hold this incident open and post status updates here..</p>
<p><small>May <var data-var='date'> 10</var>, <var data-var='time'>20:36:00</var> GMT+0</small><br /><strong>Resolved</strong> -
  We have received the following from the datacenter and are happy that all services have resumed to full capacity. Therefore, we will be closing this incident.

&quot;UPS C2 module 2 has now been replaced and tested by Vertiv. UPS system C2 is now back on load with no issues and all alarms cleared. Monitoring of the system will continue to take place by on-site engineers over the rest of the weekend.&quot;.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.elite.uk,2005:Incident/cm84amqvk003apbs5hveizgtz</id>
  <published>2025-03-11T08:05:00.000+00:00</published>
  <updated>2025-03-11T08:05:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.elite.uk/incident/cm84amqvk003apbs5hveizgtz"/>
  <title>Elite Telephone Switchboard</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 4 hours and 18 minutes</p>
    <p><strong>Affected Components:</strong> Telephone Switchboard</p>
    <p><small>Mar <var data-var='date'> 11</var>, <var data-var='time'>08:05:00</var> GMT+0</small><br /><strong>Identified</strong> -
  We have been informed by our upstream voice provider that they are suffering an issue and our main lines are currently experiencing an issue. We will update in due course.

In the meantime our normal ticket and live chat channels remain unaffected..</p>
<p><small>Mar <var data-var='date'> 11</var>, <var data-var='time'>12:23:28</var> GMT+0</small><br /><strong>Resolved</strong> -
  We are marking this as resolved now as we have had communication from our upstream that they have now brought back online our services..</p>

        ]]>
  </content>
</entry>

</feed>