Issue affecting Bytemark Cloud Server VM's currently in Manchester DC

Expected resolution: 22 Dec 2017, 13:45 UTC
Return to issues
Issue status: Resolved Date:

2 Jan 2018
14:02 UTC

Posted by:

Matthew Bloch

The RFO is now posted on our customer forum, where I'm happy to answer questions

Issue status: Resolved Date:

29 Dec 2017
10:05 UTC

Posted by:

Matthew Bloch

We've not forgotten about this RFO and are gathering the details today. I'll update this issue when it's published.

Issue status: Resolved Date:

22 Dec 2017
14:25 UTC

Posted by:

Doug Targett

Further to the resolution there will be a write-up this evening by one of our directors Matthew Bloch. This will help understand some of the detail of what has happened in these two unexpected outages.

Thank you

Issue status: Resolved Date:

22 Dec 2017
13:48 UTC

Posted by:

Doug Targett

We have restarted the service on all of the tails that allows the heads to connect to the disks.

If you are still experiencing problems please do contact support.

Please accept our apologies for these problems.

Issue status: Investigating Date:

22 Dec 2017
13:29 UTC

Posted by:

Doug Targett

We are currently working through the tails restarting the processes that allow the heads (CPU and CPU) to connect to the tails (network storage device) Once we have processed these restarts we expect service to resume.

Next update 13:45

Issue status: Investigating Date:

22 Dec 2017
13:14 UTC

Posted by:

Ian Eiloart

We believe this is a recurrence of the similar issue that we had yesterday. We'll be able to fix the problem faster this time, and get more evidence on the root cause.

Next update 13:30

Issue status: Investigating Date:

22 Dec 2017
13:04 UTC

Posted by:

Doug Targett

We identified an issue at 12.57 that has similar symptoms to an outage yesterday. We are currently looking at what the causes are and there will be more information to follow.

Next update at 13.15

Return to issues

Issue still not addressed? Please contact support.