All systems are operational
Maintenance
PostgreSQL upgrades for opal3, opal14, opal9, and opal16

On Friday 17 May 2024 at 0200 UTC the PostgreSQL database will be upgraded from version 11 to version 14 on the following servers:

  • opal3
  • opal14
  • opal9
  • opal16

We expect the PostgreSQL service to be offline for approximately 1 hour during the upgrade, all other services will continue to function normally.

Past Incidents

17th December 2020

No incidents reported

16th December 2020

DNS: Singapore Singapore servers were offline

At 11:36 UTC on Dec 16, 2020 Linode reported a network connectivity issue in their Singapore datacenter: https://status.linode.com/incidents/bt9z0b25417j

Customer servers and NS in Singapore were affected by this issue and may have been inaccessible at that time. The NS issue may have also affected any domain that uses our Singapore NS.

Service was restored after approximately 2 hours and has been up since that time.

15th December 2020

No incidents reported

14th December 2020

Email: USA Slow IMAP performance

At this time we're importing hundreds of gigabytes of mail for new customers migrating from WebFaction. This is causing heavy load on our IMAP servers so you may see slow performance in our webmail system, IMAP clients, and POP3 downloads over the next few days.

We'll update this post when the imports are complete.

  • The US IMAP service is currently under heavy load while importing mail for new customers.

  • All pending mail imports have been completed and the IMAP servers are operating normally.

    • 13th December 2020

    No incidents reported

    12th December 2020

    No incidents reported

    11th December 2020

    Web: Dallas Recurring attacks on opal4

    opal4.opalstack.com in Dallas TX USA is currently not responding. We're looking into it.

  • Opal4 is stable at this time.

  • Opal4 is not responding, likely another attack. We're investigating.

  • Opal4 is back online. The disruption was caused by another network attack. The replacement server will be set up soon and we'll start scheduling the transition.

  • Opal4 is currently not responding to ping, investigating.

  • Opal4 is stable at this time.

  • Opal4 is back online.

    The earlier assessment of an external network problem was incorrect, this appears to have been another network attack on Opal4.

    The attacks that have taking opal4 down haven't seemed to be particularly massive - similar attacks happen on other shared hosts in our infrastructure and those machines are fine. Because of this we're planning to replace opal4 in the coming weeks. We'll contact all affected customers individually with the details as we finalize the plan.

  • Opal4 is offline due to a network problem in the Leaseweb Dallas TX data center. We're awaiting further updates from them at this time.