<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <link rel="alternate" type="text/html" href="https://opalstackstatus.com/"/>
    <title>Webmail (DE) on Opalstack Status</title>
    <link>https://opalstackstatus.com/affected/webmail-de/</link>
    <description>Incident history</description>
    <generator>github.com/cstate</generator>
    <language>en</language>
    
    <lastBuildDate>2026-07-11T21:29:18+00:00</lastBuildDate>
    <updated>2026-07-11T21:29:18+00:00</updated>
    
    
    
      <atom:link href="https://opalstackstatus.com/affected/webmail-de/index.xml" rel="self" type="application/rss+xml" />
    
    
      <item>
        <title>[Resolved] DE webmail not responding</title>
        <link>https://opalstackstatus.com/issues/2026-07-11-de-webmail-not-responding/</link>
        <pubDate>Sat, 11 Jul 2026 21:29:18 +0000</pubDate>
        <guid>https://opalstackstatus.com/issues/2026-07-11-de-webmail-not-responding/</guid>
        <category>2026-07-11 22:49:02</category>
        <description>&lt;p&gt;&lt;em&gt;Fixed&lt;/em&gt; - Repairs to the host hardware are complete and the webmail server is back online. 
  &lt;span class=&#34;faded&#34;&gt;(22:49 UTC — Jul 11)&lt;/span&gt;

&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Identified&lt;/em&gt; - The outage is caused by a problem with the physical host hardware of the VPS which runs the webmail service. The data center team is investigating and estimated 30-60 minutes of downtime. 
  &lt;span class=&#34;faded&#34;&gt;(21:44 UTC — Jul 11)&lt;/span&gt;

&lt;/p&gt;
&lt;p&gt;Our DE webmail server at webmail.de.opalstack.com is currently not responding. We&amp;rsquo;re investigating at this time. 
  &lt;span class=&#34;faded&#34;&gt;(21:29 UTC — Jul 11)&lt;/span&gt;

&lt;/p&gt;</description>
        <content type="html">&lt;p&gt;&lt;em&gt;Fixed&lt;/em&gt; - Repairs to the host hardware are complete and the webmail server is back online. 
  &lt;span class=&#34;faded&#34;&gt;(22:49 UTC — Jul 11)&lt;/span&gt;

&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Identified&lt;/em&gt; - The outage is caused by a problem with the physical host hardware of the VPS which runs the webmail service. The data center team is investigating and estimated 30-60 minutes of downtime. 
  &lt;span class=&#34;faded&#34;&gt;(21:44 UTC — Jul 11)&lt;/span&gt;

&lt;/p&gt;
&lt;p&gt;Our DE webmail server at webmail.de.opalstack.com is currently not responding. We&amp;rsquo;re investigating at this time. 
  &lt;span class=&#34;faded&#34;&gt;(21:29 UTC — Jul 11)&lt;/span&gt;

&lt;/p&gt;
</content>
      </item>
    
      <item>
        <title>[Resolved] Unplanned Maintenance: webmail.de.opalstack.com</title>
        <link>https://opalstackstatus.com/issues/2025-12-18-unplanned-maintenance-webmaildeopalstackcom/</link>
        <pubDate>Thu, 18 Dec 2025 23:16:00 +0000</pubDate>
        <guid>https://opalstackstatus.com/issues/2025-12-18-unplanned-maintenance-webmaildeopalstackcom/</guid>
        <category>2025-12-19 02:36:40</category>
        <description>&lt;p&gt;We’re looking into a recent unexpected outage affecting webmail.de.opalstack.com. The site is currently up, but our upstream provider will be doing emergency maintenance on the physical host, which will make the service unavailable during that time. We’ll share updates as soon as we have more details.&lt;/p&gt;
&lt;p&gt;Fri Dec 19 02:06 - Server has been powered down for maintenance.&lt;/p&gt;
&lt;p&gt;Fri Dec 19 02:11 - Server maintenance complete, operational 
  &lt;span class=&#34;faded&#34;&gt;(23:16 UTC — Dec 18)&lt;/span&gt;

&lt;/p&gt;</description>
        <content type="html">&lt;p&gt;We’re looking into a recent unexpected outage affecting webmail.de.opalstack.com. The site is currently up, but our upstream provider will be doing emergency maintenance on the physical host, which will make the service unavailable during that time. We’ll share updates as soon as we have more details.&lt;/p&gt;
&lt;p&gt;Fri Dec 19 02:06 - Server has been powered down for maintenance.&lt;/p&gt;
&lt;p&gt;Fri Dec 19 02:11 - Server maintenance complete, operational 
  &lt;span class=&#34;faded&#34;&gt;(23:16 UTC — Dec 18)&lt;/span&gt;

&lt;/p&gt;
</content>
      </item>
    
      <item>
        <title>[Resolved] DE mail SSL certificates were briefly expired</title>
        <link>https://opalstackstatus.com/issues/2024-09-29-de-mail-ssl-certificates-were-briefly-expired/</link>
        <pubDate>Sun, 29 Sep 2024 09:30:00 +0000</pubDate>
        <guid>https://opalstackstatus.com/issues/2024-09-29-de-mail-ssl-certificates-were-briefly-expired/</guid>
        <category>2024-09-29 17:34:48</category>
        <description>&lt;p&gt;Due to an unfortunate oversight on our end the SSL certificates for our DE mail servers expired earlier today at around 09:30 UTC, causing certificate warnings to appear in email client software using DE mailboxes and in our DE webmail system.&lt;/p&gt;
