Opalstack - Notice history

Opal10 is back online.

Opal10 became non-responsive again so we're rebooting it once more.

Opal10 is back online. The outage was caused by a runaway user process consuming too much memory. We'll work with the related customer to resolve the issue.

We're rebooting opal10 at this time.

We've confirmed that there are no further blocks by Cloudmark.

Cloudmark have stated that they have de-listed the server IPs. We'll continue to monitor until we see no further blocks in the mail logs.

We're still working with Cloudmark to have the US SMTP and MX servers delisted.

We've discovered that the US MX servers are also blocked. This could cause mail forwarding to fail if the final recipient domain is using the Cloudmark block list, so we've requested delisting of those as well.

The issue is confirmed to be resolved.

The data center team identified a switching issue and a fix has been implemented. All London VPS are back online at this time.

We'll continue to monitor awaiting final confirmation from the data center that the issue is fully resolved.

The US SMTP server has remained stable following the upgrade and improved configuration.

We've implemented a fix and authentication is working normally at this time. We'll continue to monitor.

The original US SMTP is back online. We'll continue to troubleshoot and monitor.

We've taken the original US SMTP offline for an emergency upgrade.

The second server is online and is slowly picking up its share of the traffic.

We'll continue to monitor until we're satisfied that this issue is resolved.

We believe the issue is higher-than-average mail traffic, so we're adding a SMTP server to the pool to take up some of the load.

Opal1 is back online and stable online following a reboot.

The issue was caused by high RAM usage by the server's web-based database admin site.