Resolved

A resolution for an open issue

Hosted Exchange Issue

Date: 
Wed, 16/03/2011 - 11:00 - 11:21

We are aware of an issue presently affecting connectivity to our Hosted Exchange services. We are looking into the issue and will post further updates shortly.

Update 11:21: Exchange services are now back online and we are looking into the cause of the issue.

RESOLVED: Anti-spam issue

Date: 
Sat, 05/03/2011 - 17:11

Cisco have confirmed there is a hardware fault with our Cisco IronPort anti-spam appliance and they will be replacing this on Tuesday.

In the meantime we have set up a temporary spam filtering appliance using a virtual server. This will still filter spam but may not be as effective and there will be no quarantines (you will receive suspected spam emails with [*** SPAM ***] prepended to the subject).

Emails should now be being delivered correctly and any emails sent during the time the service was unavailable should be delivered eventually when the sending server retries.

RESOLVED: Network issue

Date: 
Wed, 09/02/2011 - 22:44

We have re-installed the Junos software on one of our firewalls and this is now back online. This took longer than expected due to the fact the partition table on the device was corrupted.

We have applied a backup configuration to the firewall so most customer services are now working but there are a handful of customers whose services will still be unavailable. We are working as quickly as possible to restore service to these customers.

COMPLETE: Virtual Server Migration

Date: 
Sun, 06/02/2011 - 00:00 - 03:00

We will be migrating all our virtual servers at our primary site to new hardware during this window. We don't anticipate more than 60 minutes
of downtime for each virtual server, but we will post updates and any issues on this page.

This will affect VPS, shared and resller hosting services, as well as our own website and billing and support systems. This page will not be affected as it is hosted at our DR site. Most VPS customers will have a change to their package during this window - thse customers have been emailed individually about this.

RESOLVED: Networking issue

Date: 
Sat, 05/02/2011 - 17:16

The issue affecting our switches has now been resolved. Both switches are now back online (and have also been upgraded to the recommended software version).

Customer virtual machines will need to be rebooted before they will be available again (as connectivity to the storage was lost during the switch issue). This is happening now and all servers will be back online shortly.

Please accept our apologies for any inconvenience caused.

XenServer Host Issue

Date: 
Thu, 03/02/2011 - 18:57 - 19:27

One of our XenServer hosts has become unresponsive and we need to restart the host as a result. This will cause a disruption to some customer virtual machines.

We apologise for any inconvenience caused.

Update 19:27

RESOLVED: XenServer host issue

Date: 
Wed, 19/01/2011 - 17:09

This issue is now resolved and all affected virtual machines are now coming back online.

We are still investigating the cause of the issue but please accept our apologies for any inconvenience caused.

London firewall issue

Date: 
Mon, 20/09/2010 - 14:36

We are experiencing an issue with our London firewall cluster that is resulting in network unavailability at our main site.

We are working on the issue and will post further updates here.

We apologise for any inconvenience caused.

Update 14:50: This issue is now resolved.

London firewall issue

Date: 
Sat, 03/07/2010 - 05:44 - 06:17

We are experiencing an issue with our London firewall cluster that is resulting in network unavailability at our main site.

We are working on the issue and will post further updates here.

We apologise for any inconvenience caused.

Update 06:17: This issue is now resolved. We still have one cluster node down and an engineer will be visiting the data centre later today to restore full cluster operation.

London firewall issue

Date: 
Tue, 22/06/2010 - 20:21 - 20:26

We just experienced a loss of network connectivity resulting from a firewall issue. This has been corrected and we believe it is related to a previously identified issue that we are waiting for a fix for from the vendor concerned. We are hoping to have this fix deployed in the next two weeks which should avoid any future re-occurence.

We apologise for any inconvenience caused.

Status Update Feed