&lt;p&gt;Renewed certificates were rolled out approximately 1 hour later and there have been no issues since that time (~10:30 UTC). If you continue to see a certificate warning when accessing DE email systems then please restart your software and/or your device. 
  &lt;span class=&#34;faded&#34;&gt;(09:30 UTC — Sep 29)&lt;/span&gt;

&lt;/p&gt;</description>
        <content type="html">&lt;p&gt;Due to an unfortunate oversight on our end the SSL certificates for our DE mail servers expired earlier today at around 09:30 UTC, causing certificate warnings to appear in email client software using DE mailboxes and in our DE webmail system.&lt;/p&gt;
&lt;p&gt;Renewed certificates were rolled out approximately 1 hour later and there have been no issues since that time (~10:30 UTC). If you continue to see a certificate warning when accessing DE email systems then please restart your software and/or your device. 
  &lt;span class=&#34;faded&#34;&gt;(09:30 UTC — Sep 29)&lt;/span&gt;

&lt;/p&gt;
</content>
      </item>
    
      <item>
        <title>[Resolved] Germany mail server offline.</title>
        <link>https://opalstackstatus.com/issues/2022-04-01-germany-mail-server-offline/</link>
        <pubDate>Fri, 01 Apr 2022 08:30:00 +0000</pubDate>
        <guid>https://opalstackstatus.com/issues/2022-04-01-germany-mail-server-offline/</guid>
        <category>2022-04-09 13:50:03</category>
        <description>&lt;p&gt;&lt;em&gt;Fixed&lt;/em&gt; - All repairs are complete and all DE mailboxes have been restored.&lt;/p&gt;
&lt;p&gt;If you are a DE mail customer and are still seeing issues with your IMAP/POP3 email then please email Opalstack support for further assistance. 
  &lt;span class=&#34;faded&#34;&gt;(13:50 UTC — Apr 9)&lt;/span&gt;

&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Watching&lt;/em&gt; - The repairs for message dates and mailbox permissions are 75-80% complete. 
  &lt;span class=&#34;faded&#34;&gt;(20:37 UTC — Apr 7)&lt;/span&gt;

&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Watching&lt;/em&gt; - The repairs for dates and mailbox permissions are still in progress. We expect them to be completed today. 
  &lt;span class=&#34;faded&#34;&gt;(13:40 UTC — Apr 7)&lt;/span&gt;

&lt;/p&gt;</description>
        <content type="html">&lt;p&gt;&lt;em&gt;Fixed&lt;/em&gt; - All repairs are complete and all DE mailboxes have been restored.&lt;/p&gt;
&lt;p&gt;If you are a DE mail customer and are still seeing issues with your IMAP/POP3 email then please email Opalstack support for further assistance. 
  &lt;span class=&#34;faded&#34;&gt;(13:50 UTC — Apr 9)&lt;/span&gt;

&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Watching&lt;/em&gt; - The repairs for message dates and mailbox permissions are 75-80% complete. 
  &lt;span class=&#34;faded&#34;&gt;(20:37 UTC — Apr 7)&lt;/span&gt;

&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Watching&lt;/em&gt; - The repairs for dates and mailbox permissions are still in progress. We expect them to be completed today. 
  &lt;span class=&#34;faded&#34;&gt;(13:40 UTC — Apr 7)&lt;/span&gt;

&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Watching&lt;/em&gt; - The restore is complete.&lt;/p&gt;
&lt;p&gt;We&amp;rsquo;re still working on lingering issues related to message dates and mailbox permissions which may take another day or two to fully resolve.&lt;/p&gt;
&lt;p&gt;We&amp;rsquo;ll continue to post updates until the issues are resolved. 
  &lt;span class=&#34;faded&#34;&gt;(02:32 UTC — Apr 6)&lt;/span&gt;

&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Watching&lt;/em&gt; - The restore is 99% complete. 
  &lt;span class=&#34;faded&#34;&gt;(01:42 UTC — Apr 6)&lt;/span&gt;

&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Watching&lt;/em&gt; - The restore is 99% complete.&lt;/p&gt;
&lt;p&gt;Once the restore has completed, there may be sporadic service disruptions for individual mailboxes as we identify lingering issues and correct them. 
  &lt;span class=&#34;faded&#34;&gt;(00:48 UTC — Apr 6)&lt;/span&gt;

&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Watching&lt;/em&gt; - The restore is 98-99% complete. 
  &lt;span class=&#34;faded&#34;&gt;(20:00 UTC — Apr 5)&lt;/span&gt;

&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Watching&lt;/em&gt; - The restore is 93-99% complete. 
  &lt;span class=&#34;faded&#34;&gt;(13:29 UTC — Apr 5)&lt;/span&gt;

