User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Gaming
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 1 hr ago. Last stored result reached it in 189 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 13 | 0 | 0.0 | 287 ms | 0 |
| Mon 15 | 0 | 0.0 | 113 ms | 0 |
| Mon 17 | 0 | 0.0 | 29 ms | 0 |
| Mon 19 | 0 | 0.0 | 53 ms | 0 |
| Mon 21 | 0 | 0.0 | 27 ms | 0 |
| Mon 23 | 0 | 0.0 | 32 ms | 0 |
| Tue 01 | 0 | 0.0 | 409 ms | 0 |
| Tue 03 | 0 | 0.0 | 400 ms | 0 |
| Tue 06 | 0 | 0.0 | 184 ms | 0 |
| Tue 08 | 0 | 0.0 | 68 ms | 0 |
| Tue 10 | 0 | 0.0 | 314 ms | 0 |
| Tue 12 | 0 | 0.0 | 209 ms | 0 |
| Tue 14 | 0 | 0.0 | 116 ms | 0 |
| Tue 16 | 0 | 0.0 | 107 ms | 0 |
| Tue 19 | 0 | 0.0 | 36 ms | 0 |
| Tue 21 | 0 | 0.0 | 116 ms | 0 |
| Tue 23 | 0 | 0.0 | 33 ms | 0 |
| Wed 01 | 0 | 0.0 | 326 ms | 0 |
| Wed 04 | 0 | 0.0 | 42 ms | 0 |
| Wed 06 | 0 | 0.0 | 470 ms | 0 |
| Wed 08 | 0 | 0.0 | 68 ms | 0 |
| Wed 10 | 0 | 0.0 | 33 ms | 0 |
| Wed 12 | 0 | 0.0 | 69 ms | 0 |
| Wed 13 | 0 | 0.0 | 10 ms | 0 |
| Wed 15 | 0 | 0.0 | 328 ms | 0 |
| Wed 17 | 0 | 0.0 | 394 ms | 0 |
| Wed 19 | 0 | 0.0 | 35 ms | 0 |
| Wed 21 | 0 | 0.0 | 159 ms | 0 |
| Wed 23 | 0 | 0.0 | 382 ms | 0 |
| Thu 01 | 0 | 0.0 | 135 ms | 0 |
| Thu 03 | 0 | 0.0 | 101 ms | 0 |
| Thu 05 | 0 | 0.0 | 65 ms | 0 |
| Thu 08 | 0 | 0.0 | 190 ms | 0 |
| Thu 10 | 0 | 0.0 | 336 ms | 0 |
| Thu 12 | 0 | 0.0 | 395 ms | 0 |
| Thu 14 | 0 | 0.0 | 19 ms | 0 |
| Thu 16 | 0 | 0.0 | 243 ms | 0 |
| Thu 18 | 0 | 0.0 | 14 ms | 0 |
| Thu 20 | 0 | 0.0 | 98 ms | 0 |
| Thu 22 | 0 | 0.0 | 121 ms | 0 |
| Fri 00 | 0 | 0.0 | 67 ms | 0 |
| Fri 02 | 0 | 0.0 | 53 ms | 0 |
| Fri 03 | 0 | 0.0 | 77 ms | 0 |
| Fri 05 | 0 | 0.0 | 411 ms | 0 |
| Fri 07 | 0 | 0.0 | 180 ms | 0 |
| Fri 09 | 0 | 0.0 | 51 ms | 0 |
| Fri 11 | 0 | 0.0 | 36 ms | 0 |
| Fri 12 | 0 | 0.0 | 189 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 CodeCombat 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 CodeCombat goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send CodeCombat alerts to Slack, Discord or a webhook — free.
CodeCombat is listed in our Gaming category and checked at codecombat.com. Learn typed code through a programming game. Learn Python, JavaScript, and HTML as you solve puzzles and learn to make your own coding games and websites.
CodeCombat publishes an official status page at status.codecombat.com; when we can read it, its incident level is folded into the status shown here.
Typical issues with gaming services: login and matchmaking failures, server disconnects, and store or download errors.
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: 129 ms average, 14–471 ms range across 14 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public CodeCombat incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
129 ms on average over the last 24 hours (14–471 ms).
Yes, at https://status.codecombat.com.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For gaming services, watch for login and matchmaking failures, server disconnects, and store or download errors. If many people report CodeCombat here at once, the problem is on CodeCombat'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 CodeCombat. 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.