We have had a routing problem on the DSL network affecting customers on 78.32.x.x and 78.33.x.x ip address ranges. This was caused by some missing configuration leading to a single point of failure, we have now corrected the missing config and stability has returned.
Archive for May, 2009
Outage: Preston and Glasgow PoPs
Posted: Friday, May 29th, 2009 at 02:17 by Ming-Yu Hsieh
We are aware of problems that are affecting our Preston and Glasgow PoPs. This has been reported through to the carrier and they have advised us that there is a fiber break in the Manchester area. We apologise for the inconvenience that this will be causing for all users connected via these PoPs and will update as soon possible.
Outage: telehouse-east2.core.enta.net
Posted: Tuesday, May 26th, 2009 at 19:09 by Steve Lalonde
We had an unscheduled reboot on telehouse-east2.core.enta.net, the router is now back in service. We are investigating the cause.
Outage: BT Framestreams
Posted: Tuesday, May 26th, 2009 at 18:04 by Richard Partridge
We are currently experiencing issues on a small number of BT Framestream circuits. BT have been made aware of this case and they are currently investigating the possibility of a larger network problem. Further information will be made available shortly.
-
Richard Partridge says:
There is now an outage report available for this issue. It can be found here.
Planned Maintenance: redbus-mer3.core.enta.net
Posted: Thursday, May 21st, 2009 at 16:00 by Ming-Yu Hsieh
29th May 2009, 01.00 to 06.00
During the maintenance window above, the router redbus-mer3.core.enta.net will be replaced with a higher specification device during the maintenance window above. The expected downtime for the work is 1 hour, during which, customers who are directly connected to this device will be out of service. Any traffic that would normally be routed through this equipment will route via alternate paths. We apologise for any inconvenience this may cause.
-
Ming-Yu Hsieh says:
This maintenance work completed successfully, please report any issues via the usual support channels.
Planned Maintenance: redbus-sov3.core.enta.net
Posted: Thursday, May 21st, 2009 at 15:59 by Ming-Yu Hsieh
29th May 2009, 01.00 to 06.00
During the maintenance window above, the router redbus-sov3.core.enta.net will be replaced with a higher specification device during the maintenance window above. The expected downtime for the work is 1 hour, during which, customers who are directly connected to this device will be out of service. Any traffic that would normally be routed through this equipment will route via alternate paths. We apologise for any inconvenience this may cause.
-
This maintenance work completed successfully, please report any issues via the usual support channels.
Planned Maintenance: redbus-hex2.core.enta.net
Posted: Thursday, May 21st, 2009 at 15:45 by Ming-Yu Hsieh
29th May 2009, 01.00 to 06.00
During the maintenance window above, the router redbus-hex2.core.enta.net will be replaced with a higher specification device during the maintenance window above. The expected downtime for the work is 1 hour, during which, customers who are directly connected to this device will be out of service. Any traffic that would normally be routed through this equipment will route via alternate paths. We apologise for any inconvenience this may cause.
-
This maintenance work completed successfully, please report any issues via the usual support channels.
Planned Maintenance: telecity-hex.core.enta.net
Posted: Thursday, May 21st, 2009 at 15:41 by Ming-Yu Hsieh
28th May 2009, 01.00 to 06.00
During the maintenance window above, the router telecity-hex.core.enta.net will be replaced with a higher specification device during the maintenance window above. The expected downtime for the work is 1 hour, during which, customers who are directly connected to this device will be out of service. Any traffic that would normally be routed through this equipment will route via alternate paths. We apologise for any inconvenience this may cause.
-
This maintenance work completed successfully, please report any issues via the usual support channels.
Planned Maintenance: telehouse-east2.core.enta.net
Posted: Thursday, May 21st, 2009 at 15:22 by Ming-Yu Hsieh
28th May 2009, 01.00 to 06.00
During the maintenance window above, the IOS on the telehouse-east2.core router will be upgraded to resolve some configuration issues. This software upgrade will require a reboot of the router which should take less than 30 minutes to complete, during which all directly connected customers will be out of service. Any traffic that would normally be routed through this equipment will route via alternate paths.
-
This maintenance work was canceled due to the unscheduled reboot on 26th May, as IOS and configuration was in place, the reboot upgraded the IOS at the same time.
Planned Maintenance: Global Switch Frame Circuits
Posted: Thursday, May 21st, 2009 at 15:19 by Ming-Yu Hsieh
27th May 2009 23:00 – 28th May 06:00
During the above window we will be performing router upgrades within Global Switch that will require all 2Mbps Framstream circuits supplied via this location to be out of service for a small period. Our teams will be calling all affected customers individually to advise and naturally we apologise for any inconvenience that this work will cause. This work is rescheduled from 15th May.
-
This maintenance work completed successfully, please report any issues via the usual support channels.
Latest from our carrier is engineers are on-site and splicing work is ongoing.
There is currently no ETR. Further updates will follow.
Latest update: 150 metres of fibre was damaged and has been replaced, splicing work is still ongoing.
There is currently no ETR. Further updates will follow.
Latest: Splicing on joint 1 is almost finished, splice team will then move on to joints 2 and 3.
Still no ETR, but have been told it usually takes 2 hours to re splice an entire joint with this many fibres and also that the work is progressing faster than expected.
Service has just been restored, it is not known yet if this will be stable.
There is now an outage report available for this issue. It can be found here.