&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Watching&lt;/em&gt; - The recovery is 85-95% complete. 
  &lt;span class=&#34;faded&#34;&gt;(01:22 UTC — Apr 5)&lt;/span&gt;

&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Watching&lt;/em&gt; - The recovery is 80-90% complete. 
  &lt;span class=&#34;faded&#34;&gt;(18:29 UTC — Apr 4)&lt;/span&gt;

&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Watching&lt;/em&gt; - The recovery is 75-85% complete. 
  &lt;span class=&#34;faded&#34;&gt;(13:28 UTC — Apr 4)&lt;/span&gt;

&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Watching&lt;/em&gt; - The recovery is 70-80% complete. 
  &lt;span class=&#34;faded&#34;&gt;(01:33 UTC — Apr 4)&lt;/span&gt;

&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Watching&lt;/em&gt; - The recovery is 65-75% complete. Note that there are several parallel restore processes so the overall recovery progress doesn&amp;rsquo;t reflect a percentage of the alphabet with regard to mailbox names. 
  &lt;span class=&#34;faded&#34;&gt;(19:41 UTC — Apr 3)&lt;/span&gt;

&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Watching&lt;/em&gt; - The recovery is 60-70% complete. 
  &lt;span class=&#34;faded&#34;&gt;(15:55 UTC — Apr 3)&lt;/span&gt;

&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Watching&lt;/em&gt; - The recovery is 45-60% complete. 
  &lt;span class=&#34;faded&#34;&gt;(02:22 UTC — Apr 3)&lt;/span&gt;

&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Watching&lt;/em&gt; - The recovery is 30-40% complete. We have to estimate with a range because of the parallel restore processes. 
  &lt;span class=&#34;faded&#34;&gt;(17:00 UTC — Apr 2)&lt;/span&gt;

&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Watching&lt;/em&gt; - The recovery is 24% complete. 
  &lt;span class=&#34;faded&#34;&gt;(13:30 UTC — Apr 2)&lt;/span&gt;

&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Watching&lt;/em&gt; - The recovery from backup is still in progress, albeit running slowly at only 12% complete.&lt;/p&gt;
&lt;p&gt;We believe that we&amp;rsquo;ll be able to recover most of the data from the failed server, so we&amp;rsquo;re restoring that data in parallel with the backup recovery. This should speed up the overall recovery and provide the most recent data from prior to the failure. 
  &lt;span class=&#34;faded&#34;&gt;(04:19 UTC — Apr 2)&lt;/span&gt;

&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Watching&lt;/em&gt; - The recovery is in still progress.&lt;/p&gt;
&lt;p&gt;We estimate that it is 11% complete and it is currently restoring mailboxes that being with &amp;ldquo;as&amp;rdquo;. 
  &lt;span class=&#34;faded&#34;&gt;(21:47 UTC — Apr 1)&lt;/span&gt;

&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Watching&lt;/em&gt; - DE webmail access is now working.&lt;/p&gt;
&lt;p&gt;The mailbox restore is still in progress. 
  &lt;span class=&#34;faded&#34;&gt;(16:13 UTC — Apr 1)&lt;/span&gt;

&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Watching&lt;/em&gt; - We&amp;rsquo;re still noticing some login issues for webmail and are troubleshooting that now. 
  &lt;span class=&#34;faded&#34;&gt;(15:57 UTC — Apr 1)&lt;/span&gt;

&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Watching&lt;/em&gt; - We do not have high expectations for the outcome of the filesystem check, so we&amp;rsquo;ve deployed a new DE IMAP server and have re-created all DE mailboxes as new &lt;strong&gt;empty&lt;/strong&gt; mailboxes on that server.&lt;/p&gt;
&lt;p&gt;Customers should now be able to log in to our DE mail services to send and receive new mail. No changes to your email client settings should be required.&lt;/p&gt;
&lt;p&gt;We&amp;rsquo;ll begin restoring the original mailbox contents ASAP from the most recent backup made on 30 March 2022 (the failure occurred while the 31 March backup was still in progress). The restore may take several days to complete, so we&amp;rsquo;ll keep this post updated until it is done.&lt;/p&gt;
&lt;p&gt;We&amp;rsquo;ll attempt to recover mail from 31 March 2022 when the filesystem repairs on the failed server are complete. 
  &lt;span class=&#34;faded&#34;&gt;(15:30 UTC — Apr 1)&lt;/span&gt;

&lt;/p&gt;
&lt;p&gt;At around 08:30 UTC on 1 April 2022 our DE incoming mail server stopped responding, so we initiated an emergency reboot.&lt;/p&gt;
&lt;p&gt;The server did not reboot correctly and further analysis identified a failing disk associated with outdated disk controller firmware and a failed disk controller battery.&lt;/p&gt;
&lt;p&gt;As of 11:00 UTC the disc controller was repaired and a filesystem check was initiated.&lt;/p&gt;
&lt;p&gt;Further updates follow in reverse-chronological order. 
  &lt;span class=&#34;faded&#34;&gt;(08:30 UTC — Apr 1)&lt;/span&gt;

&lt;/p&gt;
</content>
      </item>
    
  </channel>
</rss>
