Retool outage history

We hold 53 Retool incidents from Retool's status page, the newest from Nov 14, 2026. 53 of the 53 listed carry Retool's own update timeline. Each one links to a page with the vendor's updates and what our five-minute checks recorded while it was open.

Uptime & history

Tracking since Jun 22, 2026
Currently up for 2h 10m since the last recorded problem.
Operational · 24h
9.03%
0 incidents · ≈21h 50m degraded
288 checks
Operational · 7d
17.37%
2 incidents · ≈5d 18h degraded
2015 checks
Operational · 30d
72.68%
3 incidents · ≈8d 4h degraded
8638 checks
Operational · since Jun 22, 2026
83.43%
20 incidents · ≈23d 16h degraded
41202 checks

% of our checks that found Retool fully operational — a degraded check counts against it, because a slow or partly-broken service is not a working one. Down and degraded time are counted at our 5-minute check resolution, so both are approximate. Longer windows fill in as data accrues — we never show uptime we haven't measured.

Recent checks
oldernow
Past incidents

How Retool fails

Since Jul 1, 2026, Retool's status page has marked 8 Retool components as impaired, across 6,870 of our five-minute readings. Resource Queries accounts for the most: 3,598 readings (about 300 hours) on 16 days, most recently on Oct 12, 2026. Next is RetoolDB, with 1,493 readings on 7 days. We hold 53 Retool incidents from Retool's status page, the earliest from May 12, 2025. Of the 48 that Retool closed with an end time, the median lasted 3 h 53 min.

ComponentOutageDegradedMaint.DaysLast
Resource Queries—3598—16Oct 12, 2026
RetoolDB—1493—7Nov 19, 2026
New app builder—1013—8Nov 12, 2026
Workflows7309—3Jul 30, 2026
Email Server252——2Jul 24, 2026
Platform APIs—100—2Sep 14, 2026
Source Control—53—2Oct 12, 2026
Self Hosted On-Premise—45—1Aug 20, 2026

Incidents by month: Jun 2026: 2 · Jul 2026: 6 · Aug 2026: 5 · Sep 2026: 3 · Oct 2026: 3 · Nov 2026: 3

Counts are five-minute readings of Retool's own component statuses, recorded only when a component is not operational. Hours are readings times five minutes, so a gap in our recording would undercount, never overcount.

Every recorded incident

November 2026 · 3

October 2026 · 3

September 2026 · 3

July 2026 · 6

June 2026 · 2

March 2026 · 4

February 2026 · 3

January 2026 · 1

December 2025 · 2

November 2025 · 3

October 2025 · 3

September 2025 · 1

May 2025 · 1

Incidents and their updates are Retool's own words from its status page, recorded every five minutes; we never add an inferred cause. AIDownCheck is independent and not affiliated with Retool.