Archive for the ‘Incidents’ Category

Incident: Bristol

Posted: Thursday, July 12th, 2018 at 21:53 by Mark Yardley

We have just experienced a brief disruption to service at our Bristol PoP. All services should now be restored and engineers are continuing to investigate the underlying cause. We apologise for any inconvenience caused.

Incident: Nottingham

Posted: Friday, July 6th, 2018 at 11:18 by Mark Yardley

We have experienced a brief loss of connectivity to our Nottingham PoP. Most services have now been restored. Initial investigation suggests a loss of power. Engineers are currently investigating and liaising with our suppliers.

Incident: Columbo

Posted: Friday, July 6th, 2018 at 08:37 by Mark Yardley

We are currently experiencing a loss of connectivity to our Columbo PoP. Engineers are investigating and updates will be provided when available.

  1. Mark Yardley says:

    Connectivity has now been restored and initial investigation suggests this was caused by a loss of power in this location. Engineers are continuing to investigate and liaise with our suppliers. We apologise for any inconvenience caused.

Incident: Columbo BT Openreach Circuits

Posted: Thursday, July 5th, 2018 at 09:28 by Mark Yardley

We are aware of a brief interruption to service for multiple BT Openreach circuits delivered to our Columbo PoP. Initial investigation suggests this was due to a loss of power to one of our cabinets. Service has been restored and engineers are investigating the loss of service with our supplier. We apologise for any inconvenience caused.

Incident: telehouse-east2.edge

Posted: Wednesday, June 27th, 2018 at 09:42 by Mark Yardley

We have experienced an unexpected reload of one of our edge devices in Telehouse which affected a number of Virgin Media circuits. Connectivity to these services is now restored however engineers are continuing to investigate the cause. We apologise for any inconvenience.

Incident: Talktalk Circuits

Posted: Wednesday, June 27th, 2018 at 09:10 by Jamie Smith

We have experienced a brief loss of service to a number of TalkTalk circuits  Initial diagnostics indicate the circuits are related to multiple TalkTalk handoffs. Engineers are investigating and engaging with our supplier.

The circuits in question are now showing as back up, further updates to be provided once the supplier has provided us with a response.

  1. Jordan Coleman says:

    Our supplier has confirmed that a fibre break on a third party circuit earlier today caused a brief disruption to services when traffic failed over onto alternative routes. Engineers are working to resolve this. Further updates will be provided when available.

Incident: BT Wholesale Circuits

Posted: Monday, June 25th, 2018 at 11:03 by Mark Yardley

We are aware of an issue affecting a number of BT Wholesale leased line circuits. The issue has been raised with our suppliers for investigation. At the time of posting we are starting to see services restoring, however services should still be considered at risk. More information will be provided when available.

  1. David Brewis says:

    BT have identified an issue in the London Stepney Green exchange with a task raised for an engineer to attend and resolve today. We expect the next update at 17:00.

  2. Scott Morgan says:

    Our suppliers have attended site to investigate the issue.

    The engineer has conducted some preventative maintenance on the equipment and users may have seen another brief interruption to service during this work. However, we have not as yet been provided with a root cause for the previous disruption. We are continuing to escalate this with our supplier for investigation and RFO.

  3. Mark Yardley says:

    As part of ongoing investigation into this issue we are dispatching an engineer to perform pre-emptive maintenance on our equipment and to co-op with a BT Wholesale engineer. This work is scheduled for between 15:00 and 16:00 today. During the window services delivered via this supplier hand-off will experience a planned disruption to connectivity. We anticipate this should be no more than 10 minutes.

  4. Mark Yardley says:

    This work was completed successfully by our engineer in the previously mentioned window. However we are still experiencing intermittent problems with the hand-off. This issue is being escalated again with our supplier for further investigation. Updates to be provided when available.

  5. Gurinder Bansal says:

    Our suppliers have attended site and fixed a fibre break. Connectivity has been restored however services should still be considered at risk. We will continue to monitoring overnight and an update will be provided when available.

  6. Mark Yardley says:

    We have seen a recurrence of this issue again this morning. We are escalating the case further with our supplier. Updates will be provided once available.

  7. David Brewis says:

    With the recurrence of disruption to service, despite locating a suppliers faulty fibre last night, investigations continue to identify the cause. This has been further escalated in BT and we are currently still waiting on an update which will be provided as soon as it comes available.

  8. David Brewis says:

    Following hardware replacements and no further disruption experienced overnight we will continue to monitor service throughout today.

    Should a repeat of disruptions continue, further work involving BT and their vendors will be carried out moving service to new a configuration.

  9. David Brewis says:

    We continue to monitor the status of connections and observe no further drops at the exchange since 16:44 on 27th June 2018.

    Entanet will continue to monitor for an extended period whilst working with the supplier to ensure service returns to normal operation.

  10. Jamie Smith says:

    We have seen a recurrence of this again this morning. This will be re-escalated with out supplier Updates to follow once available

  11. Scott Morgan says:

    Our suppliers have advised that an engineer is currently onsite as part of this major service incident. Spare parts should be with the engineer shortly so that hardware changes can be made to help rectify the issue.

    We will update further once we have received confirmation that this work has been carried out.

  12. Scott Morgan says:

    We have received confirmation from our suppliers that a suspected faulty line card has now been replaced.

    We apologise for any inconvenience caused by this incident and we will continue to monitor.

    Please consider this as still at risk, until further monitoring allows us absolute confirmation that this is now stable.

Incident: Milton Keynes Broadband

Posted: Thursday, June 21st, 2018 at 11:16 by David Brewis

We have experienced an issue with our DSL platform where broadband users in Milton Keynes experienced slow speeds with packet loss.

Whilst normal service has now been restored we reaching out to the supplier to investigate and understand cause.

  1. David Brewis says:

    Our suppliers continue to investigate, and we expect a response within 10 working days. Please find an interim report here.

Incident: nottingham.core

Posted: Sunday, June 3rd, 2018 at 11:17 by Mark Yardley

We have experienced an unscheduled reload of our Nottingham core router. All directly attached services will have experienced a brief interruption. Initial investigation suggests this was due to loss of power in the location and engineers are investigating further with our co-location provider. All services are now restored and we apologise for any inconvenience caused.

Incident: Talk Talk Circuits

Posted: Friday, June 1st, 2018 at 13:59 by Adam Heath

We are aware that a number of Talk Talk circuits are currently experiencing a disruption to service.  Talk Talk have acknowledged an issue and are currently investigating.  We will provide further information when it becomes available.

  1. Adam Heath says:

    Talk Talk have confirmed that the disruption has been caused by core network circuit flaps connecting into their Milton Keynes core device. This is affecting circuits nationwide.

    Talk Talk have engineering resource investigating a root cause but are unable to provide us with an ERT at this time. We will continue to update upon receipt of further information.