<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Soverin Status - Incident history</title>
    <link>https://status.soverin.net</link>
    <description>Soverin</description>
    <pubDate>Wed, 3 Jun 2026 19:33:41 +0000</pubDate>
    
<item>
  <title>IMAP (binnenkomende mail) outage</title>
  <description>
    Type: Incident
    Duration: 1 minute

    Affected Components: IMAP (binnenkomende mail)
    Jun 3, 19:33:41 GMT+0 - Investigating - IMAP (binnenkomende mail) cannot be accessed at the moment. This incident was created by an automated monitoring service. Jun 3, 19:34:41 GMT+0 - Resolved - IMAP (binnenkomende mail) is now operational! This update was created by an automated monitoring service. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 minute</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Jun &lt;var data-var=&#039;date&#039;&gt; 3&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;19:33:41&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  IMAP (binnenkomende mail) cannot be accessed at the moment. This incident was created by an automated monitoring service..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jun &lt;var data-var=&#039;date&#039;&gt; 3&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;19:34:41&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  IMAP (binnenkomende mail) is now operational! This update was created by an automated monitoring service..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Wed, 3 Jun 2026 19:33:41 +0000</pubDate>
  <link>https://status.soverin.net/incident/cmpygshx000f5p69ymvsq4t0b</link>
  <guid>https://status.soverin.net/incident/cmpygshx000f5p69ymvsq4t0b</guid>
</item>

<item>
  <title>IMAP (binnenkomende mail) outage</title>
  <description>
    Type: Incident
    Duration: 4 minutes

    Affected Components: IMAP (binnenkomende mail)
    Jun 3, 19:29:42 GMT+0 - Investigating - IMAP (binnenkomende mail) cannot be accessed at the moment. This incident was created by an automated monitoring service. Jun 3, 19:33:28 GMT+0 - Resolved - IMAP (binnenkomende mail) is now operational! This update was created by an automated monitoring service. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 4 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Jun &lt;var data-var=&#039;date&#039;&gt; 3&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;19:29:42&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  IMAP (binnenkomende mail) cannot be accessed at the moment. This incident was created by an automated monitoring service..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jun &lt;var data-var=&#039;date&#039;&gt; 3&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;19:33:28&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  IMAP (binnenkomende mail) is now operational! This update was created by an automated monitoring service..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Wed, 3 Jun 2026 19:29:42 +0000</pubDate>
  <link>https://status.soverin.net/incident/cmpygndbi04utnwx4rh438auq</link>
  <guid>https://status.soverin.net/incident/cmpygndbi04utnwx4rh438auq</guid>
</item>

<item>
  <title>IMAP (binnenkomende mail) outage</title>
  <description>
    Type: Incident
    

    Affected Components: IMAP (binnenkomende mail)
    Jun 3, 19:28:16 GMT+0 - Investigating - IMAP (binnenkomende mail) cannot be accessed at the moment. This incident was created by an automated monitoring service. Jun 3, 19:28:40 GMT+0 - Resolved - IMAP (binnenkomende mail) is now operational! This update was created by an automated monitoring service. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Jun &lt;var data-var=&#039;date&#039;&gt; 3&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;19:28:16&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  IMAP (binnenkomende mail) cannot be accessed at the moment. This incident was created by an automated monitoring service..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jun &lt;var data-var=&#039;date&#039;&gt; 3&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;19:28:40&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  IMAP (binnenkomende mail) is now operational! This update was created by an automated monitoring service..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Wed, 3 Jun 2026 19:28:16 +0000</pubDate>
  <link>https://status.soverin.net/incident/cmpyglipk04spqulj1r0pf3ob</link>
  <guid>https://status.soverin.net/incident/cmpyglipk04spqulj1r0pf3ob</guid>
</item>

<item>
  <title>Intermittent connection failures to IMAP, SMTP, our dashboard and webmail</title>
  <description>
    Type: Incident
    Duration: 2 hours and 22 minutes

    Affected Components: Webmail (Aurora), Webmail (Roundcube), Website, IMAP (binnenkomende mail), Dashboard, SMTP (uitgaande mail)
    Jun 3, 18:41:57 GMT+0 - Identified - Our services are intermittently interrupted because of a DDOS attack; we are working on better filtering the traffic. Jun 3, 20:04:10 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Jun 3, 21:04:00 GMT+0 - Resolved - This incident has been resolved. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 2 hours and 22 minutes</p>
    <p><strong>Affected Components:</strong> , , , , , </p>
    &lt;p&gt;&lt;small&gt;Jun &lt;var data-var=&#039;date&#039;&gt; 3&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;18:41:57&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Our services are intermittently interrupted because of a DDOS attack; we are working on better filtering the traffic..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jun &lt;var data-var=&#039;date&#039;&gt; 3&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;20:04:10&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  We implemented a fix and are currently monitoring the result..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jun &lt;var data-var=&#039;date&#039;&gt; 3&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;21:04:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Wed, 3 Jun 2026 18:41:57 +0000</pubDate>
  <link>https://status.soverin.net/incident/cmpyexz0x04b0nwx4kyly0jjh</link>
  <guid>https://status.soverin.net/incident/cmpyexz0x04b0nwx4kyly0jjh</guid>
