Skip to main content
Retool logo

Is Retool Down?

No — Retool is up

Reachable from all 8 checked regions

Average response time: 178ms

Last checked · checks run every 6 hours

Official status page: https://status.retool.com

Retool uptime

100%
Last 7 days
100%
Last 30 days
100%
Last 90 days
241ms
Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 77 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

77-day clean streak
Sep 14: 100.00% uptime, 32 checks
Sep 15: 100.00% uptime, 32 checks
Sep 16: 100.00% uptime, 32 checks
Sep 17: 100.00% uptime, 32 checks
Sep 18: 100.00% uptime, 32 checks
Sep 19: 100.00% uptime, 32 checks
Sep 20: 100.00% uptime, 32 checks
Sep 21: 100.00% uptime, 32 checks
Sep 22: 100.00% uptime, 32 checks
Sep 23: 100.00% uptime, 40 checks
Sep 24: 100.00% uptime, 32 checks
Sep 25: 100.00% uptime, 32 checks
Sep 26: 100.00% uptime, 32 checks
Sep 27: 100.00% uptime, 32 checks
Sep 28: 100.00% uptime, 32 checks
Sep 29: 100.00% uptime, 32 checks
Sep 30: 100.00% uptime, 32 checks
Oct 1: 100.00% uptime, 32 checks
Oct 2: 100.00% uptime, 32 checks
Oct 3: 100.00% uptime, 32 checks
Oct 4: 100.00% uptime, 32 checks
Oct 5: 100.00% uptime, 32 checks
Oct 6: 100.00% uptime, 32 checks
Oct 7: 100.00% uptime, 32 checks
Oct 8: 100.00% uptime, 32 checks
Oct 9: 100.00% uptime, 32 checks
Oct 10: 100.00% uptime, 32 checks
Oct 11: 100.00% uptime, 32 checks
Oct 12: 100.00% uptime, 32 checks
Oct 13: 100.00% uptime, 32 checks
Sep 14 Today
No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

ams
202ms
DNS 53ms TCP 8ms TLS 25ms TTFB 145ms
arn
114ms
DNS 11ms TCP 1ms TLS 11ms TTFB 64ms
cdg
149ms
DNS 24ms TCP 8ms TLS 15ms TTFB 103ms
dfw
209ms
DNS 43ms TCP 0ms TLS 53ms TTFB 159ms
sin
166ms
DNS 60ms TCP 1ms TLS 9ms TTFB 156ms
sjc
110ms
DNS 33ms TCP 1ms TLS 8ms TTFB 97ms
syd
257ms
DNS 180ms TCP 1ms TLS 9ms TTFB 247ms
yyz
217ms
DNS 58ms TCP 12ms TLS 31ms TTFB 166ms

What Retool does

Retool is a platform for building internal tools quickly, assembling admin panels, support dashboards and operations consoles from prebuilt components wired to a company's own databases and APIs. The people who depend on it are usually support, operations and finance staff, so an outage stops back-office work rather than anything customers can see.

What an outage looks like

Apps load but their components stay empty, because queries against connected databases and APIs fail while the interface itself renders. The editor may refuse to save changes, and Workflows stop running on schedule so downstream jobs quietly do not happen. Self-hosted deployments can fail separately if they cannot reach the license server, which locks users out of an otherwise healthy local instance.

What to do about it

Check status.retool.com, which reports the new app builder, classic web app, Resource Queries, Workflows, RetoolDB, Platform APIs, the license server and self-hosted deployments as separate components. If only Resource Queries is affected, your own databases are probably fine and worth verifying directly. Avoid re-running Workflows by hand until the queue has drained, since duplicates are the usual result.

Is it down for everyone, or just you?

If this page says Retool is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 17 cities across three regions to find out where it breaks.

Test it yourself

Related services

Supabase
Supabase
Postman
Postman
Airtable
Airtable
MongoDB Atlas
MongoDB Atlas

Retool outage FAQ

Is Retool down or is my database connection broken?
Resource Queries is listed separately from the app builder on Retool's status page, which is the distinction that matters here. If that component is degraded, the failure is between Retool and your data source rather than in the data source itself. Confirm by querying your database directly from another client: if it answers normally, there is nothing to fix on your side but waiting.
Does a Retool outage affect self-hosted deployments?
It can, which surprises teams who chose self-hosting to avoid exactly this. Retool tracks Self Hosted On-Premise and the license server as their own components, and an instance running entirely on your infrastructure may still refuse logins if it cannot validate its license. Check both components before concluding that a self-hosted outage must be caused by your own environment.
Will my Retool Workflows run after the outage ends?
Scheduled runs missed during an incident are not automatically replayed, so treat them as skipped rather than delayed. Once Workflows is reported healthy, review anything that should have run and decide what genuinely needs triggering by hand. Be deliberate about it, because re-running a workflow that did complete is a common way to double-process records or send duplicate messages.
Can I keep using an app while the Retool editor is down?
Often yes. The app builder and the classic web app are tracked separately from the runtime pieces, so published apps may keep serving users while editing is unavailable. What you lose is the ability to change anything, which matters most when the fix your team needs is a quick edit to the very tool that is failing.
Does Retool being down affect our customers?
Usually not directly, because Retool tools are internal. The impact lands on the teams who use them: support agents cannot look up accounts, operations staff cannot process refunds or adjust orders, and finance cannot run reconciliations. Customers feel it as slower responses rather than a broken product, which is worth saying explicitly when you communicate about the incident.

How we measure this

  • We request Retool's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them.
  • A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
  • A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
  • Response times average only the regions that actually served the page, so a timeout never inflates the number.
  • Where Retool publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Retool goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required