Retool

Affected: Source Control

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-10-12 22:44 UTC

   We are investigating an issue with Source Control deployments being stalled in a "queued" state on Retool Cloud version 4.74.0

2. identified 2026-10-12 22:55 UTC

   We've identified the issue and are working on remediation.

3. monitoring 2026-10-12 23:25 UTC

   A fix is being deployed and we are monitoring.

4. monitoring 2026-10-12 23:46 UTC

   The fix has been deployed and source control deployments should be working as expected -- we are monitoring.

5. resolved 2026-10-13 00:16 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Retool's status page.

Affected: Resource Queries

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-05 15:49 UTC

   Some customers may experience slower than normal query load times. We're actively investigating and will provide updates as we learn more.

2. investigating 2026-10-05 22:06 UTC

   Some users may see improved query latency, but we are continuing to investigate.

3. monitoring 2026-10-06 02:44 UTC

   Some changes have been deployed, and we are monitoring the results

4. investigating 2026-10-06 14:40 UTC

   We are seeing intermittent spikes in query latency, as we saw earlier. A temporary mitigation is in place, and we're continuing to investigate the root cause. We'll share an update as soon as we have more information.

5. investigating 2026-10-06 19:03 UTC

   The temporary mitigation we applied earlier is still in place, and some users have reported significantly improved query latency. We're still investigating the root cause and will share another update as we learn more.

6. monitoring 2026-10-06 23:47 UTC

   A fix has been implemented and we are monitoring the results.

7. investigating 2026-10-07 15:21 UTC

   This morning we again saw high query latency. We were able to mitigate it temporarily, and our investigation into the root cause is ongoing. We'll share another update as we learn more.

8. investigating 2026-10-07 22:19 UTC

   Additional changes have been deployed as part of a more permanent fix, alongside the temporary fix already in place. We'll monitor through tomorrow morning's peak traffic to confirm their impact and will share another update then.

9. monitoring 2026-10-08 14:23 UTC

   A fix has been implemented and we are monitoring the results.

10. monitoring 2026-10-08 21:20 UTC

    We have not seen the same query latency issues since the fix was applied. We’re continuing to monitor closely and will share another update if anything changes.

11. resolved 2026-10-12 22:42 UTC

    Query performance is back to normal and the incident is resolved.

Excerpts are shortened. Read the full incident on Retool's status page.

Affected: Resource Queries

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-02 17:13 UTC

   Some customers may experience slower than normal query load times. We're actively investigating and will provide updates as we learn more.

2. monitoring 2026-10-02 18:55 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2026-10-02 19:40 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Retool's status page.

Affected: Platform APIs

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-14 16:07 UTC

   We're investigating an issue causing some users to experience errors when connecting to Retool's MCP server. Some connections may fail. We're working on a fix and will provide updates as we have them.

2. identified 2026-09-14 16:26 UTC

   The issue has been identified and a fix is being implemented.

3. monitoring 2026-09-14 19:13 UTC

   A fix has been implemented and we are monitoring the results.

4. resolved 2026-09-14 22:18 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Retool's status page.

Affected: Platform APIs

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2026-09-08 15:16 UTC

   A fix has been implemented for the issue causing intermittent "Session not found" connection failures on the Retool MCP server. We are currently monitoring the results to confirm full resolution. If you were running into this error, please retry to create a new session.

2. resolved 2026-09-08 17:30 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Retool's status page.

Affected: Resource Queries

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-09-01 15:31 UTC

   Some customers are seeing generic JDBC resource type queries fail with an error referencing LZ4 compression. Connection tests still pass, so the error appears only when running a query or loading a resource schema. We have identified the cause and are working on a fix.

2. resolved 2026-09-01 19:06 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Retool's status page.

Affected: New app builder, Self Hosted On-Premise

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-08-20 17:26 UTC

   Retool's app builder may fail to install and connect to a sandbox due to downstream dependency issues. This affects both Cloud and Self-Hosted Retool instances.

2. identified 2026-08-20 17:30 UTC

   This issue no longer affects the React App Builder on Retool Cloud. We have identified the issue for self-hosted, and are working on releasing images with a fix

3. identified 2026-08-20 18:16 UTC

   This issue affects Retool version 4.0.0+ (stable and edge), specifically for 1) newly-created React apps, 2) new publishes of existing React apps, and 3) cold starts of sandboxes when editing existing React apps. Existing published apps that do not get published after August...

