All services / Government

does.dc.gov · Government

Is District of Columbia unemployment down?

Something is off: our checks are slower than usual or had a single recent failure.

What's broken? (optional)
Is it just me?
Degraded performance

What to try while District of Columbia unemployment is having problems

Estimated fix: Not enough District of Columbia unemployment history yet; similar Government outages lasted 9 min (median, typically 8 min–18 min; 41 outages).

  • Try again outside peak hours; paper or phone options usually stay available.

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 → does.dc.gov—
Your browser → us—
Our checksSlow or flaky
Official · ReportsNo status feed · 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

Slow or flaky

Last check reached it in 54 ms · 9 min ago.

Official status

No status feed

District of Columbia unemployment does not publish a status feed we can read.

Reports and checks

Reports compared with the typical volume, with check latency and failures overlaid103217 ms19:0001:0007:0012:4518:45
ReportsTypical baselineCheck latencyFailed checkTimes in UTC
Numbers behind the chart
Time (UTC)ReportsBaselineLatencyFailed checks
13:0000.020 ms0
13:1500.0630 ms0
13:3000.0801 ms0
13:4500.0—0
14:0000.081 ms0
14:1500.0402 ms0
14:3000.0822 ms0
14:4500.0400 ms0
15:0000.0221 ms0
15:1500.0487 ms0
15:3000.033 ms0
15:4500.0417 ms0
16:0000.0495 ms0
16:1500.0465 ms0
16:3000.0405 ms0
16:4500.0314 ms0
17:0000.028 ms0
17:1500.035 ms0
17:3000.0229 ms0
17:4500.0—0
18:0000.0566 ms0
18:1500.03217 ms0
18:3000.054 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.

District of Columbia unemployment status badge Embed a live District of Columbia unemployment status badge

Free, no iframe or script. Updates every minute and links back here. More options on the embed page · JSON · MCP server

District of Columbia unemployment status and 30-day uptime badge

Past outages

No outages on record for District of Columbia unemployment yet. Outages of 10 minutes or more get their own page here.

All District of Columbia unemployment outages · Every recent outage

Having trouble with District of Columbia unemployment?

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 District of Columbia unemployment down right now?

Something is off: our checks are slower than usual or had a single recent failure.

District of Columbia unemployment not working for me but the status is fine. What now?

If District of Columbia unemployment 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 District of Columbia unemployment's side.

How does Damn is it down decide District of Columbia unemployment'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 District of Columbia unemployment checked?

About every five minutes. The cron runs each minute and rotates through the catalog, so a full pass takes a few minutes.