Wednesday, August 17, 2016

Broadband Incident Report : : YARPOLE MUX 001 : EMERGENCY PEW : Reference 41595 : Issue 1 :

--------------------------------------------------------------
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: 41595   Issue : 1  
  Detected Date: 17/08/2016   Detected Time: 10:52  
  Start Date: 17/08/2016   Start Time: 10:52  
  Anticipated Clear Date: 18/08/2016   Anticipated Clear Time: 06:00  
  Next Update Date: 18/08/2016   Next Update Time: 06:00  
     
  Incident Headline: : YARPOLE MUX 001 : EMERGENCY PEW  
     
  Incident Details: At the moment some of your Broadband End Users may be experiencing a loss of Broadband service.
FOR A FULL LIST OF affected circuits, please LOG INTO BBCR, navigate TO THE MSO Fault Search report AND enter THE MSO reference NUMBER above.
https://www.btwholesale.com/pages/static/Applications/Orders_and_Faults/Broadband_Customer_Reporting/index.htm
 
  Progress Details: Customer impact: Loss of Management has been identified from proactive monitoring on a DSL MUX in Yarpole exchange. The issue is not currently causing major service issues for customers and no fault reports have been received. There will be a 2-4 hour outage between 02:00 and 06:00 on 18th August 2016 while work is being carried out.

Current Situation: Emergency PEW for CP card to be replaced between 2am and 6am on 18/08/16. The next update will be at the commencement of the work.
 
  Dialling Codes Affected:
01568
 
     

--------------------------------------------------------------
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: