FlowSavvy Status - Incident history https://flowsavvy.instatus.com FlowSavvy Thu, 25 Dec 2025 03:10:45 +0000 Outage Type: Incident Duration: 4 hours and 29 minutes Affected Components: General Dec 25, 07:39:56 GMT+0 - Resolved - At 2025-12-25 02:59am UTC, we experienced a server issue that caused the app to be inaccessible for 13 minutes. The server was restarted, and systems have been stable for the past three hours. The issue is considered resolved at this time. We will continue monitoring and collect additional information to help identify the root cause if the issue reoccurs. Dec 26, 23:30:00 GMT+0 - Resolved - After another outage at 2025-12-25 14:29 - 14:50 UTC, we identified and fixed the root cause of the outages. Dec 25, 03:10:45 GMT+0 - Investigating - We are currently investigating this incident. Dec 25, 03:16:25 GMT+0 - Investigating - We've restarted our servers and are working to identify the issue. Dec 25, 03:33:19 GMT+0 - Monitoring - FlowSavvy has been stable since the server restart. We will continue working to identify the root cause of the outage. Type: Incident

Duration: 4 hours and 29 minutes

Affected Components:

<p><small>Dec <var data-var='date'> 25</var>, <var data-var='time'>07:39:56</var> GMT+0</small><br><strong>Resolved</strong> - At 2025-12-25 02:59am UTC, we experienced a server issue that caused the app to be inaccessible for 13 minutes. The server was restarted, and systems have been stable for the past three hours. The issue is considered resolved at this time. We will continue monitoring and collect additional information to help identify the root cause if the issue reoccurs..</p> <p><small>Dec <var data-var='date'> 26</var>, <var data-var='time'>23:30:00</var> GMT+0</small><br><strong>Resolved</strong> - After another outage at 2025-12-25 14:29 - 14:50 UTC, we identified and fixed the root cause of the outages..</p> <p><small>Dec <var data-var='date'> 25</var>, <var data-var='time'>03:10:45</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>Dec <var data-var='date'> 25</var>, <var data-var='time'>03:16:25</var> GMT+0</small><br><strong>Investigating</strong> - We've restarted our servers and are working to identify the issue..</p> <p><small>Dec <var data-var='date'> 25</var>, <var data-var='time'>03:33:19</var> GMT+0</small><br><strong>Monitoring</strong> - FlowSavvy has been stable since the server restart. We will continue working to identify the root cause of the outage..</p> ]]> Thu, 25 Dec 2025 03:10:45 +0000 https://flowsavvy.instatus.com/incident/cmjkv84vq01k9wzwyj0hsibgi https://flowsavvy.instatus.com/incident/cmjkv84vq01k9wzwyj0hsibgi Partial Outage, some services affected Type: Incident Duration: 13 hours and 48 minutes Affected Components: General Oct 20, 14:00:00 GMT+0 - Identified - AWS is experiencing a partial outage, which is affecting many of our subprocessors and systems. The following services are affected: * Payments: Our payment provider and payment tracking system provider are affected by the AWS outage, so some payments are not correctly unlocking the Pro plan. Additionally, the checkout page on desktop may not load. We will ensure all payments are correctly attributed. * Account creation: Account creation is currently failing due to the payment provider outage. * Support: Our support center service is affected by the AWS outage, so the support center may experience errors or increased latency. Please email us at [support@flowsavvy.app](mailto:support@flowsavvy.app) if you are unable to reach us through the in-app support center We are working to mitigate the issues caused by the outage and will provide an update by 1PM PDT. AWS status page: <https://health.aws.amazon.com/health/status> Oct 20, 19:53:17 GMT+0 - Monitoring - All systems have returned to operational status. We will continue monitoring the situation over the next few hours. Our payment provider is working on backfilling payment data from payments that occurred during the outage. We have recorded payments made in Stripe that were affected and will ensure they get reported and linked to the affected FlowSavvy accounts. For payments made on the App Store or Play Store during the outage, please go to your FlowSavvy "Account" settings and click "Restore purchases". If you attempted to create an account during the outage, the account was created, but the login was not working. Logging in with that same account should succeed now. Please contact [support@flowsavvy.app](mailto:support@flowsavvy.app) if you continue experiencing any issues. Oct 21, 03:47:58 GMT+0 - Resolved - This incident has been resolved. All Stripe payments that were affected by the outage have been retroactively connected to the appropriate FlowSavvy accounts. If your App Store or Play Store subscription is still not showing in your FlowSavvy account, please go to your FlowSavvy "Account" settings and click "Restore purchases". If you attempted to create an account during the outage, the account was created, but the login was not working. Logging in with that same account should succeed now. Type: Incident

Duration: 13 hours and 48 minutes

Affected Components:

<p><small>Oct <var data-var='date'> 20</var>, <var data-var='time'>14:00:00</var> GMT+0</small><br><strong>Identified</strong> - AWS is experiencing a partial outage, which is affecting many of our subprocessors and systems. The following services are affected: * Payments: Our payment provider and payment tracking system provider are affected by the AWS outage, so some payments are not correctly unlocking the Pro plan. Additionally, the checkout page on desktop may not load. We will ensure all payments are correctly attributed. * Account creation: Account creation is currently failing due to the payment provider outage. * Support: Our support center service is affected by the AWS outage, so the support center may experience errors or increased latency. Please email us at [support@flowsavvy.app](mailto:support@flowsavvy.app) if you are unable to reach us through the in-app support center We are working to mitigate the issues caused by the outage and will provide an update by 1PM PDT. AWS status page: <https://health.aws.amazon.com/health/status>.</p> <p><small>Oct <var data-var='date'> 20</var>, <var data-var='time'>19:53:17</var> GMT+0</small><br><strong>Monitoring</strong> - All systems have returned to operational status. We will continue monitoring the situation over the next few hours. Our payment provider is working on backfilling payment data from payments that occurred during the outage. We have recorded payments made in Stripe that were affected and will ensure they get reported and linked to the affected FlowSavvy accounts. For payments made on the App Store or Play Store during the outage, please go to your FlowSavvy "Account" settings and click "Restore purchases". If you attempted to create an account during the outage, the account was created, but the login was not working. Logging in with that same account should succeed now. Please contact [support@flowsavvy.app](mailto:support@flowsavvy.app) if you continue experiencing any issues..</p> <p><small>Oct <var data-var='date'> 21</var>, <var data-var='time'>03:47:58</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved. All Stripe payments that were affected by the outage have been retroactively connected to the appropriate FlowSavvy accounts. If your App Store or Play Store subscription is still not showing in your FlowSavvy account, please go to your FlowSavvy "Account" settings and click "Restore purchases". If you attempted to create an account during the outage, the account was created, but the login was not working. Logging in with that same account should succeed now..</p> ]]> Mon, 20 Oct 2025 14:00:00 +0000 https://flowsavvy.instatus.com/incident/cmgzf4zfp06fatwbp1bv19ikw https://flowsavvy.instatus.com/incident/cmgzf4zfp06fatwbp1bv19ikw General slowdown Type: Incident Duration: 5 hours and 32 minutes Affected Components: General Aug 4, 22:28:00 GMT+0 - Investigating - We are currently investigating this incident. Aug 5, 04:00:00 GMT+0 - Resolved - This incident has been resolved. Aug 4, 23:24:11 GMT+0 - Identified - We have found the issue and are working on a fix. Type: Incident

Duration: 5 hours and 32 minutes

Affected Components:

<p><small>Aug <var data-var='date'> 4</var>, <var data-var='time'>22:28:00</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>Aug <var data-var='date'> 5</var>, <var data-var='time'>04:00:00</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> <p><small>Aug <var data-var='date'> 4</var>, <var data-var='time'>23:24:11</var> GMT+0</small><br><strong>Identified</strong> - We have found the issue and are working on a fix..</p> ]]> Mon, 4 Aug 2025 22:28:00 +0000 https://flowsavvy.instatus.com/incident/cmdxpfa020igy14gh3azb7fpu https://flowsavvy.instatus.com/incident/cmdxpfa020igy14gh3azb7fpu Outlook Outage Type: Incident Duration: 2 hours Affected Components: Outlook sync Jun 12, 01:10:00 GMT+0 - Resolved - This incident has been resolved. If your Outlook sync failed during this incident, please go to Settings, then Calendars, and try restarting the sync. Jun 11, 23:10:00 GMT+0 - Investigating - Outlook authentication and syncing are not working Type: Incident

Duration: 2 hours

Affected Components:

