User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / Productivity
code42.com · Productivity
Is Code 42 down?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Is it just me?
Tests code42.com from your browser and compares it with our checks, the official status, and user reports.
Your browser → code42.com—
Your browser → us—
Our checksReaching it
Official · ReportsAll clear · Near baseline
Press Run testNothing leaves your browser except a request to the site and to us.
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, and places with fewer than 3 reports are not shown. Updates every minute.
What's broken
Our checks
Reaching it
Last check reached it in 591 ms · 5 min ago.
Official status
All clear
All Systems Operational Official status page
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 03:00 | 0 | 0.0 | 893 ms | 0 |
| 03:15 | 0 | 0.0 | 710 ms | 0 |
| 03:30 | 0 | 0.0 | 1424 ms | 0 |
| 03:45 | 0 | 0.0 | 606 ms | 0 |
| 04:00 | 0 | 0.0 | 1196 ms | 0 |
| 04:15 | 0 | 0.0 | 1200 ms | 0 |
| 04:30 | 0 | 0.0 | 1558 ms | 0 |
| 04:45 | 0 | 0.0 | 859 ms | 0 |
| 05:00 | 0 | 0.0 | 2125 ms | 0 |
| 05:15 | 0 | 0.0 | 621 ms | 0 |
| 05:30 | 0 | 0.0 | 863 ms | 0 |
| 05:45 | 0 | 0.0 | 692 ms | 0 |
| 06:00 | 0 | 0.0 | 1215 ms | 0 |
| 06:15 | 0 | 0.0 | 936 ms | 0 |
| 06:30 | 0 | 0.0 | 294 ms | 0 |
| 06:45 | 0 | 0.0 | 755 ms | 0 |
| 07:00 | 0 | 0.0 | 1253 ms | 0 |
| 07:15 | 0 | 0.0 | 672 ms | 0 |
| 07:30 | 0 | 0.0 | 886 ms | 0 |
| 07:45 | 0 | 0.0 | 1146 ms | 0 |
| 08:00 | 0 | 0.0 | 813 ms | 0 |
| 08:15 | 0 | 0.0 | 1258 ms | 0 |
| 08:30 | 0 | 0.0 | 588 ms | 0 |
| 08:45 | 0 | 0.0 | 932 ms | 0 |
| 09:00 | 0 | 0.0 | 828 ms | 0 |
| 09:15 | 0 | 0.0 | 749 ms | 0 |
| 09:30 | 0 | 0.0 | 735 ms | 0 |
| 09:45 | 0 | 0.0 | 973 ms | 0 |
| 10:00 | 0 | 0.0 | 675 ms | 0 |
| 10:15 | 0 | 0.0 | 591 ms | 0 |
Reliability
100%Uptime · 30 days
100%Uptime · 90 days
0 / 0Outages · 30 / 90 days
—Average outage
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 1 days of data so far, so the 90-day numbers fill in over time.
Embed a live Code 42 status badge
Free, no iframe or script. Updates every minute and links back here. More options on the embed page · JSON · MCP server
Past outages
No outages on record for Code 42 yet. Outages of 10 minutes or more get their own page here.
Having trouble with Code 42?
One report per service every 10 minutes from this network. No account.
Follow Code 42
Get an email when Code 42 goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Code 42 alerts to Slack, Discord or a webhook — free.
Questions
Is Code 42 down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Code 42 not working for me but the status is fine. What now?
If Code 42 is not working only for you, it is usually local: try a different browser or the app, switch between Wi-Fi and mobile data, and clear the cache. If lots of people report it here at the same time, the problem is on Code 42's side.
How does Damn is it down decide Code 42's status?
Three signals. Anonymous reports are compared with the usual volume for this hour. HTTP checks from Cloudflare have to fail twice in a row before we call our side down. When the vendor publishes a status JSON feed, that incident level is included too.
How often is Code 42 checked?
About every five minutes. The cron runs each minute and rotates through the catalog, so a full pass takes a few minutes.