User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / AI
retool.com · AI
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Press Run testYour browser tests the site, us, and two public DNS resolvers. We never store your IP; only anonymous counts by network and region.
No reports in the last 24 hours.
Dots are whole states, provinces or countries, never exact locations. We never store IP addresses. Every report with a known place can appear on the map. Updates every minute.
Each row is a time, a coarse place, and a problem type from a new report. Optional notes stay private. Places with fewer than 3 reports in the last 8 days are shown without a location.
No public reports yet.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last checked 11 min ago. Last stored result reached it in 100 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 15 | 0 | 0.0 | 169 ms | 0 |
| Mon 17 | 0 | 0.0 | 227 ms | 0 |
| Mon 18 | 0 | 0.0 | 220 ms | 0 |
| Mon 20 | 0 | 0.0 | 195 ms | 0 |
| Mon 22 | 0 | 0.0 | 241 ms | 0 |
| Tue 00 | 0 | 0.0 | 97 ms | 0 |
| Tue 02 | 0 | 0.0 | 204 ms | 0 |
| Tue 04 | 0 | 0.0 | 64 ms | 0 |
| Tue 06 | 0 | 0.0 | 255 ms | 0 |
| Tue 08 | 0 | 0.0 | 96 ms | 0 |
| Tue 10 | 0 | 0.0 | 77 ms | 0 |
| Tue 12 | 0 | 0.0 | 88 ms | 0 |
| Tue 15 | 0 | 0.0 | 193 ms | 0 |
| Tue 17 | 0 | 0.0 | 98 ms | 0 |
| Tue 19 | 0 | 0.0 | 195 ms | 0 |
| Tue 22 | 0 | 0.0 | 155 ms | 0 |
| Wed 00 | 0 | 0.0 | 364 ms | 0 |
| Wed 02 | 0 | 0.0 | 84 ms | 0 |
| Wed 04 | 0 | 0.0 | 184 ms | 0 |
| Wed 06 | 0 | 0.0 | 123 ms | 0 |
| Wed 09 | 0 | 0.0 | 201 ms | 0 |
| Wed 11 | 0 | 0.0 | 85 ms | 0 |
| Wed 13 | 0 | 0.0 | 189 ms | 0 |
| Wed 15 | 0 | 0.0 | 172 ms | 0 |
| Wed 17 | 0 | 0.0 | 328 ms | 0 |
| Wed 19 | 0 | 0.0 | 223 ms | 0 |
| Wed 21 | 0 | 0.0 | 174 ms | 0 |
| Wed 23 | 0 | 0.0 | 184 ms | 0 |
| Thu 02 | 0 | 0.0 | 189 ms | 0 |
| Thu 04 | 0 | 0.0 | 212 ms | 0 |
| Thu 06 | 0 | 0.0 | 273 ms | 0 |
| Thu 08 | 0 | 0.0 | 215 ms | 0 |
| Thu 10 | 0 | 0.0 | 216 ms | 0 |
| Thu 12 | 0 | 0.0 | 208 ms | 0 |
| Thu 14 | 0 | 0.0 | 229 ms | 0 |
| Thu 16 | 0 | 0.0 | 303 ms | 0 |
| Thu 18 | 0 | 0.0 | 221 ms | 0 |
| Thu 20 | 0 | 0.0 | 210 ms | 0 |
| Thu 22 | 0 | 0.0 | 139 ms | 0 |
| Fri 00 | 0 | 0.0 | 257 ms | 0 |
| Fri 02 | 0 | 0.0 | 196 ms | 0 |
| Fri 04 | 0 | 0.0 | 132 ms | 0 |
| Fri 07 | 0 | 0.0 | 94 ms | 0 |
| Fri 09 | 0 | 0.0 | 91 ms | 0 |
| Fri 11 | 0 | 0.0 | 256 ms | 0 |
| Fri 13 | 0 | 0.0 | 123 ms | 0 |
| Fri 15 | 0 | 0.0 | 90 ms | 0 |
| Fri 17 | 0 | 0.0 | 100 ms | 0 |
100% uptime · No user reports in the last 24h
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 8 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Retool yet. Outages of 10 minutes or more get their own page here.
One report per service every 10 minutes from this network. No account.
Get an email when Retool goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Retool alerts to Slack, Discord or a webhook — free.
Retool is listed in our AI category and checked at retool.com. Build, deploy, and manage internal tools with Retool's unified engine. Connect to any database, API, or LLM. Leverage AI throughout your business.
Retool publishes an official status page at status.retool.com; when we can read it, its incident level is folded into the status shown here.
Typical issues with AI services: slow or failed responses, rate-limit errors, and API timeouts.
Measured uptime from our checks: 100% over 8 days of checks. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 159 ms average, 90–257 ms range across 12 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Retool incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
159 ms on average over the last 24 hours (90–257 ms).
Yes, at https://status.retool.com.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For AI services, watch for slow or failed responses, rate-limit errors, and API timeouts. If many people report Retool here at once, the problem is on Retool's side.
How we detect and verify outages · Dispute this report · We review disputes within 24 hours.
Community comments
Share what you are seeing with Retool. No account needed. Comments are public, separate from outage reports. Do not include personal information.
No links or domains. 3 comments per service and 6 total per hour, per device and network. New contributors get one visible comment; further comments wait for review.