<p><small>Jun <var data-var='date'> 12</var>, <var data-var='time'>01:10:00</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved. If your Outlook sync failed during this incident, please go to Settings, then Calendars, and try restarting the sync..</p> <p><small>Jun <var data-var='date'> 11</var>, <var data-var='time'>23:10:00</var> GMT+0</small><br><strong>Investigating</strong> - Outlook authentication and syncing are not working.</p> ]]> Wed, 11 Jun 2025 23:10:00 +0000 https://flowsavvy.instatus.com/incident/cmbspjaid000fab8nv7fl0cyc https://flowsavvy.instatus.com/incident/cmbspjaid000fab8nv7fl0cyc iOS/Android widget errors Type: Incident Duration: 1 hour and 4 minutes Affected Components: iOS/Android Widgets Jan 16, 01:43:31 GMT+0 - Resolved - This incident has been resolved. Jan 16, 00:39:48 GMT+0 - Identified - iOS/Android widgets are currently failing to load. We have identified the cause and are working on a fix. Jan 16, 00:48:45 GMT+0 - Identified - We have reverted the update that caused the issue and will re-release it once the issue has been fixed. Widgets are operational. Type: Incident

Duration: 1 hour and 4 minutes

Affected Components:

<p><small>Jan <var data-var='date'> 16</var>, <var data-var='time'>01:43:31</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> <p><small>Jan <var data-var='date'> 16</var>, <var data-var='time'>00:39:48</var> GMT+0</small><br><strong>Identified</strong> - iOS/Android widgets are currently failing to load. We have identified the cause and are working on a fix..</p> <p><small>Jan <var data-var='date'> 16</var>, <var data-var='time'>00:48:45</var> GMT+0</small><br><strong>Identified</strong> - We have reverted the update that caused the issue and will re-release it once the issue has been fixed. Widgets are operational..</p> ]]> Thu, 16 Jan 2025 00:39:48 +0000 https://flowsavvy.instatus.com/incident/cm5ylstrp003gqmmfamaa7z5e https://flowsavvy.instatus.com/incident/cm5ylstrp003gqmmfamaa7z5e iOS/Android widget errors Type: Incident Affected Components: iOS/Android Widgets Nov 7, 01:20:00 GMT+0 - Resolved - Our latest update caused the iOS and Android widgets to show an error when loading the schedule. The issue started at Nov 7 01:20 UTC and was resolved at Nov 7 02:50 UTC. Type: Incident

Affected Components:

<p><small>Nov <var data-var='date'> 7</var>, <var data-var='time'>01:20:00</var> GMT+0</small><br><strong>Resolved</strong> - Our latest update caused the iOS and Android widgets to show an error when loading the schedule. The issue started at Nov 7 01:20 UTC and was resolved at Nov 7 02:50 UTC..</p> ]]> Thu, 7 Nov 2024 01:20:00 +0000 https://flowsavvy.instatus.com/incident/cm36q1c5m0022ma8uckqt6i77 https://flowsavvy.instatus.com/incident/cm36q1c5m0022ma8uckqt6i77 Outage Type: Incident Duration: 8 hours and 35 minutes Affected Components: General Sep 12, 19:43:59 GMT+0 - Investigating - We are currently investigating this incident. Sep 12, 20:31:09 GMT+0 - Monitoring - FlowSavvy is back up and we are monitoring the status and working to identify the root cause Sep 13, 01:28:33 GMT+0 - Identified - All FlowSavvy systems have been stable since the short outage around 4 hours ago. However, we have now identified the root cause of the outage and are working on a fix. Sep 13, 04:18:49 GMT+0 - Resolved - The root cause has been identified and fixed Type: Incident

Duration: 8 hours and 35 minutes

Affected Components:

<p><small>Sep <var data-var='date'> 12</var>, <var data-var='time'>19:43:59</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>Sep <var data-var='date'> 12</var>, <var data-var='time'>20:31:09</var> GMT+0</small><br><strong>Monitoring</strong> - FlowSavvy is back up and we are monitoring the status and working to identify the root cause.</p> <p><small>Sep <var data-var='date'> 13</var>, <var data-var='time'>01:28:33</var> GMT+0</small><br><strong>Identified</strong> - All FlowSavvy systems have been stable since the short outage around 4 hours ago. However, we have now identified the root cause of the outage and are working on a fix..</p> <p><small>Sep <var data-var='date'> 13</var>, <var data-var='time'>04:18:49</var> GMT+0</small><br><strong>Resolved</strong> - The root cause has been identified and fixed.</p> ]]> Thu, 12 Sep 2024 19:43:59 +0000 https://flowsavvy.instatus.com/incident/cm0zp6vrb000ek8x7tt9umwe4 https://flowsavvy.instatus.com/incident/cm0zp6vrb000ek8x7tt9umwe4 Outage Type: Incident Duration: 1 hour and 42 minutes Affected Components: General Aug 31, 21:13:18 GMT+0 - Resolved - All systems are operational. Aug 31, 19:30:55 GMT+0 - Investigating - FlowSavvy is currently not loading on all platforms. We are currently investigating this incident and will update as soon as possible. Aug 31, 19:39:49 GMT+0 - Monitoring - The issue appears to have been resolved. We will continue monitoring FlowSavvy's status and investigating the cause of the outage. Type: Incident