</item>

<item>
  <title>Deliverability to Microsoft (hotmail.com, outlook.com)</title>
  <description>
    Type: Incident
    Duration: 2 days, 21 hours and 11 minutes

    Affected Components: SMTP (uitgaande mail)
    Feb 24, 10:00:00 GMT+0 - Identified - Microsoft is implementing a new inbound mail filtering system and is broadly rate limiting external addresses for many senders. We are currently stricken by this problem with a number of our outbound ip addresses. We are rotating where we can however mail is being queued and delayed due to this problem.  
  
We are in contact with Microsoft to try to work to a solution. Unfortunately the microsoft sender support portal (specifically meant for this) is also experiencing serious problems.  
  
The listed ip addresses register as &quot;green&quot; with microsoft with a complaint rate of less than 0.1% (which is truly low), so the reason for the blocks is unknown as of yet.  
  
  
Impact: mails sent to [outlook.com](http://outlook.com) and [hotmail.com](http://hotmail.com) addresses (and related domains) can be delayed. Feb 24, 20:58:13 GMT+0 - Monitoring - We have rerouted all affected emails to other servers. All queued emails have been processed.   
  
During our efforts an unfortunate mistake rejected a number or emails with a specific error message: `Error: too many hops` If you received such message from us, please send the message again, it will be accepted and sent.  

We are waiting for a delisting response from Microsoft to resume normal operations. 

  
Current impact: no customer impact at this moment, we are monitoring the situation. Feb 27, 07:11:03 GMT+0 - Resolved - This incident has been resolved.  
  
After the initial mitigations we have seen no further deliverability issues. Microsoft is now acknowledging the platform wide problem and is responding to postmasters once again.   
  
The total impact to our users was limited to the first 12 hours of the incident in which about one percent of messages we send to Microsoft were delayed. Most were rerouted and delivered with an hour. 

   
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 2 days, 21 hours and 11 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Feb &lt;var data-var=&#039;date&#039;&gt; 24&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;10:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Microsoft is implementing a new inbound mail filtering system and is broadly rate limiting external addresses for many senders. We are currently stricken by this problem with a number of our outbound ip addresses. We are rotating where we can however mail is being queued and delayed due to this problem.  
  
We are in contact with Microsoft to try to work to a solution. Unfortunately the microsoft sender support portal (specifically meant for this) is also experiencing serious problems.  
  
The listed ip addresses register as &quot;green&quot; with microsoft with a complaint rate of less than 0.1% (which is truly low), so the reason for the blocks is unknown as of yet.  
  
  
Impact: mails sent to [outlook.com](http://outlook.com) and [hotmail.com](http://hotmail.com) addresses (and related domains) can be delayed..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Feb &lt;var data-var=&#039;date&#039;&gt; 24&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;20:58:13&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  We have rerouted all affected emails to other servers. All queued emails have been processed.   
  
During our efforts an unfortunate mistake rejected a number or emails with a specific error message: `Error: too many hops` If you received such message from us, please send the message again, it will be accepted and sent.  

We are waiting for a delisting response from Microsoft to resume normal operations. 

  
Current impact: no customer impact at this moment, we are monitoring the situation..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Feb &lt;var data-var=&#039;date&#039;&gt; 27&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;07:11:03&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved.  
  
After the initial mitigations we have seen no further deliverability issues. Microsoft is now acknowledging the platform wide problem and is responding to postmasters once again.   
  
The total impact to our users was limited to the first 12 hours of the incident in which about one percent of messages we send to Microsoft were delayed. Most were rerouted and delivered with an hour. 

  .&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Tue, 24 Feb 2026 10:00:00 +0000</pubDate>
  <link>https://status.soverin.net/incident/cmm0y8ty10385uk4aiqsz5uko</link>
  <guid>https://status.soverin.net/incident/cmm0y8ty10385uk4aiqsz5uko</guid>
</item>

<item>
  <title>Temporary Issue with Outgoing Email Delivery</title>
  <description>
    Type: Incident
    Duration: 14 minutes

    Affected Components: SMTP (uitgaande mail)
    Dec 9, 12:14:34 GMT+0 - Investigating - We are currently experiencing issues with outgoing email. Our team is actively investigating and working on a solution. As a precaution, we have temporarily disabled the sending of emails to prevent further disruption.

Any emails you attempt to send during this period will be queued and delivered once the issue has been resolved.

Thank you for your understanding and patience while we work to restore normal service.

We will keep you updated. Dec 9, 12:28:47 GMT+0 - Resolved - We experienced an issue with our outgoing mail flow due to an incorrect configuration in the email routing setup. This prevented outbound emails from being sent successfully.

As a result, some emails were not delivered, and customers may have received an incorrect “unable to deliver” notification.

About 15 minutes after identifying the issue, we temporarily disabled all outgoing email to prevent further failed delivery attempts. A fix was deployed, and outgoing email was re-enabled roughly 30 minutes later.

All systems are now operating normally. Our apologies for any inconvenience this may have caused. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 14 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Dec &lt;var data-var=&#039;date&#039;&gt; 9&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;12:14:34&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are currently experiencing issues with outgoing email. Our team is actively investigating and working on a solution. As a precaution, we have temporarily disabled the sending of emails to prevent further disruption.

Any emails you attempt to send during this period will be queued and delivered once the issue has been resolved.

Thank you for your understanding and patience while we work to restore normal service.

We will keep you updated..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Dec &lt;var data-var=&#039;date&#039;&gt; 9&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;12:28:47&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  We experienced an issue with our outgoing mail flow due to an incorrect configuration in the email routing setup. This prevented outbound emails from being sent successfully.

As a result, some emails were not delivered, and customers may have received an incorrect “unable to deliver” notification.

About 15 minutes after identifying the issue, we temporarily disabled all outgoing email to prevent further failed delivery attempts. A fix was deployed, and outgoing email was re-enabled roughly 30 minutes later.

All systems are now operating normally. Our apologies for any inconvenience this may have caused..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Tue, 9 Dec 2025 12:14:34 +0000</pubDate>
  <link>https://status.soverin.net/incident/cmiyjlwkw077tc8n932s8c259</link>
  <guid>https://status.soverin.net/incident/cmiyjlwkw077tc8n932s8c259</guid>
</item>

<item>
  <title>Webmail and Calendar not reachable</title>
  <description>
    Type: Incident
    Duration: 15 hours and 45 minutes

    Affected Components: Webmail (Aurora)
    Nov 26, 17:50:00 GMT+0 - Investigating - We are currently investigating this incident. Nov 27, 07:40:38 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Nov 27, 09:34:53 GMT+0 - Resolved - This incident has been resolved. The problem started after a routine certificate update which inadvertently caused the webmail service to have problems serving the necessary (javascript) files. The problem has been fixed and we have updated our certificate rollout logic to prevent recurrence. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 15 hours and 45 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Nov &lt;var data-var=&#039;date&#039;&gt; 26&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;17:50:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are currently investigating this incident..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Nov &lt;var data-var=&#039;date&#039;&gt; 27&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;07:40:38&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  We implemented a fix and are currently monitoring the result..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Nov &lt;var data-var=&#039;date&#039;&gt; 27&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;09:34:53&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved. The problem started after a routine certificate update which inadvertently caused the webmail service to have problems serving the necessary (javascript) files. The problem has been fixed and we have updated our certificate rollout logic to prevent recurrence..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Wed, 26 Nov 2025 17:50:00 +0000</pubDate>
  <link>https://status.soverin.net/incident/cmih4dkhh00yrh7ovp7ofckn8</link>
  <guid>https://status.soverin.net/incident/cmih4dkhh00yrh7ovp7ofckn8</guid>
</item>

<item>
  <title>Outgoing email</title>
  <description>
    Type: Incident
    Duration: 1 hour and 6 minutes

    Affected Components: Webmail (Roundcube), Webmail (Aurora), SMTP (uitgaande mail)
    Sep 12, 08:20:00 GMT+0 - Resolved - This incident has been resolved. Sep 12, 07:30:00 GMT+0 - Investigating - We are currently investigating this incident. Sep 12, 07:35:31 GMT+0 - Identified - We are continuing to work on a fix for this incident. Sep 12, 08:15:00 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 6 minutes</p>
    <p><strong>Affected Components:</strong> , , </p>
    &lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 12&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;08:20:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 12&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;07:30:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are currently investigating this incident..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 12&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;07:35:31&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We are continuing to work on a fix for this incident..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 12&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;08:15:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  We implemented a fix and are currently monitoring the result..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Fri, 12 Sep 2025 07:30:00 +0000</pubDate>
  <link>https://status.soverin.net/incident/cmfgjzjos002oryioqrof860r</link>
  <guid>https://status.soverin.net/incident/cmfgjzjos002oryioqrof860r</guid>
</item>

<item>
  <title>regular technical maintenance</title>
  <description>
    Type: Maintenance
    Duration: 1 hour and 58 minutes

    Affected Components: Website, Dashboard, Webmail (Roundcube), Webmail (Aurora), SMTP (uitgaande mail), IMAP (binnenkomende mail)
    Jan 21, 21:00:00 GMT+0 - Identified - We are planning for a scheduled maintenance during that time. Jan 21, 22:57:46 GMT+0 - Completed - Maintenance has completed successfully. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 1 hour and 58 minutes</p>
    <p><strong>Affected Components:</strong> , , , , , </p>
    &lt;p&gt;&lt;small&gt;Jan &lt;var data-var=&#039;date&#039;&gt; 21&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;21:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We are planning for a scheduled maintenance during that time..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jan &lt;var data-var=&#039;date&#039;&gt; 21&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;22:57:46&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  Maintenance has completed successfully..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Tue, 21 Jan 2025 21:00:00 +0000</pubDate>
  <link>https://status.soverin.net/maintenance/cm6708abp01j9x7nv3h1z5fvs</link>
  <guid>https://status.soverin.net/maintenance/cm6708abp01j9x7nv3h1z5fvs</guid>
</item>

<item>
  <title>IMAP (binnenkomende mail) outage</title>
  <description>
    Type: Incident
    Duration: 2 days, 8 hours and 54 minutes

    Affected Components: IMAP (binnenkomende mail)
    Nov 12, 21:38:40 GMT+0 - Investigating - IMAP (binnenkomende mail) cannot be accessed at the moment. This incident was created by an automated monitoring service. Nov 12, 22:35:33 GMT+0 - Resolved - IMAP (binnenkomende mail) is now operational! This update was created by an automated monitoring service. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 2 days, 8 hours and 54 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Nov &lt;var data-var=&#039;date&#039;&gt; 12&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;21:38:40&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  IMAP (binnenkomende mail) cannot be accessed at the moment. This incident was created by an automated monitoring service..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Nov &lt;var data-var=&#039;date&#039;&gt; 12&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;22:35:33&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  IMAP (binnenkomende mail) is now operational! This update was created by an automated monitoring service..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Tue, 12 Nov 2024 21:38:40 +0000</pubDate>
  <link>https://status.soverin.net/incident/cm3ez5cv300gbgke67yqrujrs</link>
  <guid>https://status.soverin.net/incident/cm3ez5cv300gbgke67yqrujrs</guid>
</item>

<item>
  <title>IMAP (binnenkomende mail) outage</title>
  <description>
    Type: Incident
    Duration: 4 minutes

    Affected Components: IMAP (binnenkomende mail)
    Sep 26, 07:48:00 GMT+0 - Resolved - This incident has been resolved. Sep 26, 07:43:41 GMT+0 - Investigating - IMAP (binnenkomende mail) cannot be accessed at the moment. This incident was created by an automated monitoring service. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 4 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 26&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;07:48:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 26&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;07:43:41&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  IMAP (binnenkomende mail) cannot be accessed at the moment. This incident was created by an automated monitoring service..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Thu, 26 Sep 2024 07:43:41 +0000</pubDate>
  <link>https://status.soverin.net/incident/cm1izmj8900n6edt9hqqlzyjv</link>
  <guid>https://status.soverin.net/incident/cm1izmj8900n6edt9hqqlzyjv</guid>
</item>

<item>
  <title>IMAP (binnenkomende mail) outage</title>
  <description>
    Type: Incident
    Duration: 5 hours and 49 minutes

    Affected Components: IMAP (binnenkomende mail)
    Aug 29, 01:36:44 GMT+0 - Investigating - IMAP (binnenkomende mail) cannot be accessed at the moment. This incident was created by an automated monitoring service. Aug 29, 01:42:32 GMT+0 - Resolved - IMAP (binnenkomende mail) is now operational! This update was created by an automated monitoring service. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 5 hours and 49 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 29&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;01:36:44&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  IMAP (binnenkomende mail) cannot be accessed at the moment. This incident was created by an automated monitoring service..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 29&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;01:42:32&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  IMAP (binnenkomende mail) is now operational! This update was created by an automated monitoring service..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Thu, 29 Aug 2024 01:36:44 +0000</pubDate>
  <link>https://status.soverin.net/incident/cm0em6s4k002dxtaprb18piuu</link>
  <guid>https://status.soverin.net/incident/cm0em6s4k002dxtaprb18piuu</guid>
</item>

<item>
  <title>Weekly maintenance window - Tuesdays between 22:00 and 00:00 (CEST)</title>
  <description>
    Type: Maintenance
    Duration: 49 minutes

    Affected Components: Dashboard, Webmail (Aurora)
    Jul 2, 20:00:00 GMT+0 - Identified - We are planning for a scheduled maintenance during that time. Jul 2, 20:00:01 GMT+0 - Identified - Maintenance is now in progress Jul 2, 20:48:40 GMT+0 - Completed - Our webmail maintenance has been completed. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 49 minutes</p>
    <p><strong>Affected Components:</strong> , </p>
    &lt;p&gt;&lt;small&gt;Jul &lt;var data-var=&#039;date&#039;&gt; 2&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;20:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We are planning for a scheduled maintenance during that time..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jul &lt;var data-var=&#039;date&#039;&gt; 2&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;20:00:01&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Maintenance is now in progress.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jul &lt;var data-var=&#039;date&#039;&gt; 2&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;20:48:40&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  Our webmail maintenance has been completed..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Tue, 2 Jul 2024 20:00:00 +0000</pubDate>
  <link>https://status.soverin.net/maintenance/clxxb4om844739agmwkgybvmmx</link>
  <guid>https://status.soverin.net/maintenance/clxxb4om844739agmwkgybvmmx</guid>
</item>

<item>
  <title>Software release and webmail update - 25-06-2024 22:00 and 00:00 (CEST)</title>
  <description>
    Type: Maintenance
    Duration: 2 hours

    Affected Components: Dashboard
    Jun 25, 20:00:01 GMT+0 - Identified - Maintenance is now in progress Jun 25, 22:00:00 GMT+0 - Completed - Maintenance has completed successfully Jun 25, 22:19:35 GMT+0 - Completed - **Aftercare (please read)**  
\- During our production test we noticed a caching issue with one of the browsers we used. When logging out, we received the error message: “**The page you were looking for doesn’t exist**”.   

A **Shift+Refresh** or “**new private window**” will solve the issue.   Jun 25, 20:00:00 GMT+0 - Identified - We are planning for a scheduled maintenance to implement a software release. This will include a webmail (Aurora) update. This may cause minor webmail disruptions during our maintenance window. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 2 hours</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Jun &lt;var data-var=&#039;date&#039;&gt; 25&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;20:00:01&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Maintenance is now in progress.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jun &lt;var data-var=&#039;date&#039;&gt; 25&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;22:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  Maintenance has completed successfully.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jun &lt;var data-var=&#039;date&#039;&gt; 25&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;22:19:35&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  **Aftercare (please read)**  
\- During our production test we noticed a caching issue with one of the browsers we used. When logging out, we received the error message: “**The page you were looking for doesn’t exist**”.   

A **Shift+Refresh** or “**new private window**” will solve the issue.  .&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jun &lt;var data-var=&#039;date&#039;&gt; 25&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;20:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We are planning for a scheduled maintenance to implement a software release. This will include a webmail (Aurora) update. This may cause minor webmail disruptions during our maintenance window..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Tue, 25 Jun 2024 20:00:00 +0000</pubDate>
  <link>https://status.soverin.net/maintenance/clxu5rej265856beoo4rl7xwgv</link>
  <guid>https://status.soverin.net/maintenance/clxu5rej265856beoo4rl7xwgv</guid>
</item>

<item>
  <title>IMAP (binnenkomende mail) outage</title>
  <description>
    Type: Incident
    Duration: 3 hours and 54 minutes

    Affected Components: IMAP (binnenkomende mail)
    Jun 15, 21:03:35 GMT+0 - Investigating - IMAP (binnenkomende mail) cannot be accessed at the moment. This incident was created by an automated monitoring service. Jun 15, 21:07:29 GMT+0 - Resolved - IMAP (binnenkomende mail) is now operational! This update was created by an automated monitoring service. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 3 hours and 54 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Jun &lt;var data-var=&#039;date&#039;&gt; 15&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;21:03:35&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  IMAP (binnenkomende mail) cannot be accessed at the moment. This incident was created by an automated monitoring service..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jun &lt;var data-var=&#039;date&#039;&gt; 15&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;21:07:29&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  IMAP (binnenkomende mail) is now operational! This update was created by an automated monitoring service..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Sat, 15 Jun 2024 21:03:35 +0000</pubDate>
  <link>https://status.soverin.net/incident/clxgluhbc73166f6n4oq10azth</link>
  <guid>https://status.soverin.net/incident/clxgluhbc73166f6n4oq10azth</guid>
</item>

<item>
  <title>IMAP (binnenkomende mail) outage</title>
  <description>
    Type: Incident
    Duration: 2 hours and 59 minutes

    Affected Components: IMAP (binnenkomende mail)
    Jun 14, 23:10:30 GMT+0 - Resolved - IMAP (binnenkomende mail) is now operational! This update was created by an automated monitoring service. Jun 14, 23:07:31 GMT+0 - Investigating - IMAP (binnenkomende mail) cannot be accessed at the moment. This incident was created by an automated monitoring service. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 2 hours and 59 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Jun &lt;var data-var=&#039;date&#039;&gt; 14&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;23:10:30&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  IMAP (binnenkomende mail) is now operational! This update was created by an automated monitoring service..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jun &lt;var data-var=&#039;date&#039;&gt; 14&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;23:07:31&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  IMAP (binnenkomende mail) cannot be accessed at the moment. This incident was created by an automated monitoring service..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Fri, 14 Jun 2024 23:07:31 +0000</pubDate>
  <link>https://status.soverin.net/incident/clxfau07c411594f6ncdlt5agk0</link>
  <guid>https://status.soverin.net/incident/clxfau07c411594f6ncdlt5agk0</guid>
</item>

<item>
  <title>Network maintenance</title>
  <description>
    Type: Maintenance
    Duration: 38 minutes

    Affected Components: Website, Dashboard, Webmail (Roundcube), Webmail (Aurora), SMTP (uitgaande mail), IMAP (binnenkomende mail)
    Jun 11, 20:00:01 GMT+0 - Identified - Maintenance is now in progress Jun 11, 20:00:00 GMT+0 - Identified - Tonight we will preform network maintenance. There will be a brief downtime while we upgrade our network configuration and routing.  Jun 11, 20:38:18 GMT+0 - Completed - Our technical maintenance is completed. All systems are up again and functioning within normal parameters. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 38 minutes</p>
    <p><strong>Affected Components:</strong> , , , , , </p>
    &lt;p&gt;&lt;small&gt;Jun &lt;var data-var=&#039;date&#039;&gt; 11&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;20:00:01&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Maintenance is now in progress.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jun &lt;var data-var=&#039;date&#039;&gt; 11&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;20:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Tonight we will preform network maintenance. There will be a brief downtime while we upgrade our network configuration and routing. .&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jun &lt;var data-var=&#039;date&#039;&gt; 11&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;20:38:18&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  Our technical maintenance is completed. All systems are up again and functioning within normal parameters..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Tue, 11 Jun 2024 20:00:00 +0000</pubDate>
  <link>https://status.soverin.net/maintenance/clxatdgca113991b5n7uq96x66g</link>
  <guid>https://status.soverin.net/maintenance/clxatdgca113991b5n7uq96x66g</guid>
</item>

<item>
  <title>IMAP (binnenkomende mail) outage</title>
  <description>
    Type: Incident
    Duration: 3 hours and 49 minutes

    Affected Components: IMAP (binnenkomende mail)
    Jun 4, 20:52:42 GMT+0 - Investigating - IMAP (binnenkomende mail) cannot be accessed at the moment. This incident was created by an automated monitoring service. Jun 4, 20:56:31 GMT+0 - Resolved - IMAP (binnenkomende mail) is now operational! This update was created by an automated monitoring service. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 3 hours and 49 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Jun &lt;var data-var=&#039;date&#039;&gt; 4&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;20:52:42&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  IMAP (binnenkomende mail) cannot be accessed at the moment. This incident was created by an automated monitoring service..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jun &lt;var data-var=&#039;date&#039;&gt; 4&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;20:56:31&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  IMAP (binnenkomende mail) is now operational! This update was created by an automated monitoring service..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Tue, 4 Jun 2024 20:52:42 +0000</pubDate>
  <link>https://status.soverin.net/incident/clx0vm3xo279029krmzx7dxvq0k</link>
  <guid>https://status.soverin.net/incident/clx0vm3xo279029krmzx7dxvq0k</guid>
</item>

<item>
  <title>Weekly maintenance window - Tuesdays between 22:00 and 00:00 (CEST)</title>
  <description>
    Type: Maintenance
    Duration: 1 hour and 27 minutes

    Affected Components: Webmail (Aurora)
    Apr 23, 20:02:29 GMT+0 - Identified - We have started our weekly maintenance and will update you with any progress. Apr 23, 21:26:41 GMT+0 - Completed - We have completed our maintenance and are running the migrated version of our Aurora webmail suite Apr 23, 20:00:01 GMT+0 - Identified - Maintenance is now in progress Apr 23, 20:00:00 GMT+0 - Identified - During the coming release we will update our beta Webmail suite to the latest version &amp; correct a few translations on the admin panel. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 1 hour and 27 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 23&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;20:02:29&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We have started our weekly maintenance and will update you with any progress..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 23&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;21:26:41&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  We have completed our maintenance and are running the migrated version of our Aurora webmail suite.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 23&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;20:00:01&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Maintenance is now in progress.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 23&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;20:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  During the coming release we will update our beta Webmail suite to the latest version &amp; correct a few translations on the admin panel..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Tue, 23 Apr 2024 20:00:00 +0000</pubDate>
  <link>https://status.soverin.net/maintenance/clv5bby8u18259bsn2ttcedswn</link>
  <guid>https://status.soverin.net/maintenance/clv5bby8u18259bsn2ttcedswn</guid>
</item>

<item>
  <title>Some customers might experience brief disruptions sending out email</title>
  <description>
    Type: Incident
    Duration: 9 minutes

    Affected Components: Webmail (Roundcube), SMTP (uitgaande mail)
    Apr 17, 08:09:39 GMT+0 - Investigating - We are currently investigating this incident and update with more information soon Apr 17, 08:18:56 GMT+0 - Resolved - We have found the cause and fixed the service. All mails still waiting to be sent are being processed at the moment. Our servers might take a few minutes to catch up. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 9 minutes</p>
    <p><strong>Affected Components:</strong> , </p>
    &lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 17&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;08:09:39&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are currently investigating this incident and update with more information soon.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 17&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;08:18:56&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  We have found the cause and fixed the service. All mails still waiting to be sent are being processed at the moment. Our servers might take a few minutes to catch up..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Wed, 17 Apr 2024 08:09:39 +0000</pubDate>
  <link>https://status.soverin.net/incident/clv3j7xwy22900c6n4mj0c1nhk</link>
  <guid>https://status.soverin.net/incident/clv3j7xwy22900c6n4mj0c1nhk</guid>
</item>

<item>
  <title>Weekly maintenance window - Tuesdays between 22:00 and 00:00 (CEST)</title>
  <description>
    Type: Maintenance
    Duration: 30 minutes

    Affected Components: Dashboard
    Apr 16, 20:32:37 GMT+0 - Completed - Our maintenance has successfully finished. Apr 16, 20:02:25 GMT+0 - Identified - started software update Apr 16, 20:00:00 GMT+0 - Identified - We have a weekly maintenance window to bring new features or maintain our core network. During this window you might experience brief disruption. We will keep disruptions to a minimum. Thank you for your understanding.  
  
Team Soverin 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 30 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 16&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;20:32:37&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  Our maintenance has successfully finished..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 16&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;20:02:25&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  started software update.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 16&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;20:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We have a weekly maintenance window to bring new features or maintain our core network. During this window you might experience brief disruption. We will keep disruptions to a minimum. Thank you for your understanding.  
  
Team Soverin.&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Tue, 16 Apr 2024 20:00:00 +0000</pubDate>
  <link>https://status.soverin.net/maintenance/clusvg8np99282b9lij9ss0h5i</link>
  <guid>https://status.soverin.net/maintenance/clusvg8np99282b9lij9ss0h5i</guid>
</item>

<item>
  <title>Migration</title>
  <description>
    Type: Maintenance
    Duration: 6 hours and 18 minutes

    Affected Components: Website, Dashboard, Webmail (Roundcube), Webmail (Aurora), SMTP (uitgaande mail), IMAP (binnenkomende mail)
    Apr 6, 19:58:57 GMT+0 - Identified - ETA of our servers arriving at their new home is only 15 minutes away. Apr 6, 23:00:45 GMT+0 - Identified - Since our servers received a cold-boot, they might be slower than usual, They are trying to make up for lost time. Please be patience and kind to them. Apr 6, 23:14:28 GMT+0 - Identified - You can wake up your phones again.

  
We will do some more finetuning and aftercare, but all mails from the past 5 hours have been sent to your Soverin mailboxes. Apr 6, 21:53:19 GMT+0 - Identified - We have an internal heartbeat. All servers are healthy and talking to our tech-team. Apr 6, 17:49:04 GMT+0 - Identified - In 15 minutes our maintenance window will start. Please check here regularly for maintenance updates. Apr 6, 18:19:32 GMT+0 - Identified - All our backup servers for catching your e-mails are online. Your email will be delivered to your mailbox after the maintenance is finished. Apr 6, 20:22:22 GMT+0 - Identified - Our servers have arrived. They will get a short tour of the place before they will pick their spot in the new rack Apr 6, 19:11:40 GMT+0 - Identified - All our mailservers have left their old home and have started their save journey to our new location. Apr 7, 00:20:30 GMT+0 - Completed - Our first Engineers are on their way home, while the other half stayed to lock our servers securely behind doors.

  
After the first engineers are home and ready to take over watch, the others can safely return home. Apr 6, 22:55:11 GMT+0 - Identified - Our servers are happy to receive mails again, sending out new mails are also processed.

  
Soon they can open the box with stored mails from our downtime to sort and deliver those as well. Apr 6, 20:49:14 GMT+0 - Identified - Our team is working hard to neatly slot the servers into their place. Apr 6, 22:27:47 GMT+0 - Identified - Our mailservers gave a few test shout-outs to the world.

  
Just running a few more tests before we unleash their full force sending and receiving mails Apr 6, 21:06:16 GMT+0 - Identified - Efficiency; All servers are hooked up to their life support and backup juice. Time to slowly revive the first server. Apr 6, 18:00:00 GMT+0 - Identified - At Soverin, safeguarding your email experience is our absolute priority. In our journey of perfecting our services, we&#039;re excited to share that we&#039;re moving to a new data center provider, unlocking geographical redundancy for an even more robust system. Just to clarify, we will of course remain 100% Dutch, and our mail servers will therefore also remain in the Netherlands.

During this period, there&#039;s a brief downtime, where emails play a bit of hide-and-seek. Rest assured, no emails are lost; they&#039;re just taking a fashionable pause and will grace your inbox fashionably late once the migration is complete. We understand that waiting isn&#039;t exactly thrilling, but this method guarantees your data stays rock-solid, and our email flow stays as smooth as ever. Our goal is to relocate our hardware seamlessly, minimizing any disruption during this techical upgrade. Apr 6, 18:02:27 GMT+0 - Identified - Servers are being shutdown. You can close your email clients and apps and give them some rest for a few hours Apr 6, 21:20:21 GMT+0 - Identified - First 4 servers are booting 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 6 hours and 18 minutes</p>
    <p><strong>Affected Components:</strong> , , , , , </p>
    &lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 6&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;19:58:57&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  ETA of our servers arriving at their new home is only 15 minutes away..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 6&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;23:00:45&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Since our servers received a cold-boot, they might be slower than usual, They are trying to make up for lost time. Please be patience and kind to them..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 6&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;23:14:28&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  You can wake up your phones again.

  
We will do some more finetuning and aftercare, but all mails from the past 5 hours have been sent to your Soverin mailboxes..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 6&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;21:53:19&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We have an internal heartbeat. All servers are healthy and talking to our tech-team..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 6&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;17:49:04&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  In 15 minutes our maintenance window will start. Please check here regularly for maintenance updates..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 6&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;18:19:32&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  All our backup servers for catching your e-mails are online. Your email will be delivered to your mailbox after the maintenance is finished..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 6&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;20:22:22&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Our servers have arrived. They will get a short tour of the place before they will pick their spot in the new rack.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 6&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;19:11:40&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  All our mailservers have left their old home and have started their save journey to our new location..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 7&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;00:20:30&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  Our first Engineers are on their way home, while the other half stayed to lock our servers securely behind doors.

  
After the first engineers are home and ready to take over watch, the others can safely return home..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 6&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;22:55:11&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Our servers are happy to receive mails again, sending out new mails are also processed.

  
Soon they can open the box with stored mails from our downtime to sort and deliver those as well..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 6&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;20:49:14&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Our team is working hard to neatly slot the servers into their place..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 6&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;22:27:47&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Our mailservers gave a few test shout-outs to the world.

  
Just running a few more tests before we unleash their full force sending and receiving mails.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 6&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;21:06:16&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Efficiency; All servers are hooked up to their life support and backup juice. Time to slowly revive the first server..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 6&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;18:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  At Soverin, safeguarding your email experience is our absolute priority. In our journey of perfecting our services, we&#039;re excited to share that we&#039;re moving to a new data center provider, unlocking geographical redundancy for an even more robust system. Just to clarify, we will of course remain 100% Dutch, and our mail servers will therefore also remain in the Netherlands.

During this period, there&#039;s a brief downtime, where emails play a bit of hide-and-seek. Rest assured, no emails are lost; they&#039;re just taking a fashionable pause and will grace your inbox fashionably late once the migration is complete. We understand that waiting isn&#039;t exactly thrilling, but this method guarantees your data stays rock-solid, and our email flow stays as smooth as ever. Our goal is to relocate our hardware seamlessly, minimizing any disruption during this techical upgrade..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 6&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;18:02:27&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Servers are being shutdown. You can close your email clients and apps and give them some rest for a few hours.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 6&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;21:20:21&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  First 4 servers are booting.&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Sat, 6 Apr 2024 18:00:00 +0000</pubDate>
  <link>https://status.soverin.net/maintenance/clul36mow44693bdn5veyhuhjd</link>
  <guid>https://status.soverin.net/maintenance/clul36mow44693bdn5veyhuhjd</guid>
</item>

<item>
  <title>IMAP (binnenkomende mail) outage</title>
  <description>
    Type: Incident
    Duration: 3 hours and 18 minutes

    Affected Components: IMAP (binnenkomende mail)
    Apr 5, 07:32:38 GMT+0 - Investigating - IMAP (binnenkomende mail) cannot be accessed at the moment. This incident was created by an automated monitoring service. Apr 5, 07:35:55 GMT+0 - Resolved - IMAP (binnenkomende mail) is now operational! This update was created by an automated monitoring service. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 3 hours and 18 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 5&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;07:32:38&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  IMAP (binnenkomende mail) cannot be accessed at the moment. This incident was created by an automated monitoring service..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 5&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;07:35:55&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  IMAP (binnenkomende mail) is now operational! This update was created by an automated monitoring service..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Fri, 5 Apr 2024 07:32:38 +0000</pubDate>
  <link>https://status.soverin.net/incident/clumcm3b156887kcoqdyitc3q2</link>
  <guid>https://status.soverin.net/incident/clumcm3b156887kcoqdyitc3q2</guid>
</item>

  </channel>
  </rss>