Elite UK Outage History

Started May 25, 2026, 12:46 AM UTC· resolved May 25, 2026, 08:04 AM UTC

1. investigating May 25, 2026, 12:46 AM UTC

   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..

2. identified May 25, 2026, 01:39 AM UTC

   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..

3. monitoring May 25, 2026, 01:51 AM UTC

   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..

4. monitoring May 25, 2026, 04:51 AM UTC

   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..

5. monitoring May 25, 2026, 07:04 AM UTC

   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..

6. resolved May 25, 2026, 08:04 AM UTC

   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..

Read the full incident report →

Started Mar 04, 2026, 10:45 AM UTC· resolved Mar 05, 2026, 04:38 AM UTC

1. investigating Mar 04, 2026, 10:45 AM UTC

   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..

2. identified Mar 04, 2026, 11:00 AM UTC

   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..

3. identified Mar 04, 2026, 01:36 PM UTC

   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..

4. identified Mar 04, 2026, 03:06 PM UTC

   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..

5. resolved Mar 05, 2026, 04:38 AM UTC

   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..

Read the full incident report →

Started Feb 09, 2026, 06:00 PM UTC· resolved Feb 09, 2026, 06:00 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Started Jun 20, 2025, 12:40 PM UTC· resolved Jun 20, 2025, 11:13 PM UTC

1. identified Jun 20, 2025, 12:40 PM UTC

   We (along with many other service providers) seem to have been affected by an issue on Cogent'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..

2. monitoring Jun 20, 2025, 01:26 PM UTC

   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..

3. monitoring Jun 20, 2025, 02:31 PM UTC

   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..

4. resolved Jun 20, 2025, 11:13 PM UTC

   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..

5. monitoring Jun 24, 2025, 09:20 AM UTC

   The issue affecting connectivity via Cogent on June 20th has been fully resolved. We have received the following RFO (Reason for Outage) from Cogent: > _“Customers in or transiting Slough may have experienced severe service degradation on June 20th between 12:18 and 13:32 GMT._ > > _During a routine configuration change on one of our core routers in Slough, unexpected behavior occurred resulting in entirely unexpected side effects._ > > _As soon as the issue was noticed, our IP Engineering department was involved to urgently resolve the issue._ > > _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._ > > _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.

Read the full incident report →

Started May 29, 2025, 09:51 AM UTC· resolved May 29, 2025, 11:49 AM UTC

1. identified May 29, 2025, 09:51 AM UTC

   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 'at risk'..

2. identified May 29, 2025, 11:01 AM UTC

   The fibre provider has identified the fault and are working on a resolution. We will update in due course once resolved..

3. resolved May 29, 2025, 11:49 AM UTC

   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..

Read the full incident report →

Started May 08, 2025, 02:11 PM UTC· resolved May 10, 2025, 08:36 PM UTC

1. identified May 08, 2025, 02:11 PM UTC

   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. .

2. identified May 08, 2025, 02:40 PM UTC

   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..

3. monitoring May 08, 2025, 03:14 PM UTC

   We are starting to see power return to the affected feed. We are monitoring this and liaising with the datacentre. We will update asap..

4. monitoring May 08, 2025, 05:33 PM UTC

   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..

5. monitoring May 09, 2025, 09:59 AM UTC

   We have received the following update from the Datacenter: "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." As full functionality has not been restored, we will continue to hold this incident open and post status updates here..

6. resolved May 10, 2025, 08:36 PM UTC

   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. "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.".

Read the full incident report →

Started Mar 11, 2025, 08:05 AM UTC· resolved Mar 11, 2025, 12:23 PM UTC

1. identified Mar 11, 2025, 08:05 AM UTC

   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..

2. resolved Mar 11, 2025, 12:23 PM UTC

   We are marking this as resolved now as we have had communication from our upstream that they have now brought back online our services..

Read the full incident report →