User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / Education
Is Code.org 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 → code.org—
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 39 min ago. Last stored result reached it in 55 ms.
Official status
All clear
All systems operational Official status page
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 03 | 0 | 0.0 | 36 ms | 0 |
| Mon 05 | 0 | 0.0 | 45 ms | 0 |
| Mon 07 | 0 | 0.0 | 72 ms | 0 |
| Mon 09 | 0 | 0.0 | 66 ms | 0 |
| Mon 11 | 0 | 0.0 | 70 ms | 0 |
| Mon 13 | 0 | 0.0 | 76 ms | 0 |
| Mon 15 | 0 | 0.0 | 82 ms | 0 |
| Mon 18 | 0 | 0.0 | 97 ms | 0 |
| Mon 20 | 0 | 0.0 | 47 ms | 0 |
| Mon 22 | 0 | 0.0 | 43 ms | 0 |
| Tue 00 | 0 | 0.0 | 65 ms | 0 |
| Tue 02 | 0 | 0.0 | 145 ms | 0 |
| Tue 04 | 0 | 0.0 | 47 ms | 0 |
| Tue 06 | 0 | 0.0 | 74 ms | 0 |
| Tue 08 | 0 | 0.0 | 58 ms | 0 |
| Tue 10 | 0 | 0.0 | 63 ms | 0 |
| Tue 13 | 0 | 0.0 | 84 ms | 0 |
| Tue 15 | 0 | 0.0 | 54 ms | 0 |
| Tue 17 | 0 | 0.0 | 52 ms | 0 |
| Tue 19 | 0 | 0.0 | 76 ms | 0 |
| Tue 22 | 0 | 0.0 | 71 ms | 0 |
| Wed 00 | 0 | 0.0 | 55 ms | 0 |
| Wed 02 | 0 | 0.0 | 107 ms | 0 |
| Wed 04 | 0 | 0.0 | 72 ms | 0 |
| Wed 06 | 0 | 0.0 | 110 ms | 0 |
| Wed 09 | 0 | 0.0 | 130 ms | 0 |
| Wed 11 | 0 | 0.0 | 215 ms | 0 |
| Wed 13 | 0 | 0.0 | 134 ms | 0 |
| Wed 15 | 0 | 0.0 | 159 ms | 0 |
| Wed 17 | 0 | 0.0 | 51 ms | 0 |
| Wed 20 | 0 | 0.0 | 49 ms | 0 |
| Wed 22 | 0 | 0.0 | 113 ms | 0 |
| Thu 00 | 0 | 0.0 | 69 ms | 0 |
| Thu 02 | 0 | 0.0 | 37 ms | 0 |
| Thu 04 | 0 | 0.0 | 78 ms | 0 |
| Thu 06 | 0 | 0.0 | 51 ms | 0 |
| Thu 08 | 0 | 0.0 | 63 ms | 0 |
| Thu 10 | 0 | 0.0 | 63 ms | 0 |
| Thu 12 | 0 | 0.0 | 34 ms | 0 |
| Thu 14 | 0 | 0.0 | 42 ms | 0 |
| Thu 16 | 0 | 0.0 | 54 ms | 0 |
| Thu 19 | 0 | 0.0 | 142 ms | 0 |
| Thu 21 | 0 | 0.0 | 57 ms | 0 |
| Thu 23 | 0 | 0.0 | 160 ms | 0 |
| Fri 00 | 0 | 0.0 | 78 ms | 0 |
| Fri 02 | 0 | 0.0 | 146 ms | 0 |
| Fri 04 | 0 | 0.0 | 64 ms | 0 |
| Fri 07 | 0 | 0.0 | 55 ms | 0 |
Reliability
100%Uptime · 30 days
100%Uptime · 90 days
0 / 0Outages · 30 / 90 days
—Average outage
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.
Embed this status: free live Code.org 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
No outages on record for Code.org yet. Outages of 10 minutes or more get their own page here.
Having trouble with Code.org?
One report per service every 10 minutes from this network. No account.
Follow Code.org
Get an email when Code.org goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Code.org alerts to Slack, Discord or a webhook — free.
About Code.org
We track Code.org (code.org) as part of the Education group. Bring computer science and AI education to your classroom with CodeAI’s free K–12 curriculum, hands-on projects, and teacher professional development—no prior experience needed.
Code.org publishes an official status page at status.code.org; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with education services: learning management systems and student portals slowing down around assignment deadlines, exams and registration.
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: 77 ms average, 24–160 ms range across 13 successful checks.
Questions
Is Code.org down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
When was Code.org last down?
We have not recorded a public Code.org incident since monitoring began 8 days ago.
What is Code.org's uptime?
From our own checks: 100% over 8 days of checks.
How fast does Code.org respond?
77 ms on average over the last 24 hours (24–160 ms).
Does Code.org have an official status page?
Yes, at https://status.code.org.
Code.org 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 education services, watch for learning management systems and student portals slowing down around assignment deadlines, exams and registration. If many people report Code.org here at once, the problem is on Code.org'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 Code.org. 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.