At approximately 18:15 BST whilst engineers were working in one of our racks in IP House a power cable feeding one of our core routers became dislodged from the distribution board.
Category: CoLocation Centres
Bulletin Board, CoLocation Centres, Hosting, Latest, London 1 (Hex), London 2 (TFM120 - Telehouse West), London 3 (TFM3 - Telehouse North), Planned Maintenance
Planned Maintenance – 31.07.08
by jon • • 0 Comments
Window Commences: 2008-07-31 23:00:00 GMT (UTC + 0) Window Concludes: 2008-08-01 06:00:00 GMT (UTC + 0) During the above window the fibre links between each of our 3 UK sites will be taken off line for approximately 10 minutes at a time to perform maintenance and upgrades. Whilst these upgrades are performed traffic between sites…
CoLocation Centres, London 1 (Hex), London 2 (TFM120 - Telehouse West), London 3 (TFM3 - Telehouse North), Planned Maintenance
Router Upgrades
by jon • • 0 Comments
31st May – Update Owing to certain issues with AS community handling in the maintenance release installed yesterday we are planning a further “emergency” maintenance upgrade this evening with an additional patch which resolves issues with community handling in this release. We anticipate a brief outage at 11pm to transit routes via Tiscali and NTT…
Bulletin Board, Hosting, Latest, London 3 (TFM3 - Telehouse North)
Outage Report
by jon • • 1 Comment
At approximately 03:10 this morning we experienced what appears to be the culmination of a memory leak on one of our core routers which caused the Cisco Express Forwarding (CEF) table to crash on said router. The problem was cleared by 06:10 this morning however there would have been up to a 3 hour window…
CoLocation Centres, London 2 (TFM120 - Telehouse West), Planned Maintenance
Switch Upgrades (continued)
by jon • • 0 Comments
There will be a brief outage at 2am Friday morning while we update the firmware on one of our core switches at London-2 (IPH). This outage should last for no more than 5 minutes whilst the switch reboots. Please address any queries to support@fido.net
Bulletin Board, CoLocation Centres, Latest, London 1 (Hex), Planned Maintenance
Switch Upgrades
by jon • • 1 Comment
There will be a brief outage at 2am Thursday morning while we update the firmware on one of our core switches at London-1 (Hex). This outage should last for no more than 5 minutes whilst the switch reboots. Please address any queries to support@fido.net
CoLocation Centres, London 1 (Hex), London 2 (TFM120 - Telehouse West), London 3 (TFM3 - Telehouse North), Planned Maintenance
Router Maintenance
by jon • • 0 Comments
We will be performing routine maintenance on our border routers Sunday evening which will result in a reboot / reload of sessions on each router. The impact of this should be minimal as you have connections to redundant routers. The plan is to reboot Hex at approximately 11pm IP House at midnight TeleHouse North at…
CoLocation Centres, London 1 (Hex), Planned Maintenance
Backbone Maintenance
by jon • • 1 Comment
AT RISK NOTIFICATION:: London Ring. This at risk period is not expected to be service affecting. At risk Window Commences: 2007-02-22 00:00:00 GMT (UTC + 0) At risk Window Concludes: 2007-02-22 02:00:00 GMT (UTC + 0) Reason for notification: To increase port capacity to meet customer demand by addition of two 2x10G backbone switches at…
CoLocation Centres, Latest
London 3 Now Live
by jon • • 0 Comments
We are pleased to announce that earlier this week we commissioned London-3 at Telehouse North. This site is to be known as London 3 (THN-TFM3) and gives us access to an unprecedented number of additional peers / data carriers going forwards which should enable us to grow our network and peering relationships considerably over the…
Bulletin Board, CoLocation Centres, Hosting, Latest, London 1 (Hex), London 2 (TFM120 - Telehouse West)
Routing Problems
by jon • • 0 Comments
Following reports of packet loss and abnormal ping responses from certain parts of our network, we began investigating a switch configuration error earlier today. Whilst reconfiguring the switch to overcome the reported errors a change to the spanning tree configuration caused a number of routing anomalies which started at roughly 13:37. We worked quickly to…