<?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>Aqua Voice Status - Incident history</title>
    <link>https://status.withaqua.com</link>
    <description>Aqua Voice</description>
    <pubDate>Wed, 13 Aug 2025 15:03:00 +0000</pubDate>
    
<item>
  <title>Aqua Desktop timing out</title>
  <description>
    Type: Incident
    Duration: 22 minutes

    Affected Components: Desktop (Windows), Desktop (macOS)
    Aug 13, 15:03:00 GMT+0 - Investigating - Aqua Desktop timing out. Aug 13, 15:25:00 GMT+0 - Resolved - This incident has been resolved. Root cause under investigation. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 22 minutes</p>
    <p><strong>Affected Components:</strong> , </p>
    &lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 13&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;15:03:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  Aqua Desktop timing out..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 13&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;15:25:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved. Root cause under investigation..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Wed, 13 Aug 2025 15:03:00 +0000</pubDate>
  <link>https://status.withaqua.com/incident/cmea8bpvt000yy5ytbxafdkhb</link>
  <guid>https://status.withaqua.com/incident/cmea8bpvt000yy5ytbxafdkhb</guid>
</item>

<item>
  <title>Users cannot log in</title>
  <description>
    Type: Incident
    Duration: 4 minutes

    Affected Components: Website, Desktop (Windows), Desktop (macOS)
    Aug 4, 21:28:12 GMT+0 - Investigating - We are currently investigating this incident. Aug 4, 21:31:48 GMT+0 - Resolved - This incident has been resolved. 
  </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;Aug &lt;var data-var=&#039;date&#039;&gt; 4&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;21:28:12&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;Aug &lt;var data-var=&#039;date&#039;&gt; 4&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;21:31:48&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>Mon, 4 Aug 2025 21:28:12 +0000</pubDate>
  <link>https://status.withaqua.com/incident/cmdxmgn2g01jkc69k9b6ykhi6</link>
  <guid>https://status.withaqua.com/incident/cmdxmgn2g01jkc69k9b6ykhi6</guid>
</item>

<item>
  <title>Users could not start sessions due to a failed migration. </title>
  <description>
    Type: Incident
    Duration: 10 minutes

    Affected Components: Desktop (Windows), Desktop (macOS)
    Jun 21, 02:16:52 GMT+0 - Resolved - This incident has been resolved.  
  
A migration failed during one of our deployments.  Jun 21, 02:07:01 GMT+0 - Investigating - We are currently investigating this incident. Jun 21, 02:46:44 GMT+0 - Postmortem - After the previous deployment problem, we made a ton of upgrades to ensure deployments wouldn&#039;t take down the service for people. More redundancy. Blue-green deployments. More and better tests.   

That had been working well... but rolling out this batch of changes caused a bunch of database connections to have invalid caches while a migration was applying. That broke auth with a cascade of &#039;cached plan must not change result type&#039; errors.  
  
**Impact**  
Aqua was totally down for 10 to 15 minutes.   
  
**Fixes**  
No more yolo migrations. Deployment synchronization. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 10 minutes</p>
    <p><strong>Affected Components:</strong> , </p>
    &lt;p&gt;&lt;small&gt;Jun &lt;var data-var=&#039;date&#039;&gt; 21&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;02:16:52&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved.  
  
A migration failed during one of our deployments. .&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jun &lt;var data-var=&#039;date&#039;&gt; 21&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;02:07:01&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;Jun &lt;var data-var=&#039;date&#039;&gt; 21&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;02:46:44&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Postmortem&lt;/strong&gt; -
  After the previous deployment problem, we made a ton of upgrades to ensure deployments wouldn&#039;t take down the service for people. More redundancy. Blue-green deployments. More and better tests.   

That had been working well... but rolling out this batch of changes caused a bunch of database connections to have invalid caches while a migration was applying. That broke auth with a cascade of &#039;cached plan must not change result type&#039; errors.  
  
**Impact**  
Aqua was totally down for 10 to 15 minutes.   
  
**Fixes**  
No more yolo migrations. Deployment synchronization..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Sat, 21 Jun 2025 02:07:01 +0000</pubDate>
  <link>https://status.withaqua.com/incident/cmc5llv84001xf68tq8y2k3y0</link>
  <guid>https://status.withaqua.com/incident/cmc5llv84001xf68tq8y2k3y0</guid>
</item>

<item>
  <title>Users could not log in while backend changes were applying (~10min)</title>
  <description>
    Type: Incident
    Duration: 6 minutes

    Affected Components: Website, Desktop (Windows), Desktop (macOS)
    May 13, 21:18:19 GMT+0 - Resolved - This incident has been resolved. May 13, 21:12:24 GMT+0 - Identified - We are continuing to work on a fix for this incident. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 6 minutes</p>
    <p><strong>Affected Components:</strong> , , </p>
    &lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 13&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;21:18:19&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;May &lt;var data-var=&#039;date&#039;&gt; 13&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;21:12:24&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;
]]>
  </content:encoded>
  <pubDate>Tue, 13 May 2025 21:12:24 +0000</pubDate>
  <link>https://status.withaqua.com/incident/cman0cmrx003o9ekllgb24ymt</link>
  <guid>https://status.withaqua.com/incident/cman0cmrx003o9ekllgb24ymt</guid>
</item>

<item>
  <title>Increased latency on paste</title>
  <description>
    Type: Incident
    Duration: 1 hour and 55 minutes

    Affected Components: Desktop (Windows), Desktop (macOS)
    Apr 28, 20:48:15 GMT+0 - Resolved - This incident has been resolved. Apr 28, 18:53:42 GMT+0 - Identified - We are continuing to work on a fix for this incident. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 55 minutes</p>
    <p><strong>Affected Components:</strong> , </p>
    &lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 28&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;20:48:15&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;Apr &lt;var data-var=&#039;date&#039;&gt; 28&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;18:53:42&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;
]]>
  </content:encoded>
  <pubDate>Mon, 28 Apr 2025 18:53:42 +0000</pubDate>
  <link>https://status.withaqua.com/incident/cma1fshrp002s13zjjj1crtdf</link>
  <guid>https://status.withaqua.com/incident/cma1fshrp002s13zjjj1crtdf</guid>
</item>

  </channel>
  </rss>