4. monitoring 2026-08-20 21:08 UTC

   Images with the fix are out: 4.0.12-stable 4.43.0-edge Our minimum release age for React app builder dependencies is 5 days, so this incident will self-resolve for any self-hosted deployments that don't upgrade on August 24th, by 7am PST. All currently affected self-hosted...

5. resolved 2026-08-20 23:20 UTC

   This incident is resolved. Images with the fix are out: 4.0.12-stable 4.43.0-edge Our minimum release age for React app builder dependencies is 5 days, so this incident will self-resolve for any self-hosted deployments that don't upgrade on August 24th, by 7am PST. All currently...

Excerpts are shortened. Read the full incident on Retool's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. resolved 2026-08-19 16:00 UTC

   Some users may have seen an error or a blank preview when opening or editing apps built with Retool's AI app builder. The issue has now been resolved.

Excerpts are shortened. Read the full incident on Retool's status page.

Affected: Source Control

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. monitoring 2026-08-17 18:32 UTC

   An upstream incident with Github (https://www.githubstatus.com/incidents/zkxwbgr0cnmx) is causing issues with source control in Retool. Github has deployed a fix and we are monitoring.

2. resolved 2026-08-17 21:49 UTC

   Github has resolved their incident.

Excerpts are shortened. Read the full incident on Retool's status page.

Affected: New app builder

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-08-14 15:06 UTC

   We are currently investigating this issue.

2. identified 2026-08-14 15:20 UTC

   The issue has been identified and a fix is being implemented.

3. monitoring 2026-08-14 16:36 UTC

   A fix has been implemented and we are monitoring the results.

4. resolved 2026-08-14 19:00 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Retool's status page.

Affected: New app builder

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-08-06 20:27 UTC

   We are investigating reports of customers being unable to save or publish changes in React apps, with an error about system dependencies. We will share an update as soon as we know more.

2. monitoring 2026-08-06 20:41 UTC

   A fix has been implemented, and we are monitoring the results

3. resolved 2026-08-06 21:16 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Retool's status page.

Affected: Workflows, Retool-managed Temporal (via Temporal.io)

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-07-30 20:22 UTC

   We are investigating an issue with Retool Workflows being stuck in a pending state. There is also an uptick in 429 rate limit responses for start triggers

2. identified 2026-07-30 20:45 UTC

   We've identified the issue and are working on a fix.

3. monitoring 2026-07-30 21:20 UTC

   The fix has been deployed, and we're monitoring the results. Workflows are still degraded but recovering.

4. monitoring 2026-07-30 23:08 UTC

   We are continuing to monitor for any further issues.

5. resolved 2026-07-31 05:52 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Retool's status page.

Affected: Resource Queries

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2026-07-29 13:14 UTC

   A fix has been implemented and we are monitoring the results.

2. resolved 2026-07-29 13:36 UTC

   The fix was verified and the breakage is now resolved.

Excerpts are shortened. Read the full incident on Retool's status page.

Affected: Email Server

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-07-23 22:22 UTC

   We are investigating the disabling of retool-email.com domain due to spam. Note that this does not impact official retool emails like user invites and password resets.

2. resolved 2026-07-24 18:34 UTC

   Some Retool Emails failed with a "Disabled for sending spam" error due to an issue with our upstream email provider. The sending domain has since been restored, and email delivery is operating normally. We've also added safeguards to prevent recurrence. We apologize for the...

Excerpts are shortened. Read the full incident on Retool's status page.

Affected: New app builder

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-07-14 14:10 UTC

   We're investigating an issue affecting Apps built in the new AI app builder. Affected users may see an empty Data tab ("This app does not contain any functions") and be unable to publish, with an error that backend functions are unapproved or "not visible in the Data tab."

2. monitoring 2026-07-14 16:55 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2026-07-14 17:21 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Retool's status page.

Affected: Workflows

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-08 16:17 UTC

   We're investigating an issue where some Retool Cloud Workflows are intermittently failing with timeout errors.

2. monitoring 2026-07-09 00:19 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2026-07-09 16:10 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Retool's status page.

Affected: Resource Queries

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-01 15:29 UTC

   We are currently investigating an issue where queries are experiencing higher latency.

2. monitoring 2026-07-01 15:35 UTC

   A fix has been implemented and we are monitoring the results.

3. identified 2026-07-01 15:53 UTC

   The issue has been identified and a fix is being implemented.

4. monitoring 2026-07-01 18:36 UTC

   A fix has been implemented and we are monitoring the results.

5. resolved 2026-07-06 17:25 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Retool's status page.

Affected: Source Control

Failure mode: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-06-05 14:11 UTC

   We've identified the issue and are preparing a fix

2. identified 2026-06-05 14:11 UTC

   We are continuing to work on a fix for this issue.

3. monitoring 2026-06-05 17:17 UTC

   A fix has been implemented and we are monitoring the results.

4. resolved 2026-06-09 17:23 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Retool's status page.

Affected: Classic web app

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-06-04 15:13 UTC

   We are investigating reports that Retool Mobile apps fail to load when opened in a web browser (the in-browser "View"/user-mode preview and the editor preview button). Editing mobile apps and running them in the native iOS/Android Retool Mobile apps are unaffected.

2. identified 2026-06-04 15:45 UTC

   The issue has been identified and a fix is being implemented.

3. monitoring 2026-06-04 16:39 UTC

   A fix has been implemented and we are monitoring the results.

4. resolved 2026-06-04 19:16 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Retool's status page.

Affected: Classic web app

Failure mode: Login, tokens, certificates or credentials failed. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-05-26 20:14 UTC

   We're investigating reports of customers experiencing sign-in issues on the Retool Mobile app for iOS and Android. Affected users may be returned to the sign-in screen after authenticating, or be unable to complete sign-in.

2. identified 2026-05-27 14:51 UTC

   The issue has been identified as a change made to how mobile sessions are validated. We have rolled back that change and are working on a permanent fix. As we work on shipping that fix, please try the following: - Android: Clear the app cache. Open your Settings, go to Apps (or...

3. monitoring 2026-05-28 14:24 UTC

   The issue has been identified as a change made to how mobile sessions are validated. We have rolled back that change and are monitoring the results If you are unable to log into Retool Mobile, you will have to do the following: - Android: Clear the app cache. Open your Settings,...

4. monitoring 2026-05-29 18:55 UTC

   The issue has been identified as a change made to how mobile sessions are validated. We have rolled back that change and are monitoring the results If you are unable to log into Retool Mobile, you will have to do the following: - Android: Clear the app cache. Open your Settings,...

5. resolved 2026-06-04 09:22 UTC

   This incident is resolved. If you are having issues signing in, please first try the following: - Android: Clear the app cache. Open your Settings, go to Apps (or Applications), tap Retool Mobile, select Storage, and tap Clear cache. - iOS: Delete and reinstall the Retool Mobile...

Excerpts are shortened. Read the full incident on Retool's status page.

Affected: Classic web app

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. monitoring 2026-05-25 12:39 UTC

   A fix has been implemented and we are monitoring the results.

2. resolved 2026-05-25 12:52 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Retool's status page.

Affected: Classic web app

Failure mode: CDN or edge layer failed or served bad content. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-05-20 14:17 UTC

   We are reopening our investigation of this issue after continued reports.

2. monitoring 2026-05-20 16:13 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2026-05-20 17:58 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Retool's status page.

Affected: Classic web app

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-05-19 15:11 UTC

   We are investigating reports that some Retool pages are returning a "Page not found".

2. monitoring 2026-05-19 17:03 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2026-05-19 17:28 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Retool's status page.

Affected: Workflows, License server, Retool-managed Temporal (via Temporal.io), Self Hosted On-Premise

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-05-12 13:14 UTC

   We are currently investigating this issue.

2. monitoring 2026-05-12 14:06 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2026-05-12 14:42 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Retool's status page.

Affected: Classic web app, Resource Queries

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-05-11 23:50 UTC

   We're investigating an issue with our MotherDuck integration for Cloud orgs

2. resolved 2026-05-12 03:07 UTC

   MotherDuck is fully operational again. We identified and fixed a caching issue that required us to temporarily disable the integration. Access has been restored as of May 11, 2026. We apologize for the disruption.

Excerpts are shortened. Read the full incident on Retool's status page.

Affected: Resource Queries

Failure mode: A configuration change caused the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-05-08 19:06 UTC

   We are currently investigating issues with the Motherduck resource and are disabling it as the investigation is ongoing.

2. resolved 2026-05-09 08:43 UTC

   MotherDuck is fully operational again. We identified and fixed a caching issue that required us to temporarily disable the integration. Access has been restored as of May 8, 2026. We apologize for the disruption.

Excerpts are shortened. Read the full incident on Retool's status page.

Affected: Workflows

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-05-08 17:03 UTC

   We are investigating an issue where workflows using custom npm libraries are failing to execute. This affects both Retool Cloud and self-hosted customers. A fix has been identified and is currently being deployed to Cloud. Self-hosted patch releases are in progress.

2. monitoring 2026-05-08 18:15 UTC

   A fix has been deployed to Retool Cloud. Self-hosted customers should upgrade to 3.300.28-stable or 3.334.12-stable, which has the fix. We are monitoring to confirm full resolution.

3. resolved 2026-05-08 22:33 UTC

   This incident has been resolved. Self-hosted customers should update to 3.300.28-stable or 3.334.12-stable for the fix.

Excerpts are shortened. Read the full incident on Retool's status page.

Affected: Classic web app, Infrastructure

Failure mode: Network, DNS, routing or connectivity failure. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Cloudflare.

1. investigating 2026-05-05 23:59 UTC

   We are investigating errors for some users preventing Retool Apps from loading due to errors with retool-edge.com

2. identified 2026-05-06 00:41 UTC

   We've identified the issue is due to certain ISPs blocking the retool-edge.com domain. Confirmed ISPs are Comcast Business and Optimum (Altice USA / Cabelvision). We are actively working to remove the block.

3. identified 2026-05-06 01:52 UTC

   While we work on removing the ISP blocks, here is a workaround. You can temporarily resolve this by switching to a trusted public DNS resolver such as 1.1.1.1 (Cloudflare) or 8.8.8.8 (Google). Mac: 1. System Settings → Network → select your connection → Details 2. Click the DNS...

4. identified 2026-05-06 16:23 UTC

   Comcast Business SecurityEdge customers may find that the workaround mentioned does not work, and neither does allowlisting the retool-edge.com domain. In these cases, disabling SecurityEdge has been successful. If you are still experiencing issues after trying the DNS...

5. identified 2026-05-06 20:51 UTC

   TALOS has reclassified our domain. We have escalated directly to affected ISPs to have the block fully lifted and are actively working toward a resolution. We will provide another update once full resolution is confirmed.

6. monitoring 2026-05-07 18:47 UTC

   We are seeing reports of some users returning to normal operation. We are continuing to work with ISPs to remove the block on retool-edge.com and will keep you posted on our progress. If you are still experiencing issues, the workaround below remains available.

7. monitoring 2026-05-08 00:26 UTC

   We are no longer receiving new reports of users being affected. We will continue to monitor this incident over the next 24 hours before marking it as resolved.

8. resolved 2026-05-08 15:38 UTC

   All affected ISPs have confirmed that retool-edge.com is no longer being blocked. This incident is now resolved. Thank you for your patience.

Excerpts are shortened. Read the full incident on Retool's status page.

Affected: Resource Queries

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-04-21 17:16 UTC

   We are reopening an investigation into an issue where Google Sheets resources are intermittently failing with a "premature close" error. This is affecting a subset of users on Retool Cloud. Our team is actively investigating the root cause and working on a mitigation.

2. investigating 2026-04-21 23:39 UTC

   We are still investigating this issue.

3. identified 2026-04-22 17:31 UTC

   We've identified the issue and a fix is being prepared

4. monitoring 2026-04-22 22:01 UTC

   We've deployed a fix and are monitoring the results.

5. investigating 2026-04-23 17:00 UTC

   We are still investigating this issue.

6. monitoring 2026-04-24 02:36 UTC

   We've deployed another attempted fix and are monitoring the results.

7. monitoring 2026-04-25 00:09 UTC

   We are continuing to monitor for any further issues.

8. resolved 2026-04-27 14:49 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Retool's status page.

Affected: Resource Queries

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-04-17 14:19 UTC

   We are investigating an issue where Google Sheets resources are intermittently failing with a "premature close" error. This is affecting a subset of users on Retool Cloud. Our team is actively investigating the root cause and working on a mitigation.

2. identified 2026-04-17 17:58 UTC

   The issue has been identified and a fix is being implemented.

3. monitoring 2026-04-17 18:24 UTC

   A fix has been implemented and we are monitoring the results.

4. monitoring 2026-04-18 03:35 UTC

   The issue has been resolved.

5. resolved 2026-04-18 03:36 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Retool's status page.

Affected: Resource Queries, RetoolDB

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-04-16 15:49 UTC

   We are currently investigating an issue causing PostgreSQL and REST API queries to fail. This also affects users' ability to use RetoolDB.

2. identified 2026-04-16 17:01 UTC

   We have identified the potential root cause of this issue and are implementing a fix

3. monitoring 2026-04-16 17:36 UTC

   A fix has been implemented and we are monitoring the results.

4. resolved 2026-04-16 18:17 UTC

   Following the fix we are seeing error rates of the affected services return to normal. With that in mind, we are considering this issue resolved.

Excerpts are shortened. Read the full incident on Retool's status page.

Affected: Resource Queries

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-04-16 15:31 UTC

   We are investigating an issue where Google Sheets resources are intermittently failing with a "premature close" error. This is affecting a subset of users on Retool Cloud. Our team is actively investigating the root cause and working on a mitigation.

2. resolved 2026-04-16 17:33 UTC

   We are closing this incident as it has been identified as part of a larger issue. Please follow: [Retool Cloud] PostgreSQL and REST API Resource Queries Intermittently Failing, for the latest updates and resolution progress.

Excerpts are shortened. Read the full incident on Retool's status page.

Affected: Resource Queries

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-03-25 13:54 UTC

   We are looking into an issue that is preventing Cloud customers with Custom Domains from completing the OAuth2 Resource Authentication flow. Affected customers can work around this behavior by authenticating said resources via their base (.retool.com) domain.

2. identified 2026-03-25 17:05 UTC

   The issue has been identified and a fix is being implemented.

3. resolved 2026-03-25 20:36 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Retool's status page.

Affected: Classic web app

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-03-17 17:36 UTC

   Unfortunately this issue has not been fully resolved as previously indicated, and we are continuing to work on a fix. We apologise for the continued disruption.

2. resolved 2026-03-17 21:08 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Retool's status page.

Affected: Classic web app

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-03-17 15:20 UTC

   We are currently investigating reports of intermittent navigation issues affecting some Cloud users. Users may experience apps failing to load or the browser reverting to a previous app when navigating between apps. We are actively investigating this issue. We apologize for any...

2. identified 2026-03-17 16:04 UTC

   We have identified the root cause and are working on a fix.

3. resolved 2026-03-17 16:48 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Retool's status page.

Affected: Workflows, Resource Queries

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-03-06 18:53 UTC

   We're aware that some users are encountering unexpected rate‑limiting when using AI-powered features. We are actively investigating the root cause and working to restore full functionality as quickly as possible.

2. monitoring 2026-03-06 20:08 UTC

   We believe the issue has been resolved after coordination with our AI providers. We are actively monitoring the situation and will notify you if any further problems arise. Thank you for your patience.

3. resolved 2026-03-06 21:12 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Retool's status page.

Affected: Workflows, Resource Queries

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. monitoring 2026-02-25 05:08 UTC

   We’re experiencing elevated error rates on our Google Sheets, MySQL, and PostgreSQL integrations. The root cause has been identified and is under active monitoring by our engineering team. All query operations continue to function as expected. We’ll keep you posted with any new...

2. monitoring 2026-02-25 05:52 UTC

   We are continuing to monitor for any further issues.

3. resolved 2026-02-25 17:54 UTC

   We've confirmed that the resources affected are operational and have resolved this incident.

Excerpts are shortened. Read the full incident on Retool's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. resolved 2026-02-04 22:46 UTC

   Between 12:00pm and 12:08pm, there was a partial outage across many of Retool's product surfaces. There should be no impact outside of that timeframe.

Excerpts are shortened. Read the full incident on Retool's status page.

Affected: RetoolDB

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-02-03 13:30 UTC

   We are aware of an issue where RetoolDB is unavailable for new Retool organizations. We are working with our vendor to get this back online ASAP. This only affects new cloud organizations; organizations pre-incident are not affected.

2. identified 2026-02-03 22:04 UTC

   We are continuing to work on a fix for this issue.

3. resolved 2026-02-03 23:07 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Retool's status page.

Affected: Classic web app

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-01-13 17:32 UTC

   We are currently looking into reports of users being unable to navigate between apps, whether it be via HTML hyperlink or Retools built in utils (openApp/openUrl)

2. investigating 2026-01-13 17:32 UTC

   We are continuing to investigate this issue.

3. monitoring 2026-01-13 18:12 UTC

   A fix has been implemented and we are monitoring the results. If you were affected by this behavior, please clear your browser's cache and refresh the page before trying to navigate across apps.

4. resolved 2026-01-13 19:02 UTC

   This incident has been resolved. If you were affected by this behavior, please clear your browser's cache and refresh the page before trying to navigate across apps.

Excerpts are shortened. Read the full incident on Retool's status page.

Affected: Resource Queries

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2025-12-18 19:53 UTC

   We have identified an issue where OAuth requests to Snowflake with any value being passed via the prompt parameter are being rejected. We are actively working on implementing a fix. In the meantime, the current workaround is to remove the prompt parameter entirely from your...

2. resolved 2025-12-18 23:46 UTC

   The issue has been fixed on Retool Cloud and all systems are operating normally. Self-hosted customers can remove the `prompt` parameter as a workaround until the patch is available.

Excerpts are shortened. Read the full incident on Retool's status page.

Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2025-12-17 23:25 UTC

   An infra routing changed caused elevated backend errors that may have caused resource queries to timeout or fail

Excerpts are shortened. Read the full incident on Retool's status page.

Affected: Source Control

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: GitHub.

1. monitoring 2025-11-18 21:36 UTC

   GitHub is currently experiencing service issues that may affect Retool users who use GitHub as their source control provider.

2. monitoring 2025-11-18 21:36 UTC

   We are continuing to monitor for any further issues.

3. monitoring 2025-11-18 21:58 UTC

   We are continuing to monitor for any further issues.

4. monitoring 2025-11-18 21:59 UTC

   We are continuing to monitor for any further issues.

5. resolved 2025-11-18 22:03 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Retool's status page.

Affected: Infrastructure

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. monitoring 2025-11-18 13:45 UTC

   We have determined that this is related to an issue with one of our external partners. We are awaiting updates on their end and will update here once this is resolved.

2. monitoring 2025-11-18 14:52 UTC

   Our external partner has pushed out a fix and we are continuing to monitor Retool services.

3. resolved 2025-11-18 15:05 UTC

   We have observed stable and healthy performance since 14:43 UTC and are now considering this incident resolved.

Excerpts are shortened. Read the full incident on Retool's status page.

Affected: Source Control

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-11-17 15:34 UTC

   We are currently investigating reports of increased latency and intermittent failures while deploying source controlled elements on Retool Cloud.

2. monitoring 2025-11-17 20:36 UTC

   A potential fix has been implemented and we are monitoring the results

3. resolved 2025-11-18 14:46 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Retool's status page.

Affected: Resource Queries

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-10-29 13:45 UTC

   We are currently investigating reports of users hitting errors with Retool AI actions

2. monitoring 2025-10-29 15:56 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2025-10-29 17:02 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Retool's status page.

Affected: Classic web app

Failure mode: Network, DNS, routing or connectivity failure. Root cause: Network or DNS. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-10-17 19:32 UTC

   We're investigating the source of failures in web calls and latency. Observed a spike of issues around 12:15 but have since recovered.

2. investigating 2025-10-17 23:19 UTC

   we've identified minor network instability that caused the failures. Continuing to monitor the situation in case of new regressions

3. investigating 2025-10-17 23:20 UTC

   we've identified minor network instability that caused the failures. Continuing to monitor the situation in case of new regressions (typo below)

4. resolved 2025-10-20 19:13 UTC

   No additional instability was witnessed over the weekend, this incident is being marked resolved.

Excerpts are shortened. Read the full incident on Retool's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. resolved 2025-10-16 18:45 UTC

   Elevated 500 errors on a back-end endpoint preventing some apps from loading

Excerpts are shortened. Read the full incident on Retool's status page.

Affected: Infrastructure

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-09-24 11:34 UTC

   We are currently investigating reports of users being unable to access Retool from various regions outside of the US.

2. monitoring 2025-09-24 12:43 UTC

   The reported latency looks to have subsided. We are monitoring for any follow-up issues.

3. resolved 2025-09-24 12:57 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Retool's status page.

Affected: Classic web app, Workflows, Resource Queries

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2025-05-12 23:23 UTC

   Retool occasionally incorrectly returns a self-signed TLS certificate on a small subset of HTTP requests. This can manifest on any request, affecting normal usage as well as Workflow runs that run resource queries. Our team has identified the issue and is working on a...

2. identified 2025-05-13 01:21 UTC

   We've implemented a stopgap to prevent this issue from reoccurring while we wait to execute a permanent resolution. You may continue to very rarely see this self-signed cert issue.

3. monitoring 2025-05-13 14:45 UTC

   We've confirmed that the issue has stabilized. We're monitoring for unexpected spikes in errors, but please anticipate a very low rate of errors until a permanent fix has been executed.

4. resolved 2025-05-18 09:17 UTC

   We've rolled out the fix and verified that customers should no longer be seeing self-signed TLS certificate errors and that custom-domain provisioning capability has been restored.

Excerpts are shortened. Read the full incident on Retool's status page.