<?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>Swivro Status - Incident history</title>
    <link>https://swivro.instatus.com</link>
    <description>Swivro</description>
    <pubDate>Sat, 7 Aug 2021 05:35:39 +0000</pubDate>
    
<item>
  <title>DirectAdmin Inaccessibility </title>
  <description>
    Type: Incident
    

    Affected Components: DirectAdmin Server 13
    Aug 7, 05:35:39 GMT+0 - Resolved - As reported by our users, the issue looks to be resolved and the software misconfiguration has been fixed. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 7&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;05:35:39&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  As reported by our users, the issue looks to be resolved and the software misconfiguration has been fixed..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Sat, 7 Aug 2021 05:35:39 +0000</pubDate>
  <link>https://swivro.instatus.com/incident/cks1ch4zo200597kn07unq1lhp</link>
  <guid>https://swivro.instatus.com/incident/cks1ch4zo200597kn07unq1lhp</guid>
</item>

<item>
  <title>Website Migration [Potential Inaccessibility]</title>
  <description>
    Type: Incident
    Duration: 4 minutes

    Affected Components: Home Website
    Jun 27, 04:03:33 GMT+0 - Monitoring - We are currently monitoring the migration process of our homepage. We migrated our files to a new server on a new domain name and are awaiting the result which we expect to come shortly. Jun 27, 04:07:19 GMT+0 - Resolved - We have finished server migration and luckily minimal downtime was experienced, of less than 60 seconds. Thanks to CloudFlare&#039;s Always Live and Cache CDN, our website did not experience even more prolonged downtime. Thank you for understanding. 
  </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; 27&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;04:03:33&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  We are currently monitoring the migration process of our homepage. We migrated our files to a new server on a new domain name and are awaiting the result which we expect to come shortly..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jun &lt;var data-var=&#039;date&#039;&gt; 27&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;04:07:19&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  We have finished server migration and luckily minimal downtime was experienced, of less than 60 seconds. Thanks to CloudFlare&#039;s Always Live and Cache CDN, our website did not experience even more prolonged downtime. Thank you for understanding..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Sun, 27 Jun 2021 04:03:33 +0000</pubDate>
  <link>https://swivro.instatus.com/incident/ckqeo4efk5961579jn6bt1vrrwt</link>
  <guid>https://swivro.instatus.com/incident/ckqeo4efk5961579jn6bt1vrrwt</guid>
</item>

<item>
  <title>Email Support Messages Delayed</title>
  <description>
    Type: Incident
    Duration: 28 minutes

    Affected Components: Email Support
    Jun 26, 23:10:55 GMT+0 - Investigating - Users that attempt to contact us via our sales or support email (sales@swivro.com or support@swivro.com) will not receive a response at this time, as we currently are not able to receive new messages. We are currently investigating this incident. Jun 26, 23:13:55 GMT+0 - Identified - We are continuing to work on a fix for this incident. We have identified the issue, being a conflict with our Email Forwarding Service Provider. We are in contact with the company and are working to resolve this issue ASAP. Jun 26, 23:28:58 GMT+0 - Monitoring - We implemented a fix and currently monitoring the result. The issue discovered was a conflict with multiple faulty MX Records being automatically created. Jun 26, 23:33:12 GMT+0 - Monitoring - We previously implemented a fix and was monitoring the result, but it does appear that the fix which was implemented is not taking effect. The team associated with this issue type continues to work to resolve this issue as fast as they can. Updates will continue to be provided here. Jun 26, 23:38:40 GMT+0 - Resolved - The issue has been fully resolved and we are now receiving emails to all of our support emails. Thank you for understanding. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 28 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Jun &lt;var data-var=&#039;date&#039;&gt; 26&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;23:10:55&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  Users that attempt to contact us via our sales or support email (sales@swivro.com or support@swivro.com) will not receive a response at this time, as we currently are not able to receive new messages. We are currently investigating this incident..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jun &lt;var data-var=&#039;date&#039;&gt; 26&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;23:13:55&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. We have identified the issue, being a conflict with our Email Forwarding Service Provider. We are in contact with the company and are working to resolve this issue ASAP..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jun &lt;var data-var=&#039;date&#039;&gt; 26&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;23:28:58&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  We implemented a fix and currently monitoring the result. The issue discovered was a conflict with multiple faulty MX Records being automatically created..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jun &lt;var data-var=&#039;date&#039;&gt; 26&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;23:33:12&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  We previously implemented a fix and was monitoring the result, but it does appear that the fix which was implemented is not taking effect. The team associated with this issue type continues to work to resolve this issue as fast as they can. Updates will continue to be provided here..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jun &lt;var data-var=&#039;date&#039;&gt; 26&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;23:38:40&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  The issue has been fully resolved and we are now receiving emails to all of our support emails. Thank you for understanding..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Sat, 26 Jun 2021 23:10:55 +0000</pubDate>
  <link>https://swivro.instatus.com/incident/ckqedorkk25839598n0f7vnn6y2</link>
  <guid>https://swivro.instatus.com/incident/ckqedorkk25839598n0f7vnn6y2</guid>
</item>

<item>
  <title>Server Disk Upgrades [Causing Downtime]</title>
  <description>
    Type: Incident
    

    Affected Components: DirectAdmin Server 13, DirectAdmin Server 5
    Jun 16, 00:44:19 GMT+0 - Resolved - Server upgrades have been completed and all services are now operational. 
  </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; 16&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;00:44:19&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  Server upgrades have been completed and all services are now operational..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Wed, 16 Jun 2021 00:44:19 +0000</pubDate>
  <link>https://swivro.instatus.com/incident/ckpyr5r6g86785a3ogiii5b9st</link>
  <guid>https://swivro.instatus.com/incident/ckpyr5r6g86785a3ogiii5b9st</guid>
</item>

  </channel>
  </rss>