Duration: 1 hour and 42 minutes

Affected Components:

<p><small>Aug <var data-var='date'> 31</var>, <var data-var='time'>21:13:18</var> GMT+0</small><br><strong>Resolved</strong> - All systems are operational..</p> <p><small>Aug <var data-var='date'> 31</var>, <var data-var='time'>19:30:55</var> GMT+0</small><br><strong>Investigating</strong> - FlowSavvy is currently not loading on all platforms. We are currently investigating this incident and will update as soon as possible..</p> <p><small>Aug <var data-var='date'> 31</var>, <var data-var='time'>19:39:49</var> GMT+0</small><br><strong>Monitoring</strong> - The issue appears to have been resolved. We will continue monitoring FlowSavvy's status and investigating the cause of the outage..</p> ]]> Sat, 31 Aug 2024 19:30:55 +0000 https://flowsavvy.instatus.com/incident/cm0ijfwcp00akmjaoifhtxr39 https://flowsavvy.instatus.com/incident/cm0ijfwcp00akmjaoifhtxr39 Task Creation/Completion is Erroring Type: Incident Duration: 27 minutes Affected Components: General May 28, 23:08:00 GMT+0 - Investigating - Multiple actions involving tasks such as creating, completing, and editing are erroring. We are investigating the issue and will provide a fix as soon as possible. We apologize for the inconvenience. May 28, 23:16:58 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. May 28, 23:35:10 GMT+0 - Resolved - This issue has been resolved. Type: Incident

Duration: 27 minutes

Affected Components:

<p><small>May <var data-var='date'> 28</var>, <var data-var='time'>23:08:00</var> GMT+0</small><br><strong>Investigating</strong> - Multiple actions involving tasks such as creating, completing, and editing are erroring. We are investigating the issue and will provide a fix as soon as possible. We apologize for the inconvenience..</p> <p><small>May <var data-var='date'> 28</var>, <var data-var='time'>23:16:58</var> GMT+0</small><br><strong>Monitoring</strong> - We implemented a fix and are currently monitoring the result..</p> <p><small>May <var data-var='date'> 28</var>, <var data-var='time'>23:35:10</var> GMT+0</small><br><strong>Resolved</strong> - This issue has been resolved..</p> ]]> Tue, 28 May 2024 23:08:00 +0000 https://flowsavvy.instatus.com/incident/clwr0d4sw38744bfodwf70wb8b https://flowsavvy.instatus.com/incident/clwr0d4sw38744bfodwf70wb8b Degraded performance / Calendar syncing disabled Type: Incident Duration: 1 day, 5 hours and 30 minutes Affected Components: Google Calendar sync, Outlook sync, General, iCloud sync Jan 18, 22:50:27 GMT+0 - Investigating - We are investigating an issue causing slow performance and syncing. Jan 18, 23:26:57 GMT+0 - Investigating - Calendar syncing appears to be a large contributor to the slow performance. We have temporarily disabled Google, iCloud, and Outlook syncing while we investigate the issue. Jan 19, 00:23:48 GMT+0 - Identified - We have identified the root cause of the performance issues and are working on a fix. Performance has returned to normal for all services except calendar syncing, which will remain disabled until the fix is complete. We will provide periodic status updates. In the meantime, we recommend reviewing your external calendars (Google, iCloud, Outlook) to ensure you don't miss meetings. Thank you for your patience! Jan 19, 18:12:50 GMT+0 - Identified - Enabling syncing caused the performance issues to return, so we have disabled syncing again. We apologize for the inconvenience and will provide a status update by 4pm EST (9pm UTC) Jan 19, 18:00:49 GMT+0 - Monitoring - Syncing has been re-enabled and all services are operational. Please go to Settings > Calendars and select "Try again" to re-activate syncing. We will continue monitoring performance over the next few hours before marking this incident as resolved. Jan 20, 01:52:00 GMT+0 - Monitoring - Syncing has been re-enabled. We will continue monitoring performance over the next few hours before marking this incident as resolved. Note: If your sync failed earlier before we disabled all syncing, you may need to re-activate syncing by going to Settings > Calendars and selecting "Try again". Jan 20, 00:29:06 GMT+0 - Identified - We are working on scaling our systems to accommodate increased sync load. This will include a brief window (less than 5 minutes) during which FlowSavvy will be unavailable while we scale our systems. This brief downtime will occur between 8-8:30pm EST (1-1:30am UTC). Jan 19, 21:00:35 GMT+0 - Identified - We have identified the root cause of the slow performance and are working on a fix. Calendar syncing will remain disabled until the fix is complete. We will provide an update by 7pm EST (12am UTC) Jan 20, 04:20:01 GMT+0 - Resolved - This issue has been resolved Type: Incident

