User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / AI
Is 21st.dev down?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Is it just me?
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Your browser → 21st.dev—
Your browser → us—
Our checksReaching it
Official · ReportsAll clear · Near baseline
DNS (1.1.1.1 · Google)—
Your provider—
Connection—
Upstream—
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.
Live outage map
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.
What's broken
Recent reports
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.
Our checks
Reaching it
Last checked 1 hr ago. Last stored result reached it in 265 ms.
Official status
All clear
No active incidents in the official feed Official status page
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 20:00 | 0 | 0.0 | 225 ms | 0 |
| 22:00 | 0 | 0.0 | 369 ms | 0 |
| 00:00 | 0 | 0.0 | 286 ms | 0 |
| 02:00 | 0 | 0.0 | 175 ms | 0 |
| 04:15 | 0 | 0.0 | 206 ms | 0 |
| 06:15 | 0 | 0.0 | 608 ms | 0 |
| 08:30 | 0 | 0.0 | 385 ms | 0 |
| 10:30 | 0 | 0.0 | 318 ms | 0 |
| 12:15 | 0 | 0.0 | 358 ms | 0 |
| 14:15 | 0 | 0.0 | 234 ms | 0 |
| 16:15 | 0 | 0.0 | 265 ms | 0 |
| 17:45 | 0 | 0.0 | 265 ms | 0 |
Reliability
97.56%Uptime · 30 days
97.56%Uptime · 90 days
1 / 1Outages · 30 / 90 days
2 h 2 minAverage outage
97.56% 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.
Embed this status: free live 21st.dev badge
Free, no iframe or script. Updates every minute and links back here. More options on the embed page · badge docs · JSON · MCP server
Past outages
Having trouble with 21st.dev?
One report per service every 10 minutes from this network. No account.
Follow 21st.dev
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.
About 21st.dev
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.56% over 8 days of checks. We logged 1 public incident since monitoring began 8 days ago.
Response time over the last 24 hours: 308 ms average, 175–608 ms range across 12 successful checks.
Questions
Is 21st.dev down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
When was 21st.dev last down?
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.
What is 21st.dev's uptime?
From our own checks: 97.56% over 8 days of checks.
How fast does 21st.dev respond?
308 ms on average over the last 24 hours (175–608 ms).
Does 21st.dev have an official status page?
Yes, at https://status.21st.dev.
21st.dev not working for me but the status is fine. What now?
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.