Fido.Net Status Updates

Author: jon

ALL Clear: Telehouse <-> DBC

Following on from an emergency hardware replacement at THN connections to our DBC site should now be live again.   Customers may have noticed partial or total routing loss for a period during this emergency maintenance, and we are investigating why the redundant links were not as effective as they should have been, although we…

AT RISK: Telehouse to DBC Link

Engineers are currently investigating a problem with the fabric between Telehouse and our DBC site in London Docklands.   There appears to be a fault with one of the redundant switches, and this has been removed temporarily while engineers investigate further.  During this emergency maintenance the network is at risk should the redundant connection also…

SMTP/TLS Authentication issues

We are aware of some reports of issues authenticating using TLS over SMTP since the installation of new SSL certificates on our mail servers overnight.   We have taken this issue up with Comodo as a matter of urgency (the reason appears to be a problem verifying the trust chain) and we hope to have…

SSL Certificate Updates

We have today updated the Wildcard SSL certificates on servers in the fido.net and server.fido.net domains As a result you may be prompted to confirm a change in the recorded SSL certificate you have stored in your caches.  This is entirely normal and you should accept the new certificate if prompted.   If we have…

MBORC Update 27.12.2012

MBORC declaration and Service update  This MBORC declaration and Service update is issued as a special alert to all Openreach customers due to the continuing severe weather experienced over the past few days  On 24 December 2012, we declared MBORC for repair activities on 12 areas of the UK in addition to 6 areas already declared…

PCS6 Cloud 6 Reboot

We are investigating the cause of a service failure with the new PCS6 Cloud 6 Front end.   A number of VMs have shut down, and we are investigating the cause of the failure currently Update – the problem has been identified and resolved.  This issue should not happen again.   Background: 09:45 an auto…