Tuesday, June 17, 2014

Broadband Incident Report : : MULTIPLE MUXES IN THE READING AREA : LOSS OF SERVICE : Reference 21802 : Issue 5 :

--------------------------------------------------------------
Incident Manager - Automatic Mailer.
*** PLEASE DO NOT REPLY TO THIS E-MAIL ***
--------------------------------------------------------------

  BT Wholesale - Broadband Incident Report  
     
  Please read the following incident report as it could have an impact on some of your end users  
     
  BT Incident Reference: 21802   Issue : 5  
  Detected Date: 17/06/2014   Detected Time: 11:23  
  Start Date: 17/06/2014   Start Time: 11:23  
  Anticipated Clear Date: 17/06/2014   Anticipated Clear Time: 18:30  
  Next Update Date: 17/06/2014   Next Update Time: 18:30  
     
  Incident Headline: : MULTIPLE MUXES IN THE READING AREA : LOSS OF SERVICE  
     
  Incident Details: At the moment some of your Broadband End Users may be experiencing a loss of Broadband service.


 
  Progress Details: A technical bridge is still ongoing with the engineers on site at Reading, Kingston, Wantage and Guildford, who are still investigating the root cause. They are currently performing a number of diagnostic tests with the technical support team and the vendor to prove the root cause. A Precision Testing Officer (PTO) has been requested for both Guilford, and Reading. One of the PTOs is en-route to Guildford with an ETA of 16:45. Spare hardware has also been ordered, and en-route to Swindon with an ETA of 17:12.  
  Dialling Codes Affected:
0136701380014540148901666
0167201720017220179401962
0239263
 
     

--------------------------------------------------------------
This message concerns an on-going incident. We have tried to make sure that the information is accurate at the time of publication but it may quickly become out of date as the incident progresses. You may use the information only to advise your customers of the progress of the incident. You must not re-publish the information in any form except as a service update on your customer website.

No comments: