This is the Blacknight hosting and domain name registration offsite maintenance / technical blog.
If you are an existing client of Blacknight we recommend you subscribe to the feed to get the latest service updates: 
Subscribe to this blog’s feed or subscribe to the email updates
You can also find us on Twitter and Facebook
Want our latest domain name and website hosting offers? Check here.
The server pemlinng038 will be taken offline at approx 9pm to perform scheduled maintenance. It is estimated that this maintenance should be for no more than 15-30 minutes. We will update this post if there are any delays encountered during the process.
Four shared MySQL database servers are out of service at the moment due to an unexpected issue. We’re working to restore service urgently. Servers affected below: pemmysql29-bk3 pemmysql30-bk3 pemmysql31-bk3 pemmysql32-bk3 Updates to follow… Update @ 14:15 – all four MySQL nodes are back in service.
The following MySQL servers will be briefly taken offline to performance scheduled updates: pemmysql84.blacknight.com pemmysql85.blacknight.com pemmysql86.blacknight.com pemmysqlng015.blacknight.com pemmysqlng016.blacknight.com pemmysqlng017.blacknight.com pemmysqlng018.blacknight.com pemmysqlng019.blacknight.com pemmysqlng020.blacknight.com pemmysqlng021.blacknight.com pemmysqlng022.blacknight.com pemmysqlng023.blacknight.com pemmysqlng024.blacknight.com pemmysqlng025.blacknight.com pemmysqlng026.blacknight.com pemmysqlng027.blacknight.com pemmysqlng028.blacknight.com pemmysqlng029.blacknight.com pemmysqlng030.blacknight.com pemmysqlng031.blacknight.com pemmysqlng032.blacknight.com pemmysqlng033.blacknight.com pemmysqlng034.blacknight.com Servers should be offline for no more than a few minutes each.
We are currently experiencing issues on one of our shared hosting nodes Pemlinng074 (78.153.210.20) – Engineers are investigating the issue and we will update this post as soon as we have more information. To check if your website is affected – please use https://check.blacknight.tech/ Update : 14:48 We were unable to resolve the issue […]