Problem description
Added on: 12/09/2008 @ 12:01
We have been made aware that there is an issue with BIRMINGHAM ATM NODE 10025 and this is affecting many circuits. The complete list of dialing codes affected are as follows:
01142, 01159, 01162, 01173, 01179, 01189, 01202, 01205, 012120, 012121, 012123, 012124, 012131, 012133, 012135, 012136, 012142, 012144, 012145, 012146, 012147, 012148, 012150, 012152, 012155, 012158, 012160, 012162, 012163, 012164, 012169, 012170, 012173, 012174, 01223, 01225, 01226, 01229, 01234, 01235, 01242, 01244, 01246, 01248, 01252, 01254, 01260, 01267, 01269, 01270, 01271, 01274, 01275, 01276, 01278, 01279, 01280, 01283, 01295, 01296, 01303, 01305, 01308, 01332, 01344, 01352, 01375, 01384, 01386, 01400, 01430, 01432, 01437, 01442, 01443, 01446, 01454, 01455, 01458, 01473, 01479, 01480, 01483, 01484, 01493, 01494, 01495, 01497, 01501, 01502, 015153, 015170, 01522, 01527, 01530, 01531, 01542, 01543, 01562, 01564, 01565, 01566, 01597, 01604, 016120, 016122, 016123, 016137, 016147, 016148, 016164, 016165, 016179, 016183, 016186, 016187, 01622, 01625, 01629, 01633, 01636, 01639, 01664, 01675, 01685, 01691, 01698, 01704, 01709, 01722, 01724, 01727, 01733, 01740, 01745, 01746, 01752, 01753, 01754, 01756, 01761, 01766, 01769, 01778, 01782, 01785, 01788, 01792, 01803, 01823, 01840, 01843, 01845, 01865, 01873, 01895, 01902, 01904, 01905, 01908, 01924, 01925, 01934, 01952, 01970, 01978, 01993, 01995, 0203229, 0207513, 0207718, 0208427, 0208466, 0208501, 0208561, 0208606, 0208658, 0208848, 0208864, 0208897, 0208959, 0247625, 0247644, 0247659, 0247660, 0247668, 0282564, 0283832, 0283834, 0287035, 0287136, 0288225, 0289086, 0289145, 0292022, 0292023, 0292034, 0292037, 0292055, 0292059, 0292086, 0292088, LLCL0, LLCM0, LLEA0, LLEM0, LLLC0, LLLN0, LLLS0, LLLV0, LLLW0, LLMR0, LLMY0, LLND0, LLNE0, LLSD0, LLSL0, LLSM0, LLSS0, LLST0, LLSW0, LLTH0, LLWE0, LLWM0, LLWN0
BT have given us an Anticipated Clear Time of 12/09/2008 13:08. This will be affecting customers who cannot connect to the Internet.
If you were logged in to the portal, you could associate your username with this problem.