Duration: 1 day, 5 hours and 30 minutes

Affected Components: , , ,

<p><small>Jan <var data-var='date'> 18</var>, <var data-var='time'>22:50:27</var> GMT+0</small><br><strong>Investigating</strong> - We are investigating an issue causing slow performance and syncing..</p> <p><small>Jan <var data-var='date'> 18</var>, <var data-var='time'>23:26:57</var> GMT+0</small><br><strong>Investigating</strong> - Calendar syncing appears to be a large contributor to the slow performance. We have temporarily disabled Google, iCloud, and Outlook syncing while we investigate the issue..</p> <p><small>Jan <var data-var='date'> 19</var>, <var data-var='time'>00:23:48</var> GMT+0</small><br><strong>Identified</strong> - We have identified the root cause of the performance issues and are working on a fix. Performance has returned to normal for all services except calendar syncing, which will remain disabled until the fix is complete. We will provide periodic status updates. In the meantime, we recommend reviewing your external calendars (Google, iCloud, Outlook) to ensure you don't miss meetings. Thank you for your patience!.</p> <p><small>Jan <var data-var='date'> 19</var>, <var data-var='time'>18:12:50</var> GMT+0</small><br><strong>Identified</strong> - Enabling syncing caused the performance issues to return, so we have disabled syncing again. We apologize for the inconvenience and will provide a status update by 4pm EST (9pm UTC).</p> <p><small>Jan <var data-var='date'> 19</var>, <var data-var='time'>18:00:49</var> GMT+0</small><br><strong>Monitoring</strong> - Syncing has been re-enabled and all services are operational. Please go to Settings > Calendars and select "Try again" to re-activate syncing. We will continue monitoring performance over the next few hours before marking this incident as resolved..</p> <p><small>Jan <var data-var='date'> 20</var>, <var data-var='time'>01:52:00</var> GMT+0</small><br><strong>Monitoring</strong> - Syncing has been re-enabled. We will continue monitoring performance over the next few hours before marking this incident as resolved. Note: If your sync failed earlier before we disabled all syncing, you may need to re-activate syncing by going to Settings > Calendars and selecting "Try again"..</p> <p><small>Jan <var data-var='date'> 20</var>, <var data-var='time'>00:29:06</var> GMT+0</small><br><strong>Identified</strong> - We are working on scaling our systems to accommodate increased sync load. This will include a brief window (less than 5 minutes) during which FlowSavvy will be unavailable while we scale our systems. This brief downtime will occur between 8-8:30pm EST (1-1:30am UTC)..</p> <p><small>Jan <var data-var='date'> 19</var>, <var data-var='time'>21:00:35</var> GMT+0</small><br><strong>Identified</strong> - We have identified the root cause of the slow performance and are working on a fix. Calendar syncing will remain disabled until the fix is complete. We will provide an update by 7pm EST (12am UTC).</p> <p><small>Jan <var data-var='date'> 20</var>, <var data-var='time'>04:20:01</var> GMT+0</small><br><strong>Resolved</strong> - This issue has been resolved.</p> ]]> Thu, 18 Jan 2024 22:50:27 +0000 https://flowsavvy.instatus.com/incident/clrjt1zt634100bmo5driwb9ll https://flowsavvy.instatus.com/incident/clrjt1zt634100bmo5driwb9ll Intermittent Server Outages Type: Incident Duration: 3 hours and 15 minutes Affected Components: General Jan 8, 04:05:00 GMT+0 - Investigating - FlowSavvy is experiencing an outage that started at approximately 4:05AM UTC. We are investigating the issue and will provide an update here as soon as possible. We apologize for any inconvenience this may cause. Jan 8, 04:50:00 GMT+0 - Investigating - Services are back to operational status. However, we are still investigating the root cause of the outage. The severity level has been lowered to "partial outage" to indicate potential intermittent interruptions until the root cause is identified and resolved. Jan 8, 07:20:00 GMT+0 - Resolved - The issue causing the outages has been isolated to prevent further outages. Marking this incident as resolved as services are fully operational, though we will continue working on a fix for the root cause. Type: Incident

