All systems are operational
Maintenance
Scheduled downtime for opal4
  • When: October 26, 2026 19:00 - October 27, 2026 03:00 (US/Central)
  • Duration: Up to 8 hours

On October 26, 2026 at 19:00 US/Central time, opal4.opalstack.com will be taken offline and relocated to a new data center. The relocation may take up to 8 hours, but we are hopeful that it will be completed in less time.

Your websites, files, and databases hosted on the server will be unavailable during the relocation.

Your server IP address will not change.

Your email accounts will remain online during the relocation.

If you would like to move to a different server prior to the scheduled downtime, please contact the Opalstack support team. Most managed migrations are completed with only a few minutes of downtime required.

We apologize for any inconvenience. If you have any questions or concerns regarding the downtime then please contact our support team and someone will get back to you as soon as possible.

Scheduled downtime for imap1.us.opalstack.com
  • When: October 27, 2026 19:00 - October 28, 2026 03:00 (US/Central)
  • Duration: Up to 8 hours

On October 27, 2026 at 19:00 US/Central time, imap1.us.opalstack.com will be taken offline and relocated to a new data center. The relocation may take up to 8 hours, but we are hopeful that it will be completed in less time.

Mailboxes on the server will be unavailable during the relocation. Affected customers have been notified individually.

Websites are hosted on separate infrastructure and will remain online during the relocation.

If you have any questions or concerns regarding this notice then please contact our support team and someone will get back to you.

Scheduled downtime for opal19
  • When: October 28, 2026 19:00 - October 29, 2026 03:00 (US/Central)
  • Duration: Up to 8 hours

On October 28, 2026 at 19:00 US/Central time, opal19.opalstack.com will be taken offline and relocated to a new data center. The relocation may take up to 8 hours, but we are hopeful that it will be completed in less time.

Your websites, files, and databases hosted on the server will be unavailable during the relocation.

Your server IP address will not change.

Your email accounts will remain online during the relocation.

If you would like to move to a different server prior to the scheduled downtime, please contact the Opalstack support team. Most managed migrations are completed with only a few minutes of downtime required.

We apologize for any inconvenience. If you have any questions or concerns regarding the downtime then please contact our support team and someone will get back to you as soon as possible.

Past Incidents

6th January 2022

No incidents reported

5th January 2022

No incidents reported

4th January 2022

No incidents reported

3rd January 2022

Email: Germany German SMTP blocked by Microsoft

On January 3 2022 at 20:47 UTC Microsoft began blocking mail sent from smtp.de.opalstack.com to domains that use the Microsoft 365 email system.

Microsoft's own IP reputation and junk mail reporting systems indicate that there are no problems with smtp.de.opalstack.com so we've reached out to them for answers.

We'll update this post as soon as more information is available.

In the interim as a possible workaround customers may create a new mailbox on our US mail server and use that temporarily for their outgoing email authentication.

  • It's been over a week and we've seen no blocks of the new server IP by MIcrosoft, so we consider this to be resolved.

  • We informed Microsoft of our findings and the corrective action we've taken but we've still received no further communication from them.

    To work around this we've moved smtp.de.opalstack.com to a new IP address. Customers do not need to change any settings - the DNS change should propagate automatically within the hour.

    After the DNS change has propagated, customers should be able to send mail to email addresses that are hosted by Microsoft.

    We'll leave this incident open and will continue to monitor.

  • We've still not heard from Microsoft but we believe we've identified the activity that triggered the block and are taking action to mitigate it at this time.

    We'll notify Microsoft of the actions we're taking and continue to hold on for a response.

  • We're still awaiting a response from Microsoft and have reached out to them as a reminder.

    • 2nd January 2022

    No incidents reported

    1st January 2022

    No incidents reported

    31st December 2021

    No incidents reported