Fido.Net Status Updates

Category: Latest

Details of latest changes / status / updates

LINX Juniper LAN Broadcast Storms

The LINX (London Internet Exchange) Juniper peering LAN is currently experiencing high volumes of broadcast traffic.   As a precaution, we have disabled connections to the LINX Juniper LAN in order to restore stability We are awaiting an update from LINX as to the cause of the broadcasts and their plans to resolve the situation

AT RISK: Bank Holiday Maintenance 23-25th May 2015

We are planning a full range of works over the Bank Holiday weekend which will result in upgraded capacity and improved network performance.   During the maintenance window a number of segments of the network will be upgraded which may result in brief periods where services should be considered “At Risk” when redundant paths are…

AT RISK – Fibre issue in THN <-> THE

08:10 We have identified an issue with one of the fibre connections between Telehouse North and Telehouse East Engineers are currently on site resolving the issue During this time the resilient ring is at risk and routing may be briefly affected as the ring topology resets   08:30 Update the break has been addressed and…

NTP Vulnerability

CERT have published an advisory in relation to a vulnerability in the ntpd daemon https://ics-cert.us-cert.gov/advisories/ICSA-14-353-01A   As a precaution, we have already forced an update on customer routers which we manage where a new firmware update is already available. We are also planning on updating our core routers over the next few days, between midnight…

Network issues 18.12.2014

We have identified issues with one of our Juniper core routers / BGP edge routers this morning   Initial attempts to rectify the issue by engineers have been unsuccessful and an emergency reboot has been initiated to attempt to resolve the connectivity issues through this node.   We will update this notification in more detail once…

RFO – London 2 connection issues 25.11.2014 AM

At approximately 08:30 this morning one of our trusted peers started to experience network issues which translated as sending increased prefixes via our BGP interconnect (Border Gateway Protocol)  (500,000 instead of the usual 10,000 routes).   Our automated systems detected this and shut the sessions down, however owing to a configuration timeout issue the sessions…