Summary
NOC have identified Some Customers connected to Swadlincote , Burton on Trent , Barton under Needwood and Repton exchanges are experiencing total loss of service. This is due to CRQ000000066249 has overran. Affected exchange codes:EMSWADL , EMBURTO , EMBARTO , EMRPTON.
exchangecodeEMSWADL,EMBURTO,EMBARTO,EMRPTON
Latest Update Preliminary investigations are underway with our NOC engineers to determine the root cause of this network incident. At this stage we are unable to issue an ERT until our NOC engineers have completed further diagnostics. Â
Latest Update NOC have confirmed service has been restored to customers at Burton on Trent, Barton under Needwood and Repton exchanges as of approx. 06:09. Customers at Swadlincote exchange remain impacted. The IP Access and Access Ops teams are continuing work to bring the two MSANs back into service with support from an onsite field engineer following planned works CRQ000000066249. Â
Latest Update NOC have confirmed service has been restored to customers at Burton on Trent, Barton under Needwood and Repton exchanges as of approx. 06:09. Customers at Swadlincote exchange remain impacted. The IP Access and Access Ops teams are continuing work to bring the two MSANs back into service with support from an onsite field engineer following planned works CRQ000000066249. Â
Latest Update The IP Access and Access Ops teams have made a config change to bring the two MSANs back into service, post change checks are currently being completed to ensure service has been fully restored. Â
Technical / Suspected Root Cause NOC identified customers connected to Swadlincote, Burton on Trent, Barton under Needwood and Repton exchanges experienced total loss of service from 06:00 due to over running planned worked under CRQ000000066249. Service was restored to Burton on Trent, Barton under Needwood and Repton exchanges as of 06:09 however, Swadlincote exchange remained impacted. To restore service to Swadlincote IP Access and Access Ops teams made a config change to bring two MSANs back into service as of approx. 08:36. This incident will now be closed with any further root cause analysis being completed via the problem management process. Â