Last 10 minor outages posts, sorted by last updated
Order posts by limited to posts

MINOR Closed Web IRC
AFFECTED
Web IRC
STARTED
Sep 28, 09:15 AM (1 day ago)
CLOSED
Sep 28, 04:00 PM (22½ hours ago)
DESCRIPTION
Our web-based IRC client (webirc.aa.net.uk), purposefully hosted by a third party, is experiencing packet loss. This will be affecting those customers how join our IRC channel by this website.
Resolution:

MINOR Closed b.gormless
AFFECTED
b.gormless
STARTED
Sep 25, 09:53 AM (4 days ago)
CLOSED
Sep 25, 10:02 AM (4 days ago)
DESCRIPTION
At 09:53 one of our LNSs 'B.Gormless' crashed, causing some customers to drop and reconnect a few moments later. The cause is being investigated.
Resolution:

MINOR Closed BT DSL
AFFECTED
BT DSL
STARTED
Sep 19, 01:43 PM (10 days ago)
CLOSED
Sep 19, 05:32 PM (9¾ days ago)
DESCRIPTION
Our monitoring has picked up a large number of BT circuits disconnected at 13:43. We're investigating
Resolution: BT say: Fault proved to a fibre bend at Mile End TE by PTO. Cleared at 17:25.

MINOR Closed V.Gormless
AFFECTED
V.Gormless
STARTED
Sep 04, 07:30 PM (24¾ days ago)
CLOSED
Sep 04, 09:33 PM (24½ days ago)
DESCRIPTION
Customer on our 'V.Gormless' LNS have being seeing very slow speeds since 7:30pm this evening. This is affecting about 5% of our customers.
Resolution: Customers have been moved off the affected router and we'll continue our investigation in to the cause tomorrow.

...A problem has been identified with the traffic shaping code in the latest FireBrick Software. A temporary solution by way of configuration change has been applied to our routers, and a software update will be applied in due course.


MINOR Closed Routing
AFFECTED
Routing
STARTED
Aug 10, 12:20 PM (1½ months ago)
CLOSED
Aug 10, 12:45 PM (1½ months ago)
DESCRIPTION
At around 12:20 there was a problem on the LINX peering LAN (a peering exchange used by most of the UK internet). This affected one of our connections to LINX (in Telehouse) and caused routing to some destinations to break for a couple of minutes.
Resolution: This was caused by some of the network switches in LINX's network rebooting. However, the cause of the rebooting is yet to be discovered. This affected many other internet providers connected to the LINX exchange point.

MINOR Closed Webmail problems
AFFECTED
Webmail problems
STARTED
Aug 08, 08:38 AM (1¾ months ago)
CLOSED
Aug 08, 09:06 AM (1¾ months ago)
DESCRIPTION
We are investigating a problem affect customers webmail access. Engineers are working on this and we'll provide an update shortly.
Resolution:

MINOR Closed DSL
AFFECTED
DSL
STARTED
Aug 02, 08:30 PM (1¾ months ago)
CLOSED
Aug 02, 08:38 PM (1¾ months ago)
DESCRIPTION
Customers on the 'Z.Witless' LNS saw their drop and reconnect at around 20:30 this evening. This was caused by the LNS restarting due to a 'watchdog'.
Resolution: We believe the cause of this has been resolved in a later firmware, and we will apply this as soon as we can. We do apologise for the loss of service this caused those customers.

MINOR Closed Database
AFFECTED
Database
STARTED
Jul 31, 04:00 PM (1¾ months ago)
CLOSED
Aug 01, 09:00 AM (2 months ago)
DESCRIPTION
Some Control page changes are being delayed in becoming 'live', this is due to a delay in our database replication at the moment. This means that some changes, eg changing email/VoIP passwords won't be updated right away.
Resolution: This was resolved

MINOR Closed SMS
AFFECTED
SMS
STARTED
Aug 01, 05:00 PM (1¾ months ago)
CLOSED
Aug 02, 01:30 PM (1¾ months ago)
DESCRIPTION
We have had reports of SMS not being received on our 074411 range of numbers from some carriers. This is being investigated.
Resolution:

MINOR Closed DSL
AFFECTED
DSL
STARTED
Jul 17, 12:55 PM (2¼ months ago)
CLOSED
Jul 17, 01:27 PM (2¼ months ago)
DESCRIPTION
Customers on one of our LNSs, z.witless, dropped and reconnected at around 1PM. This was due to the LNS crashing and restarting. Cause is being investigated.
Resolution: The CPU on z.witless hung and the watchdog rebooted the device causing customers connected to it to drop and reconnect - causing an outage for a couple of minutes. We suspect the cause of the CPU problem is something rare (we've not seen this in production before) and one that the FireBrick developers are already working on to understand.