Fido.Net Status Updates

Category: Latest

Details of latest changes / status / updates

web-11 issues

We became aware of issues with web-11 at approximately 17:30 this evening We believe there are one or more sites on the server which are currently on the receiving end of a DDoS attack. Engineers are working to address the problems and will have more of an update in a few hours.  Initial attempts to…

DNS Server Upgrades

As part of our continued programme of improvements we have updated the DNS server farm this evening during the Wednesday maintenance window.   The updates bring a number of security patches as well as the long awaited DNSSEC support customers have been asking for.   Further to this we have also enabled additional servers in…

Issues affecting ported numbers

We have been made aware of an issue with our upstream provider and routing issues affecting some ported numbers within the BT core network.   BT are working on this issue currently and hope to have the problem addressed shortly   Please accept our apologies for any inconvenience caused by this matter which is outside…

Updated SSL Certificates

We are currently busy updating our SSL certificates across all of our servers as the old wildcard certificates for *.fido.net and *.server.fido.net are due to expire on Friday. As such you may receive an SSL certificate warning if you were trusting the old certificate on your domain, or if you connect to a hosts alias…

lon-1 routing issue

At approx 00:27 this morning during a routine configuration update, an issue arose with one of our JunOS routers which resulted in a routing engine becoming unstable. Normal service was resumed at 00:48 We are collecting debug information to submit to Juniper as part of a JTAC incident in relation to the issue at this…

ALL Clear – Extended Maintenance Complete

The extended maintenance window to perform Juniper firmware upgrades on the core network has been completed Maintenance started at 23:00 and was completed by 02:45 Disruption was kept to a minimum, however customers with single feeds will have been affected – primarily between 01:55 and 02:30 during which time we encountered an issue with one…