flok Status - Incident history https://status.flok.org flok Mon, 11 May 2026 19:30:00 +0000 Issues with login and loss of database connection Type: Incident Duration: 1 day, 22 hours and 54 minutes Affected Components: App May 12, 20:30:11 GMT+0 - Monitoring - **Recent flok app login bugs have been resolved.** Thank you for your patience – We sincerely apologize for the disruption. There were bugs in the update published Monday 5/11 that caused login errors, database sync issues, favorites not displaying correctly, and food log history not showing up. These are now resolved: Please quit and relaunch the flok app. If you're still stuck after that, uninstalling and reinstalling should get you back in. \* If you are still experiencing any issues or need help getting back in, please reach out to support via the chat bot or [support@flok.org](mailto:support@flok.org) and we will be happy to assist. Again, we apologize for the inconvenience, and we understand your frustration: many of us at flok use the app ourselves or for our loved ones, and we were right there with you. We’ve all come to rely on these tools, and when they stop working, it’s stressful. Thank you for your patience and understanding. \- The flok team \* The only remaining issue is for those who use “Login with google” or “Login with Apple.” If you use one of these services, please tap “forget password” and enter your Google or Apple email address and log in using that email & your new password. We'll update you when this is resolved. If you experience service interruptions in the future, you can find status updates here: <https://status.flok.org> May 11, 19:30:00 GMT+0 - Investigating - ​We are working as fast as we can to resolve the issue but it appears the only thing working is to uninstall and reinstall, and there does appear to be an issue with the google login widget, we are working on that as quickly as possible. ​ If you are logging in with Google please try username and password. May 11, 23:13:28 GMT+0 - Investigating - We are currently investigating this incident, your data is still safe in the flok database. May 13, 18:23:57 GMT+0 - Resolved - **This incident is fully resolved.** The issues introduced in the May 11 update — including login errors, database sync issues, favorites not displaying, and food log history not showing — were resolved earlier this week. The last remaining item, Google and Apple login, is now also fully restored. If you're still experiencing any issues, please reach out via the in-app chat or at [support@flok.org](mailto:support@flok.org). — The flok team Type: Incident

Duration: 1 day, 22 hours and 54 minutes

Affected Components:

<p><small>May <var data-var='date'> 12</var>, <var data-var='time'>20:30:11</var> GMT+0</small><br><strong>Monitoring</strong> - **Recent flok app login bugs have been resolved.** Thank you for your patience – We sincerely apologize for the disruption. There were bugs in the update published Monday 5/11 that caused login errors, database sync issues, favorites not displaying correctly, and food log history not showing up. These are now resolved: Please quit and relaunch the flok app. If you're still stuck after that, uninstalling and reinstalling should get you back in. \* If you are still experiencing any issues or need help getting back in, please reach out to support via the chat bot or [support@flok.org](mailto:support@flok.org) and we will be happy to assist. Again, we apologize for the inconvenience, and we understand your frustration: many of us at flok use the app ourselves or for our loved ones, and we were right there with you. We’ve all come to rely on these tools, and when they stop working, it’s stressful. Thank you for your patience and understanding. \- The flok team \* The only remaining issue is for those who use “Login with google” or “Login with Apple.” If you use one of these services, please tap “forget password” and enter your Google or Apple email address and log in using that email & your new password. We'll update you when this is resolved. If you experience service interruptions in the future, you can find status updates here: <https://status.flok.org>.</p> <p><small>May <var data-var='date'> 11</var>, <var data-var='time'>19:30:00</var> GMT+0</small><br><strong>Investigating</strong> - ​We are working as fast as we can to resolve the issue but it appears the only thing working is to uninstall and reinstall, and there does appear to be an issue with the google login widget, we are working on that as quickly as possible. ​ If you are logging in with Google please try username and password..</p> <p><small>May <var data-var='date'> 11</var>, <var data-var='time'>23:13:28</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident, your data is still safe in the flok database..</p> <p><small>May <var data-var='date'> 13</var>, <var data-var='time'>18:23:57</var> GMT+0</small><br><strong>Resolved</strong> - **This incident is fully resolved.** The issues introduced in the May 11 update — including login errors, database sync issues, favorites not displaying, and food log history not showing — were resolved earlier this week. The last remaining item, Google and Apple login, is now also fully restored. If you're still experiencing any issues, please reach out via the in-app chat or at [support@flok.org](mailto:support@flok.org). — The flok team.</p> ]]> Mon, 11 May 2026 19:30:00 +0000 https://status.flok.org/incident/cmp1umpc706qiugttn42i9dd5 https://status.flok.org/incident/cmp1umpc706qiugttn42i9dd5 Can't access food database Type: Incident Affected Components: App Dec 2, 18:07:00 GMT+0 - Resolved - This incident has been resolved. Users cannot access their foods or food details. Type: Incident