Duration: 3 hours and 15 minutes

Affected Components:

<p><small>Jan <var data-var='date'> 8</var>, <var data-var='time'>04:05:00</var> GMT+0</small><br><strong>Investigating</strong> - FlowSavvy is experiencing an outage that started at approximately 4:05AM UTC. We are investigating the issue and will provide an update here as soon as possible. We apologize for any inconvenience this may cause..</p> <p><small>Jan <var data-var='date'> 8</var>, <var data-var='time'>04:50:00</var> GMT+0</small><br><strong>Investigating</strong> - Services are back to operational status. However, we are still investigating the root cause of the outage. The severity level has been lowered to "partial outage" to indicate potential intermittent interruptions until the root cause is identified and resolved..</p> <p><small>Jan <var data-var='date'> 8</var>, <var data-var='time'>07:20:00</var> GMT+0</small><br><strong>Resolved</strong> - The issue causing the outages has been isolated to prevent further outages. Marking this incident as resolved as services are fully operational, though we will continue working on a fix for the root cause..</p> ]]> Mon, 8 Jan 2024 04:05:00 +0000 https://flowsavvy.instatus.com/incident/clr4fe1gq163350bin9uzpxqplk https://flowsavvy.instatus.com/incident/clr4fe1gq163350bin9uzpxqplk Intermittent issues Type: Incident Duration: 1 hour and 5 minutes Affected Components: General Oct 31, 17:55:21 GMT+0 - Investigating - We are currently investigating an issue causing intermittent failures. Users may experience degraded performance or failed requests in any area of the app. We recommend refreshing the page (or restarting the app) if you experience degraded performance or errors. Oct 31, 19:00:00 GMT+0 - Resolved - This incident has been resolved and appears to have only affected requests from 10:14-10:17am PST (17:14-17:17 UTC). We will continue making performance optimizations to mitigate issues like this. Type: Incident

Duration: 1 hour and 5 minutes

Affected Components:

<p><small>Oct <var data-var='date'> 31</var>, <var data-var='time'>17:55:21</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating an issue causing intermittent failures. Users may experience degraded performance or failed requests in any area of the app. We recommend refreshing the page (or restarting the app) if you experience degraded performance or errors..</p> <p><small>Oct <var data-var='date'> 31</var>, <var data-var='time'>19:00:00</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved and appears to have only affected requests from 10:14-10:17am PST (17:14-17:17 UTC). We will continue making performance optimizations to mitigate issues like this..</p> ]]> Tue, 31 Oct 2023 17:55:21 +0000 https://flowsavvy.instatus.com/incident/cloemq5x215978booc77p9cwyz https://flowsavvy.instatus.com/incident/cloemq5x215978booc77p9cwyz New Status Page Type: Incident Affected Components: iCloud sync, Google Calendar sync, iOS/Android Widgets, Push Notifications, Outlook sync Oct 30, 15:34:33 GMT+0 - Resolved - Welcome to our new status page! Starting today (Oct 30), we'll provide updates on incidents here. Type: Incident

Affected Components: , , , ,

<p><small>Oct <var data-var='date'> 30</var>, <var data-var='time'>15:34:33</var> GMT+0</small><br><strong>Resolved</strong> - Welcome to our new status page! Starting today (Oct 30), we'll provide updates on incidents here..</p> ]]> Mon, 30 Oct 2023 15:34:33 +0000 https://flowsavvy.instatus.com/incident/clod2990035070brn2rknfgb0i https://flowsavvy.instatus.com/incident/clod2990035070brn2rknfgb0i