cr1.thn was restored to service on the evening of the 28th September and has remained stable since. All services have been closely monitored and have been operating normally.
The cause of the MTU issue that plagued broadband users connected via lns0.vlt after the THN interconnect was lost was identified and we believe is now resolved.
We apologise for the inconvenience caused.
All services have now been re-routed in one way or another
Work continues to replace cr1.thn and subsequently to identify the cause of the MTU issue for lns0.vlt so that it can be returned to service, but at this time nobody should have a loss of service - if you are experiencing disruption please email support
There was an MTU issue identified that was affecting broadband users connected via lns0.vlt - we have for the time being withdrawn this LNS from service.
There has been a total loss of the route processor in cr1.thn and a replacement is being organised, and any services that can be re-routed around cr1.thn in the meantime are being re-routed.
cr1.thn appears to have vanished without a trace
An engineer is on their way to investigate the rack
This will cause a loss of any services directly connected to cr1.thn, causes a loss of resilience to broadband and other layer2/3 services
Broadband circuits connected via Telehouse North will have suffered disruption followed by a reconnect over the other interconnect.
Apologies for the inconvenience caused - more as we have it
We’ll find your subscription and send you a link to login to manage your preferences.
We’ve found your existing subscription and have emailed you a secure link to manage your preferences.
We’ll use your email to save your preferences so you can update them later.
Subscribe to other services using the bell icon on the subscribe button on the status page.
You’ll no long receive any status updates from Netcalibre Service Status, are you sure?
{{ error }}
We’ll no longer send you any status updates about Netcalibre Service Status.