Affected Components:

<p><small>Dec <var data-var='date'> 2</var>, <var data-var='time'>18:07:00</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved. Users cannot access their foods or food details..</p> ]]> Mon, 2 Dec 2024 18:07:00 +0000 https://status.flok.org/incident/cm47h475q002je8iwarn0pbgc https://status.flok.org/incident/cm47h475q002je8iwarn0pbgc flok App Service Impact due to Microsoft Azure outage Type: Incident Duration: 6 hours and 15 minutes Affected Components: App Jul 18, 23:18:00 GMT+0 - Investigating - flok is aware of an issue where the flok app often spins while loading and then fails to load data. Data is not gone, but the service is currently experiencing an outage due to dependent issues in Azure. We are monitoring this issue with Microsoft @ <https://app.azure.com/h/HS91-NQ8/92d883> and will provide and update. Jul 19, 02:03:18 GMT+0 - Identified - Azure has updated that root cause of the issue has been identified, and incremental resolution is likely within 90 mins. We are continuing to monitor and will update when resolved. Jul 19, 02:49:09 GMT+0 - Monitoring - Azure has mitigated the issue and we are seeing the app return results and function as expected now. We will continue to monitor before closing this incident. Thank you everyone for you patience. Jul 19, 05:33:22 GMT+0 - Resolved - This incident has been resolved. Azure has successfully recovered the services we depend on, and has closed their incident. Type: Incident

Duration: 6 hours and 15 minutes

Affected Components:

<p><small>Jul <var data-var='date'> 18</var>, <var data-var='time'>23:18:00</var> GMT+0</small><br><strong>Investigating</strong> - flok is aware of an issue where the flok app often spins while loading and then fails to load data. Data is not gone, but the service is currently experiencing an outage due to dependent issues in Azure. We are monitoring this issue with Microsoft @ <https://app.azure.com/h/HS91-NQ8/92d883> and will provide and update..</p> <p><small>Jul <var data-var='date'> 19</var>, <var data-var='time'>02:03:18</var> GMT+0</small><br><strong>Identified</strong> - Azure has updated that root cause of the issue has been identified, and incremental resolution is likely within 90 mins. We are continuing to monitor and will update when resolved..</p> <p><small>Jul <var data-var='date'> 19</var>, <var data-var='time'>02:49:09</var> GMT+0</small><br><strong>Monitoring</strong> - Azure has mitigated the issue and we are seeing the app return results and function as expected now. We will continue to monitor before closing this incident. Thank you everyone for you patience. .</p> <p><small>Jul <var data-var='date'> 19</var>, <var data-var='time'>05:33:22</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved. Azure has successfully recovered the services we depend on, and has closed their incident..</p> ]]> Thu, 18 Jul 2024 23:18:00 +0000 https://status.flok.org/incident/clyry34o797419hjofdzoodxi0 https://status.flok.org/incident/clyry34o797419hjofdzoodxi0 Internal Rollout for Flight One Type: Maintenance Duration: 2 hours Affected Components: Website, App Jul 21, 21:30:01 GMT+0 - Identified - Maintenance is now in progress Jul 21, 21:30:00 GMT+0 - Identified - We are planning for a scheduled maintenance during that time. Jul 21, 23:30:00 GMT+0 - Completed - Maintenance has completed successfully Type: Maintenance

Duration: 2 hours

Affected Components: ,

<p><small>Jul <var data-var='date'> 21</var>, <var data-var='time'>21:30:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> <p><small>Jul <var data-var='date'> 21</var>, <var data-var='time'>21:30:00</var> GMT+0</small><br><strong>Identified</strong> - We are planning for a scheduled maintenance during that time..</p> <p><small>Jul <var data-var='date'> 21</var>, <var data-var='time'>23:30:00</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully.</p> ]]> Fri, 21 Jul 2023 21:30:00 +0000 https://status.flok.org/maintenance/clk38migy66463bioapgo3wi0l https://status.flok.org/maintenance/clk38migy66463bioapgo3wi0l flok Investigating Type: Incident Duration: 43 minutes Affected Components: Website May 3, 17:37:21 GMT+0 - Resolved - This incident has been resolved. May 3, 17:36:39 GMT+0 - Investigating - We are currently investigating this incident. Type: Incident

Duration: 43 minutes

Affected Components:

