Update 01:30: After investigating all possibilities including power, slot compatabilty and chassis capability, we re-inserted the card once again and powered the line cards up one by one. This brought the new 48 port copper gigabit line card online without issues this time. On investigation, the power available in the chassis remains at acceptable levels.

During the below maintenance, our Cisco 6506 chassis disabled power to all line cards. We re-enabled power and all has returned to normal. This would have affected all customers directly connected to this device and any interconnect customers going through Telehouse North.

We are continuing to invesitigate the cause of this.

Dear Customers,

Update April 7th 23:00: All traffic has now been moved back to this link. This issue has now been resolved.

Update April 7th 10:00: The link has performed without errors or further drops, and we will be moving all layer 2 traffic back over it at 11pm this evening.

Update April 5th 17:51: We have swapped over to the new fibre now and have returned IP traffic over it. We will monitor for 24 hours and bring all traffic back over this link in 48 hours, should the link remain stable over this course.

Update April 5th 17:10: We are preparing to swap over to the new fibre shortly.

Update April 5th 09:15: All ip traffic has been placed back on the link, however interconnect customers remain off this link while we perform further testing. Interconnect customers should still consider themselves at risk of a second fibre break on the London Docklands ring at this time.

We have seen an increasing error rate and port drops on one of our Fibre ports in the Docklands area after some internal work this morning in one of the datacentres by external contractors. We have closed this down as to avoid any further distruptions to customer traffic. All traffic would have been re-routed automatically around the ring. However, at this point, please consider yourselves to be AT RISK should a further fibre break occur.

We are working with the datacentre to find the cause of this and will issue a further update shortly.

Kind Regards
C4L Technical Team