34SP.com System Status History

Description

Update at 09:24:09(BST): We have been operating with IPv6 access available to our website & account pages thus far with zero reported problems. As a result, I believe that it is suitable to mark this (potential) outage as resolved.

Any customers having trouble accessing our website (or any site hosted by 34SP.com) should drop us an e-mail to discuss this.

---

Update at 09:20:15(BST): So far, so good!

---

Update at 22:06:39(BST): The AAAA records for IPv6 are now live.

---

Update at 21:35:19(BST): Added a slight correction.

---

Customers should be reminded that June 8th is 'World IPv6 Day': http://www.worldipv6day.org/

34SP.com are participating in IPv6 Day in any way that we can and will be activating IPv6 access to the following websites:

http://34sp.com
http://www.34sp.com
http://account.34sp.com

If you are experiencing any faults that you believe to be related to these actions, please be sure to visit http://test-ipv6.com and/or contact your ISP.

It is expected that the vast majority of customers will not notice the change at all. If all goes well, we hope to keep IPv6 access to our website as a permanent feature.

Start Time

7th June 2011, at 9:30PM

Description

Update at 21:26:03(BST): Gambit has been running well since this outage first occurred, therefore we are marking this update as resolved.

---

Update at 21:04:51(BST):
Gambit is back up and running and we are monitoring this machine.

---

Update at 20:28:51(BST): Gambit is currently rebooting.

---

The Personal hosting server, Gambit, is experiencing some difficulties with a few of its services. At this time we're still trying to resolve the issue.

Start Time

5th June 2011, at 8:04PM

Description

Update at 21:03:45(BST):
All appears to be well now. This outage is now marked as resolved.

---

The recent issues with xenserve12 have now been rectified.

The issue was brought about by abuse from a single customer, whom has acted rather irresponsibly. This user will be contacted in due course and made aware.

At this time we're running checks across all databases and repairs will be issued if anything is amiss.

34SP.com apologise for the obvious inconvenience caused by this outage.

Start Time

5th June 2011, at 5:54PM

Description

Update at 09:53:40(BST): The issue has now been resolved with this server.The issue with this server has now been resolved.

---

It has been brought to our attention that there seems to be an issue with our vps3 server.

This has been raised to the system administrators to investigate. We will update this page as soon as we have any more information.

Start Time

3rd June 2011, at 8:05AM

Description

Update at 21:04:17(BST):
All appears to be well since the change to the network. This means that this update will now be marked as resolved/closed.

---

Update at 23:46:43(BST):
Service-impacting work is now complete. All seems to be running well. We'll be monitoring this for a short period of time this evening, to ensure smooth running of the network.

---

Update at 23:02:06(BST):
Maintenance window beginning now. Customers will see some short outages of up to a few minutes at a time. We'll be doing our best to keep this to a minimum.

---

As a reminder to customers utilising services hosted within our Manchester facility, there is a scheduled maintenance window due to begin in approximately 30 minutes.

Updates will be made to this page periodically throughout the window.

Start Time

2nd June 2011, at 10:29PM

Description

Update at 09:59:17(BST): This issue was resolved as of the earlier update.

---

Update at 16:25:15(BST): We have suspended a single website that appears to have been causing trouble (i.e. unsecured software versions).

The customer involved has been contacted before but has not responded in good time. We have suspended this hosting and will again contact the customer, but touch-wood, Lothos is currently running well.

---

Update at 12:15:17(BST): Lothos back up and running once again, all file system checks completed happily, with only minor modifications. This should hopefully improve reliability. We'll continue to monitor lothos for now.

---

Update at 11:46:16(BST): Our logs show some potential disk based issues so we are running a check on the storage in this machine. During this check, all services will be unavailable.

---

Update at 09:50:53(BST): Lothos is still experiencing issues; we're working to get to the bottom of it.

---

Update at 09:26:25(BST): All services should now be operating once again upon Lothos. All databases have been checked and we will continue to monitor this machine for a short while.

---

Update at 08:53:41(BST): Despite attempts this morning, we're unable to access Lothos remotely and will need to enlist the aide of an on-site Engineer.

---

We are presently investigating an issue affecting all services on this server.

Start Time

31st May 2011, at 3:40AM

Description

Update at 09:27:00(BST): Server8 has been running well for some time now and as a result, this outage is now marked as resolved.

---

Update at 22:08:32(BST): The new RAM has been fitted and xenserve8 is now back up and running! We'll be keeping a close eye on this machine for the next few hours.

---

Update at 21:51:49(BST): New RAM has been located and this is being fitted.

We apologise for the continued setbacks leading to this continued outage and appreciate your patience in this matter.

---

Update at 20:28:58(BST): Further setbacks have been experienced: this is due to the wrong type of RAM being sought from spares. This is due to a mistake in our records and we're working to find a solution (ideally the correct RAM).

More updates as they come.

---

Update at 19:54:05(BST): We apologies for extended outage to this server, the Engineer is still working on the machine and we hope to have service returned shortly.

---

Update at 19:17:36(BST): An Engineer is on-site now and will be replacing the memory in xenserve8. This means that the machine will be offline for 5-10 minutes whilst the memory is replaced with spares.

---

Update at 18:19:36(BST): A substantial portion of the memory in this server has failed. We have an engineer en route to replace the memory and will update as soon as this has been done.

This server is currently showing some hardware errors. We are attempting to restore functionality as quickly as possible.

Start Time

26th May 2011, at 5:44PM

Description

Update at 08:48:46(BST): The issue has now been resolved with this server.Update at 08:48:42(BST): The engineers have now resolved the issue affecting the MySQL service so all aspects should be back up and running.

We have received reports of MySQL issues on the server which will be affecting Emails and any sites with database driven content.

Our engineers are working on the issue now and normal service should resume shortly.

Start Time

26th May 2011, at 8:28AM

Description

Update at 17:42:55(BST): All now seems well. This outage is now marked as resolved.

---

Update at 17:19:43(BST): There is quite a high load on the MySQL datbase at present (which is in itself, rising and falling). We're investigating the cause of this, which is most-likely to be as a result of rogue/un-optimised queries.

---

Update at 16:47:48(BST): The machine rebooted cleanly and we are working on ascertaining the cause of the fault.

We will be checking the consistency of all databases and monitoring from this point onwards.

---

Business8 appears to have suffered a kernel panic, we've restarted the machine via the power controllers and will be monitoring the machine as it reboots.

Start Time

20th May 2011, at 4:45PM

Description

Update at 15:46:31(BST): This outage is now marked as resolved.

---

Update at 09:47:58(BST): The reboot has succeeded and the machine is back-up and running smoothly again.

We'll be checking all databases as a matter of course and shall continue to monitor the situation.

---

Update at 09:39:41(BST): Having no luck logging-in remotely, we have been forced to hard-reboot this machine. It is likely that the machine exhausted its swap memory during the surge.

The machine is coming back up now.

---

At present xenserve9 is unresponsive, causing issues with services. This is related to a surge in traffic that has caused a very high load.

We are working as quickly as possible to return the machine to a working state.

Start Time

18th May 2011, at 9:20AM