Archive for January, 2008

news.enta.net

Posted: Wednesday, January 30th, 2008 at 17:55 by Neil Watson

We are currently aware that the news service supplied by news.enta.net is not functioning. Engineers are looking into the problem and will be restoring the service as soon as they possibly can. Further info as we receive it.

  1. Steve Lalonde says:

    news.enta.net is now working again.

Planned BT Maintenanace – Central 2

Posted: Tuesday, January 29th, 2008 at 15:07 by Neil Watson

Wednesday 13th February 2008 – 00.00hrs – 06.00hrs

BT have made us aware that they will be carrying out maintenance work that will affect Central 2 during the above maintenance window. The reason for this work is configuration changes, fibre changes and IOS upgrade. During the window above users may experience a period of downtime of up to 1 hour.

BT have assured us that the work will be completed as efficiently as possible and we, of course, apologise for the inconvenience that this may cause.

DSL Usage statistics

Posted: Monday, January 28th, 2008 at 15:09 by Neil Watson

We are currently aware that customers and Partners are unable to retrieve their usage data for their DSL circuits. This is due to a hardware failure which is preventing the information from being presented. We apologise for the inconvenience that this will be causing and wish to reassure you that the service will be resumed as soon as possible. Please note that the data on individual usage is still being collected during this period and all figures will reflect this usage.

Incident Report: telehouse-north0.core.enta.net

Posted: Thursday, January 24th, 2008 at 18:02 by Neil Watson

An incident report for the outage experienced on Tuesday 22nd January 2008 is now available below.

Incident Report – telehouse-north0.core.enta.net

Viper Maintenance

Posted: Thursday, January 24th, 2008 at 15:37 by Martyn Haynes

cpp1.viper.enta.net will be taken down for essential maintenance at 16:30 to address security and performance issues. We expect the viper to be down no longer than 15 minutes.

Emergency Maintenance: Birmingham POP

Posted: Wednesday, January 23rd, 2008 at 14:31 by Neil Watson

Thursday 24th January 2008 – 20.00hrs

We will performing emergency maintenance at our Birmingham POP tomorrow from 20.00hrs. Our audit following on from the Cambridge POP emergency maintenance has indicated a problem with the router in this location that has the potential for causing downtime if not corrected as soon as possible. We will therefore be replacing this router in this POP.

The work will impact all customers connected to the Birmingham POP with an outage of upto 2hrs, however it is expected that the downtime will be less than 30 minutes. We apologise for the inconvenience caused.

  1. Steve Lalonde says:

    This work is now complete, services were restored to normal within 15 minutes.

Planned Maintenance: Five London Sites

Posted: Wednesday, January 23rd, 2008 at 14:26 by Neil Watson

30th January 2008 – 00.00hrs – 06.00hrs

We will be replacing blades and performing software upgrades at the following sites:

  • Telehouse Metro
  • Telecity Hex 6&7
  • Telecity Hex 8&9
  • Telecity Sovereign House
  • Telecity Meridian Gate

The work will involve a period of downtime for all customers who are directly connected, although this is expected to be no greater than 1hr per site. Please note this will not affect our DSL Centrals, except for those customers that take an L2TP feed through one of the affected sites.

  1. Ming-Yu Hsieh says:

    This work is now complete.

Outage: telehouse-north0.core.enta.net

Posted: Tuesday, January 22nd, 2008 at 16:18 by Steve Lalonde

We have just had the above router reload unexpectedly, this has caused some routing instability for the last few minutes.

Engineers are investigating the cause.

  1. Steve Lalonde says:

    Initial investigations have not shown any clear indication of the cause for this reload, we are raising a tac case with Cisco.

Emergency Maintenance: Cambridge POP

Posted: Monday, January 21st, 2008 at 10:02 by Neil Watson

Monday 21st January 2008, 20.00hrs

We will performing emergency maintenance at our Cambridge POP tonight from 20.00hrs. Our system monitoring has indicated a problem with the router in this location that has the potential for causing downtime if not corrected as soon as possible. We will therefore be replacing this router in this POP.

The work will impact all customers connected to the Cambridge POP with an outage of upto 2hrs, however it is expected that the downtime will be less than 30 minutes. We apologise for the inconvenience and will be auditing other similar equipment to ensure that any potential downtime is kept to a minimum.

  1. Steve Lalonde says:

    This work is now complete

London to Manchester 10Gig Outage

Posted: Sunday, January 20th, 2008 at 09:53 by Steve Lalonde

Currently our London to Manchester 10Gig circuit is out of service for Maintenance, looks like no one spotted the notification 10 days ago. :(

Traffic is flowing over alternate paths and there is enough capacity to handle the traffic.

Here are the details of the work:-

Start Time: Sunday 20th January 2008, 08:00 GMT

End Time: Correction: Sunday 20th January 2008, 15:00 GMT

Estimated Impact:

Services could be affected for up to 7 hours. Services may suffer small outages during this window but should not be hard down for more than two hours.

Reason for Maintenance:

Excavation and repair damaged fibre duct that has become damaged due to building works in the location of the current duct.

Once the ducting has been repaired, a 2km section of fibre from the Bradley Stoke site will be externally spliced to a new splice enclosure on the Bradley Stoke Way. This will need to be pulled in and spliced.

  1. Steve Lalonde says:

    The circuit came back into service while I was posting the notification :)

    This is still at risk until 15:00 GMT today.

  2. Steve Lalonde says:

    Circuit is down again, I have moved some traffic that would normally use this link to take a path via London until the 10Gig is stable again.