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 30 min ago. Last stored result reached it in 180 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 15 | 0 | 0.0 | 133 ms | 0 |
| Mon 17 | 0 | 0.0 | 183 ms | 0 |
| Mon 19 | 0 | 0.0 | 102 ms | 0 |
| Mon 21 | 0 | 0.0 | 180 ms | 0 |
| Mon 23 | 0 | 0.0 | 124 ms | 0 |
| Tue 01 | 0 | 0.0 | 179 ms | 0 |
| Tue 03 | 0 | 0.0 | 89 ms | 0 |
| Tue 06 | 0 | 0.0 | 284 ms | 0 |
| Tue 08 | 0 | 0.0 | 116 ms | 0 |
| Tue 10 | 0 | 0.0 | 93 ms | 0 |
| Tue 12 | 0 | 0.0 | 71 ms | 0 |
| Tue 14 | 0 | 0.0 | 141 ms | 0 |
| Tue 16 | 0 | 0.0 | 270 ms | 0 |
| Tue 19 | 0 | 0.0 | 159 ms | 0 |
| Tue 21 | 0 | 0.0 | 296 ms | 0 |
| Tue 23 | 0 | 0.0 | 93 ms | 0 |
| Wed 01 | 0 | 0.0 | 106 ms | 0 |
| Wed 04 | 0 | 0.0 | 223 ms | 0 |
| Wed 06 | 0 | 0.0 | 137 ms | 0 |
| Wed 08 | 0 | 0.0 | 170 ms | 0 |
| Wed 10 | 0 | 0.0 | 68 ms | 0 |
| Wed 12 | 0 | 0.0 | 121 ms | 0 |
| Wed 13 | 0 | 0.0 | 48 ms | 0 |
| Wed 15 | 0 | 0.0 | 108 ms | 0 |
| Wed 17 | 0 | 0.0 | 121 ms | 0 |
| Wed 19 | 0 | 0.0 | 224 ms | 0 |
| Wed 21 | 0 | 0.0 | 160 ms | 0 |
| Wed 23 | 0 | 0.0 | 136 ms | 0 |
| Thu 01 | 0 | 0.0 | 130 ms | 0 |
| Thu 03 | 0 | 0.0 | 187 ms | 0 |
| Thu 05 | 0 | 0.0 | 132 ms | 0 |
| Thu 08 | 0 | 0.0 | 256 ms | 0 |
| Thu 10 | 0 | 0.0 | 223 ms | 0 |
| Thu 12 | 0 | 0.0 | 116 ms | 0 |
| Thu 14 | 0 | 0.0 | 202 ms | 0 |
| Thu 16 | 0 | 0.0 | 77 ms | 0 |
| Thu 18 | 0 | 0.0 | 73 ms | 0 |
| Thu 20 | 0 | 0.0 | 192 ms | 0 |
| Thu 22 | 0 | 0.0 | 124 ms | 0 |
| Fri 00 | 0 | 0.0 | 289 ms | 0 |
| Fri 02 | 0 | 0.0 | 93 ms | 0 |
| Fri 04 | 0 | 0.0 | 220 ms | 0 |
| Fri 06 | 0 | 0.0 | 96 ms | 0 |
| Fri 08 | 0 | 0.0 | 82 ms | 0 |
| Fri 10 | 0 | 0.0 | 94 ms | 0 |
| Fri 12 | 0 | 0.0 | 107 ms | 0 |
| Fri 14 | 0 | 0.0 | 102 ms | 0 |
| Fri 16 | 0 | 0.0 | 180 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 CodeCrafters 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 CodeCrafters goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send CodeCrafters alerts to Slack, Discord or a webhook — free.
We track CodeCrafters (codecrafters.io) as part of the AI group. Build your own Redis, Git, SQLite, and more from scratch. Advanced challenges designed for experienced engineers, used by developers at Google, OpenAI, and Vercel.
CodeCrafters publishes an official status page at status.codecrafters.io; 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: 100% over 8 days of checks. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 134 ms average, 70–289 ms range across 13 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public CodeCrafters incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
134 ms on average over the last 24 hours (70–289 ms).
Yes, at https://status.codecrafters.io.
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 CodeCrafters here at once, the problem is on CodeCrafters'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 CodeCrafters. 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.