34SP.com System Status History

colossus.34sp.com (colossus.34sp.com)

resolved

Description

The MySQL server on colossus.34sp.com has failed, along with the ssh server. This combination means that we are currently unable to restart the database service remotely. An engineer is en route to the datacentre to correct the problem locally. At this time, static pages are still being served correctly, and e-mail is still being accepted onto the server. We hope to have full service restored in approximately 1 hour.

UPDATE: An engineer has fixed remote access to the server and we are now working to restore database access.

UPDATE: Service has now been restored on colossus.

Start Time

11th August 2006, at 9:00AM

Resolution Time

11th August 2006, at 8:57AM

Telephone lines down.

resolved

Description

Our telephone lines are now back.

Start Time

1st August 2006, at 12:42PM

Resolution Time

1st August 2006, at 11:53AM

server4.xenserve.com (server4.xenserve.com)

resolved

Description

We are currently looking into an issue affecting this xenserve server.

7.45 - this matter has now been resolved

Start Time

31st July 2006, at 7:38AM

Resolution Time

31st July 2006, at 5:49AM

spam.34sp.com upgrade (spam.34sp.com)

resolved

Description

*NOTE* This upgrade was completed as of half past midnight.

The upgrade of the spam.34sp.com server is presently underway.

Due to a technical complication the upgrade is taking slightly longer than anticipated. We anticipate a further delay of 60-120 minutes at this time.

No mail should be lost during this extended upgrade period.

Thank you in advance for your patience during this period.



Start Time

27th July 2006, at 12:05AM

Resolution Time

26th July 2006, at 10:39PM

Sonny.34sp.com (sonny.34sp.com)

resolved

Description

An issue affecting the sonny.34sp.com server is currently being looked into
----
7.24am - Sonny back online

Start Time

24th July 2006, at 7:22AM

Resolution Time

24th July 2006, at 5:25AM

Sonny.34sp.com (sonny.34sp.com)

resolved

Description

We are currently looking into an issue affecting the sonny.34sp.com server accounts.

----
8.30am - the server has been rebooted remotely.

----
8.50am - a further remote reboot has been actioned.

----
9.10am - an Engineer is on the way to the datacenter to look into this issue further

----
11:25am - this issue has now been resolved - all services should now be back online on the sonny server.

Start Time

20th July 2006, at 8:23AM

Resolution Time

20th July 2006, at 9:28AM

Queeg (queeg.34sp.com)

resolved

Description

This issue has now been resolved at 20:03
--------------

Server rebooted at 19:57

Start Time

19th July 2006, at 7:57PM

Resolution Time

19th July 2006, at 6:03PM

Support Telephones

resolved

Description

Our lines are now fully functional into our offices. We hope you will find the new telephone system enables telephone staff to be even more efficient than before.

--------------------------------
We have just had a new exchange fitted in our office complex as such there are currently some issues with the telephone system.

For now all calls will be handled by the office blocks reception who will then pass you to us until the support line is programmed into the new exchange.

Apologies for any inconvenience caused.

Start Time

17th July 2006, at 9:50AM

Resolution Time

17th July 2006, at 8:39AM

Support.

resolved

Description

Our support operatives are attending telephone training and the lines will not be available until 3pm.

Email support may also be degraded during this time.

We apologies for any inconvenience caused.
This issue has now been resolved at 14:33
--------------

Start Time

14th July 2006, at 2:00PM

Resolution Time

14th July 2006, at 12:33PM

Queeg.34sp.com (Queeg.34sp.com)

resolved

Description

The queeg.34sp.com server has failed.

The server is presently running a self diagnostic of the hard disk array.

We are waiting for this to complete before investigating further.

The queeg.34sp.com server was back online at 6.28PM after the disk check completed. We will now be investigating the cause of this failure.

Start Time

10th July 2006, at 5:59PM

Resolution Time

10th July 2006, at 4:41PM