34SP.com System Status History

Description

16:13 - The issue is now resolved. All SMTP servers can be confirmed as working.

All users are advised to continue using smtp.34sp.com and/or their own smtp.domain.tld addresses for SMTP connections, as these will provide the best level of redundancy.

---

16:07 - We believe that the issue should now be resolved, however Engineers will continue to monitor the affected SMTP servers.

---

Currently you may be unable to send e-mail via the Atmail system, or via SMTP upgrades (used with Professional/Personal & Reseller hosting).

Engineers are currently dealing with the system that hosts all three of the aforementioned machines.

In the mean time, users may temporarily use smtp3.34sp.com, smtp4.34sp.com or smtp7.34sp.com as drop-in replacements.

Start Time

29th January 2010, at 3:38PM

Description

Update at 22:57:44( GMT ) : The issue has now been resolved with this server.

We thank you for your patience with Mother at this time.

---

We're currently investigating a problem that is affecting Mother. All services have had to be disabled whilst the problem is remedied.

It is expected that Mother will be returned to working status shortly.

Start Time

28th January 2010, at 10:53PM

Description

Update at 22:33:48( GMT ) : The issue has now been resolved with this server.

---

22:30 This fault has now been corrected.

22:15 We are presently looking at a fault affecting the server1 reseller system.

Start Time

19th January 2010, at 10:29PM

Description

Update at 22:32:39( GMT ) : The issue has now been resolved with this server.

---

Update @ 09:05. Services should be returned now. Deepthought will be continued to be monitored for a little while longer before this is considered as resolved.

Thank you for your patience during this outage.

---

We're currently experiencing an issue with the Deepthought server. An Engineer is attending and full service should be returned shortly.

Start Time

19th January 2010, at 8:51AM

Description

Update at 14:25:22( GMT ) : The issue has now been resolved with this server.

---

The problem with the atmail system has been identified and the outage is now completely resolved.

Thank you for your patience.

---

It has now come to our attention that POP3/IMAP access may be affected as well.

The investigation into the issue is on-going.

---

At present we're experiencing an outage on the webmail portion of our Spam Filtering (Atmail) e-mail system.

IMAP/POP3 access appears to be working normally.

Engineers are currently investigating the reason for this outage.

Start Time

15th January 2010, at 2:11PM

Description

This has now been resolved. Thank you for your patience.

Update at 12:27:06( GMT ) : The issue has now been resolved with this server.

---

The Engineer has reached the data centre and we're working to bring Prohost2 back on-line as quickly as possible.

We thank you for your continued patience during this outage.

---

An Engineer is en-route to the data centre to conduct repairs.

---

At present Engineers are investigating an outage of the Prohost2 server hardware.

Start Time

15th January 2010, at 10:13AM

Description

Update at 01:44:06 (GMT) : The issue has now been resolved with this server.

---

We are currently looking into issue affecting services on this server.

Start Time

15th January 2010, at 12:45AM

Description

Update at 20:30:15 (GMT) : The issue has now been resolved with this server.

---

Server is currently having some updates installed and will be offline for a short while.

Start Time

14th January 2010, at 8:14PM

Description

Update at 17:38:36( GMT ) : The issue has now been resolved with this server.

This was to carry out an emergency security update.

---

We're currently experiencing an issue with the Apache configuration on Prohost4. All websites are currently down whilst we remedy the issue.

E-mail services are currently not affected.

Start Time

12th January 2010, at 5:20PM

Description

Update at 13:30:33 (GMT) : The issue has now been resolved with this server.

---

An issue was identified with the server at 13:08:44 (GMT) January 12, 2010. 34SP.com engineers have been notified and are presently looking into this problem. Further updates will be posted by our support team, should the problem require extended analysis/correction.

Start Time

12th January 2010, at 1:08PM