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.
Lines have reconnected, we do apologise for the interruption of service for those affected.
Some lines have reconnected to the 'backup' LNS - y.witless, this won't be causing any problems for customers but they will be moved off overnight tonight back on to the main LNSs.
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.