Damn, is it down?

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.

What's broken? (optional)
Is it just me?
No problems detected

Live diagnosis

Is it just me?

Finds which layer is broken (the service, its provider, your ISP, DNS, or your own network) and what to try.

Your browser → code42.com—
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, and places with fewer than 3 reports are not shown. Updates every minute.

User reports

0

Near baseline. 0 in the last hour. Typical hour is about 0.

Our checks

Reaching it

Last check reached it in 862 ms · 2 min ago.

Reports and checks

Reports compared with the typical volume, with check latency and failures overlaid102125 ms16:1522:1504:1510:0016:00
ReportsTypical baselineCheck latencyFailed checkTimes in UTC
Numbers behind the chart
Time (UTC)ReportsBaselineLatencyFailed checks
04:1500.01200 ms0
04:3000.01558 ms0
04:4500.0859 ms0
05:0000.02125 ms0
05:1500.0621 ms0
05:3000.0863 ms0
05:4500.0692 ms0
06:0000.01215 ms0
06:1500.0936 ms0
06:3000.0294 ms0
06:4500.0755 ms0
07:0000.01253 ms0
07:1500.0672 ms0
07:3000.0886 ms0
07:4500.01146 ms0
08:0000.0813 ms0
08:1500.01258 ms0
08:3000.0588 ms0
08:4500.0932 ms0
09:0000.0828 ms0
09:1500.0749 ms0
09:3000.0735 ms0
09:4500.0973 ms0
10:0000.0675 ms0
10:1500.0591 ms0
10:3000.01127 ms0
10:4500.0643 ms0
11:0000.01580 ms0
11:1500.0553 ms0
11:3000.0971 ms0
11:4500.0564 ms0
12:0000.0789 ms0
12:1500.0766 ms0
12:3000.01425 ms0
12:4500.01380 ms0
13:0000.0841 ms0
13:1500.0632 ms0
13:3000.0807 ms0
13:4500.0569 ms0
14:0000.01117 ms0
14:1500.0581 ms0
14:3000.0473 ms0
14:4500.0946 ms0
15:0000.01010 ms0
15:1500.0795 ms0
15:3000.0554 ms0
15:4500.0764 ms0
16:0000.0862 ms0

Reliability

Score 100/100 · grade A

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.

Code 42 status badge 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

Code 42 status and 30-day uptime badge

Past outages

No outages on record for Code 42 yet. Outages of 10 minutes or more get their own page here.

All Code 42 outages · Every recent outage

Having trouble with Code 42?

One report per service every 10 minutes from this network. No account.

What's broken? (optional)

Notes are stored for rate-limit context and are not shown publicly.

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.