User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Government
does.dc.gov · Government
Checks are succeeding and user reports are near the baseline.
Live diagnosis
Finds which layer is broken (the service, its provider, your ISP, DNS, or your own network) and what 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, and places with fewer than 3 reports are not shown. Updates every minute.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last check reached it in 57 ms · 3 min ago.
No status feed
District of Columbia unemployment does not publish a status feed we can read.
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 13:00 | 0 | 0.0 | 20 ms | 0 |
| 13:15 | 0 | 0.0 | 630 ms | 0 |
| 13:30 | 0 | 0.0 | 801 ms | 0 |
| 13:45 | 0 | 0.0 | — | 0 |
| 14:00 | 0 | 0.0 | 81 ms | 0 |
| 14:15 | 0 | 0.0 | 402 ms | 0 |
| 14:30 | 0 | 0.0 | 822 ms | 0 |
| 14:45 | 0 | 0.0 | 400 ms | 0 |
| 15:00 | 0 | 0.0 | 221 ms | 0 |
| 15:15 | 0 | 0.0 | 487 ms | 0 |
| 15:30 | 0 | 0.0 | 33 ms | 0 |
| 15:45 | 0 | 0.0 | 417 ms | 0 |
| 16:00 | 0 | 0.0 | 495 ms | 0 |
| 16:15 | 0 | 0.0 | 465 ms | 0 |
| 16:30 | 0 | 0.0 | 405 ms | 0 |
| 16:45 | 0 | 0.0 | 314 ms | 0 |
| 17:00 | 0 | 0.0 | 28 ms | 0 |
| 17:15 | 0 | 0.0 | 35 ms | 0 |
| 17:30 | 0 | 0.0 | 229 ms | 0 |
| 17:45 | 0 | 0.0 | — | 0 |
| 18:00 | 0 | 0.0 | 566 ms | 0 |
| 18:15 | 0 | 0.0 | 3217 ms | 0 |
| 18:30 | 0 | 0.0 | 54 ms | 0 |
| 18:45 | 0 | 0.0 | 252 ms | 0 |
| 19:00 | 0 | 0.0 | 501 ms | 0 |
| 19:15 | 0 | 0.0 | 492 ms | 0 |
| 19:30 | 0 | 0.0 | 18 ms | 0 |
| 19:45 | 0 | 0.0 | 19 ms | 0 |
| 20:00 | 0 | 0.0 | 863 ms | 0 |
| 20:15 | 0 | 0.0 | 361 ms | 0 |
| 20:30 | 0 | 0.0 | 480 ms | 0 |
| 20:45 | 0 | 0.0 | 384 ms | 0 |
| 21:00 | 0 | 0.0 | 215 ms | 0 |
| 21:15 | 0 | 0.0 | 19 ms | 0 |
| 21:30 | 0 | 0.0 | 33 ms | 0 |
| 21:45 | 0 | 0.0 | 710 ms | 0 |
| 22:00 | 0 | 0.0 | 474 ms | 0 |
| 22:15 | 0 | 0.0 | 448 ms | 0 |
| 22:30 | 0 | 0.0 | 211 ms | 0 |
| 22:45 | 0 | 0.0 | 57 ms | 0 |
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.
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
One report per service every 10 minutes from this network. No account.
Get an email when District of Columbia unemployment goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send District of Columbia unemployment alerts to Slack, Discord or a webhook — free.
We track District of Columbia unemployment (does.dc.gov) as part of the Government group. Live checks and user reports.
District of Columbia unemployment has no official status feed we can read, so this page relies on our own checks and user reports.
What usually goes wrong with government services: portal sign-in failures, forms not submitting, and slow pages during deadlines.
Measured uptime from our checks: 100% over 1 day of checks. No public incidents logged since monitoring began 1 day ago.
Response time over the last 24 hours: 435 ms average, 13–6370 ms range across 61 successful checks.
Checks are succeeding and user reports are near the baseline.
We have not recorded a public District of Columbia unemployment incident since monitoring began 1 day ago.
From our own checks: 100% over 1 day of checks.
435 ms on average over the last 24 hours (13–6370 ms).
Not one we can read. This page uses independent checks of does.dc.gov and user reports.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For government services, watch for portal sign-in failures, forms not submitting, and slow pages during deadlines. If many people report District of Columbia unemployment here at once, the problem is on District of Columbia unemployment's side.