There is a major issue with broadband lines at present.
We are investigating this now.
Thursday, June 26, 2008
Subscribe to:
Post Comments (Atom)
Subscribe To
Posts
Comments
Archives
-
►
2009
(368)
-
►
November
(27)
- [closed] 07:22 21CN-BRAS-RED1-L-STE
- [info] L-WAT 21CN
- [info] Todays overnight BT screw ups
- [closed] Faraday node failure
- [info] 03:12 21CN-BRAS-RED1-PE
- [info] 13:44 21CN-BRAS-RED2-MQD
- [info] 00:18 21CN-BRAS-RED1-L-STE
- [info] New BT planned work
- [open] Packet loss on Canterbury Exchange
- [open] Packet loss on Upton Park Exchange
- [Closed] VoIP Problems
- [info] 00:21 21CN-BRAS-RED1-MQD
- [info] 18:00 21CN-BRAS-RED2-L-WAT
- [info] 02:00 21CN-BRAS-RED2-BM-TH
- [info] Ongoing BRAS flapping issues
- [Open] RoundCube Webmail - Upgrades
- [closed] 09:08 21CN-BRAS-RED1-L-STE
- [info] BT RADIUS issues (at risk)
- [info] BT Planned Engineering Works (PEWs)
- [info] 01:31 21CN-BRAS-RED1-GI-B
- [info] 00:03 21CN-BRAS-RED1-L-FAR
- [info] IDN
- [close] 21CN-BRAS-RED2-CF-C
- [closed] 21CN-BRAS-RED2-L-WAT
- [info] All is well
- [info] Units billing trial
- [info] 21CN-BRAS-RED1-L-WAT
-
►
October
(72)
- [closed] Major issue (not BT)
- [info] New diagnostic feature
- [info] Test LNS
- [info] Why so many outages reports on here
- [info] 08:27 21CN-BRAS-RED3-BM-TH
- [info] 21CN-BRAS-RED1-BS
- [info] ESR10-MILTONKEYNES4
- [info] 21CN-BRAS-RED3-L-NWS
- [closed] BE line issues (High Latency)
- [info] ESR13-BIRMINGHAM6
- [info] 21CN-BRAS-RED2-SL
- [reminder] maintenance work
- [closed] 21CN-BRAS-RED1-BS
- [info] Working with BT
- [info] L-WAT
- [info] 21CN-BRAS-RED2-SL
- [closed] 20CN via READING BRASs
- [closed] 21CN-BRAS-RED2-SL
- [info] End of an era (again)
- [info] L-WAT
- [info] L-WAT
- [close] 21CN-BRAS-RED1-GI-B
- [info] New DNS
-
►
November
(27)
BT Planned Work
Latest BT Incident Reports
4 Follow-up Messages (Posted by AAISP Staff):
Lines are coming back up now.
This appears to be an issue with the links to BT, which we are investigating.
Most customers back on line now.
We restarted careless so graphs have been lost.
Logs suggest it was some sort of attack on careless itself. We are trying to track the source,
Post a Comment