Issue with tail13 and tail15

Expected resolution: 24 Apr 2018, 08:30 UTC
Return to issues
Issue status: Resolved Date:

24 Apr 2018
08:17 UTC

Posted by:

Ian Chilton

The affected pool on tail13 has been emptied and tail15 has returned after a short interruption to service.

We're working hard to try and track down the cause to these sudden tail problems.

Issue status: Monitoring Date:

24 Apr 2018
07:50 UTC

Posted by:

Andrew Ladlow

We've identified the issue and begun to migrate discs away from both affected tails, so this should mean that your Cloud Servers are performing normally again.

We'll continue to monitor both tails throughout the morning to ensure full service has been restored.

If you think this problem is still impacting your services at Bytemark, please do get in touch.

Expected resolution time updated: 24 Apr 2018, 08:30 UTC

Issue status: Investigating Date:

24 Apr 2018
07:16 UTC

Posted by:

Andrew Ladlow

We've been alerted to an unexpected outage of tail13 and tail15 at approximately 08:10AM GMT+1.

A tail is one of the physical boxes that forms part of our Cloud infrastructure. Some of your Cloud Servers will have discs running on this hardware. If you've got an affected Cloud Server, you may notice it is unresponsive or offline.

Sorry about this! We've identified the problem and working to restore full service as soon as possible. We'll post updates here as soon as they're available.

If you're experiencing any problems with your services at Bytemark that you think might be related, please do get in touch.

Expected resolution time updated: 24 Apr 2018, 08:00 UTC

Return to issues

Issue still not addressed? Please contact support.