User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / 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 56 min ago. Last stored result reached it in 265 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Nov 6 | 0 | 0.0 | 236 ms | 0 |
| Nov 7 | 0 | 0.0 | 277 ms | 0 |
| Nov 7 | 0 | 0.0 | 237 ms | 0 |
| Nov 7 | 0 | 0.0 | 355 ms | 0 |
| Nov 7 | 0 | 0.0 | 375 ms | 0 |
| Nov 8 | 0 | 0.0 | 313 ms | 0 |
| Nov 8 | 0 | 0.0 | 313 ms | 0 |
| Nov 8 | 0 | 0.0 | 294 ms | 0 |
| Nov 8 | 0 | 0.0 | 274 ms | 0 |
| Nov 9 | 0 | 0.0 | 287 ms | 0 |
| Nov 9 | 0 | 0.0 | 331 ms | 0 |
| Nov 9 | 0 | 0.0 | 323 ms | 0 |
| Nov 9 | 0 | 0.0 | 337 ms | 0 |
| Nov 10 | 0 | 0.0 | 340 ms | 0 |
| Nov 10 | 0 | 0.0 | 240 ms | 0 |
| Nov 10 | 0 | 0.0 | 370 ms | 0 |
| Nov 10 | 0 | 0.0 | 329 ms | 0 |
| Nov 11 | 0 | 0.0 | 369 ms | 0 |
| Nov 11 | 0 | 0.0 | 284 ms | 0 |
| Nov 11 | 0 | 0.0 | 265 ms | 0 |
| Nov 11 | 0 | 0.0 | 316 ms | 0 |
| Nov 12 | 0 | 0.0 | 347 ms | 0 |
| Nov 12 | 0 | 0.0 | 300 ms | 0 |
| Nov 12 | 0 | 0.0 | 334 ms | 2 |
| Nov 12 | 0 | 0.0 | 297 ms | 0 |
| Nov 13 | 0 | 0.0 | 206 ms | 0 |
| Nov 13 | 0 | 0.0 | 385 ms | 0 |
| Nov 13 | 0 | 0.0 | 265 ms | 0 |
97.53% 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.
One report per service every 10 minutes from this network. No account.
Get an email when 21st.dev goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send 21st.dev alerts to Slack, Discord or a webhook — free.
We track 21st.dev (21st.dev) as part of the AI group. 12,000+ hand-crafted React and Tailwind CSS components, templates, and shadcn themes by real design engineers. Preview live, install with one command — for you and your AI agent.
21st.dev publishes an official status page at status.21st.dev; when we can read it, its incident level is folded into the status shown here.
Common problems for AI services: slow or failed responses, rate-limit errors, and API timeouts.
Measured uptime from our checks: 97.53% over 8 days of checks. We logged 1 public incident since monitoring began 8 days ago.
Response time over the last 24 hours: 319 ms average, 175–608 ms range across 12 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
The most recent public incident we recorded started 2026-11-12 and lasted 2 h 2 min. 1 incident since monitoring began 8 days ago.
From our own checks: 97.53% over 8 days of checks.
319 ms on average over the last 24 hours (175–608 ms).
Yes, at https://status.21st.dev.
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 21st.dev here at once, the problem is on 21st.dev'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 21st.dev. 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.