<p><small>May <var data-var='date'> 3</var>, <var data-var='time'>17:37:21</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> <p><small>May <var data-var='date'> 3</var>, <var data-var='time'>17:36:39</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> ]]> Wed, 3 May 2023 17:36:39 +0000 https://status.flok.org/incident/clh7zcxpf66062imodui4kw1by https://status.flok.org/incident/clh7zcxpf66062imodui4kw1by flok Investigating Type: Incident Duration: 50 minutes Affected Components: Website May 3, 15:22:29 GMT+0 - Investigating - We are currently investigating this incident. May 3, 15:23:18 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 50 minutes

Affected Components:

<p><small>May <var data-var='date'> 3</var>, <var data-var='time'>15:22:29</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>May <var data-var='date'> 3</var>, <var data-var='time'>15:23:18</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Wed, 3 May 2023 15:22:29 +0000 https://status.flok.org/incident/clh7uke8o12412ieohesgwexnd https://status.flok.org/incident/clh7uke8o12412ieohesgwexnd flok Investigating Type: Incident Duration: 1 hour and 2 minutes Affected Components: Website Apr 20, 12:05:18 GMT+0 - Investigating - We are currently investigating this incident. Apr 20, 12:06:19 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 1 hour and 2 minutes

Affected Components:

<p><small>Apr <var data-var='date'> 20</var>, <var data-var='time'>12:05:18</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>Apr <var data-var='date'> 20</var>, <var data-var='time'>12:06:19</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Thu, 20 Apr 2023 12:05:18 +0000 https://status.flok.org/incident/clgp2srct1141780i9ogr9w250pr https://status.flok.org/incident/clgp2srct1141780i9ogr9w250pr flok Investigating Type: Incident Duration: 1 hour and 2 minutes Affected Components: Website Apr 20, 06:04:18 GMT+0 - Investigating - We are currently investigating this incident. Apr 20, 06:05:20 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 1 hour and 2 minutes

Affected Components:

<p><small>Apr <var data-var='date'> 20</var>, <var data-var='time'>06:04:18</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>Apr <var data-var='date'> 20</var>, <var data-var='time'>06:05:20</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Thu, 20 Apr 2023 06:04:18 +0000 https://status.flok.org/incident/clgopwi81621343ieok13iiezwf https://status.flok.org/incident/clgopwi81621343ieok13iiezwf flok Investigating Type: Incident Duration: 3 hours and 56 minutes Affected Components: Website Apr 19, 18:06:38 GMT+0 - Investigating - We are currently investigating this incident. Apr 19, 18:10:33 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 3 hours and 56 minutes

Affected Components:

<p><small>Apr <var data-var='date'> 19</var>, <var data-var='time'>18:06:38</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>Apr <var data-var='date'> 19</var>, <var data-var='time'>18:10:33</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Wed, 19 Apr 2023 18:06:38 +0000 https://status.flok.org/incident/clgo09kg3150937ihogj7bvcdsu https://status.flok.org/incident/clgo09kg3150937ihogj7bvcdsu flok Investigating Type: Incident Duration: 3 hours and 55 minutes Affected Components: Website Apr 18, 11:45:32 GMT+0 - Resolved - This incident has been resolved. Apr 18, 11:41:37 GMT+0 - Investigating - We are currently investigating this incident. Type: Incident

Duration: 3 hours and 55 minutes

Affected Components:

<p><small>Apr <var data-var='date'> 18</var>, <var data-var='time'>11:45:32</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> <p><small>Apr <var data-var='date'> 18</var>, <var data-var='time'>11:41:37</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> ]]> Tue, 18 Apr 2023 11:41:37 +0000 https://status.flok.org/incident/clgm72lhp87518hzofxljm955t https://status.flok.org/incident/clgm72lhp87518hzofxljm955t flok Investigating Type: Incident Duration: 1 hour and 53 minutes Affected Components: Website Apr 18, 05:16:16 GMT+0 - Investigating - We are currently investigating this incident. Apr 18, 07:08:31 GMT+0 - Identified - We are continuing to work on a fix for this incident. Apr 18, 07:09:22 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 1 hour and 53 minutes

Affected Components:

<p><small>Apr <var data-var='date'> 18</var>, <var data-var='time'>05:16:16</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>Apr <var data-var='date'> 18</var>, <var data-var='time'>07:08:31</var> GMT+0</small><br><strong>Identified</strong> - We are continuing to work on a fix for this incident..</p> <p><small>Apr <var data-var='date'> 18</var>, <var data-var='time'>07:09:22</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Tue, 18 Apr 2023 05:16:16 +0000 https://status.flok.org/incident/clgltb0sx76065hjop0zgs823u https://status.flok.org/incident/clgltb0sx76065hjop0zgs823u