User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / Government
reemployct.dol.ct.gov · Government
Is Connecticut unemployment down?
Something is off: our checks are slower than usual or had a single recent failure.
What to try while Connecticut unemployment is having problems
Estimated fix: Past Connecticut unemployment outages lasted 18 min (median, typically 18 min–24 min; 5 outages we recorded).
- 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 → reemployct.dol.ct.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.
What's broken
Our checks
Slow or flaky
Last check failed · 2 min ago.
Official status
No status feed
Connecticut unemployment does not publish a status feed we can read.
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 13:00 | 0 | 0.0 | 125 ms | 0 |
| 13:15 | 0 | 0.0 | 236 ms | 1 |
| 13:30 | 0 | 0.0 | — | 1 |
| 13:45 | 0 | 0.0 | 386 ms | 1 |
| 14:00 | 0 | 0.0 | 473 ms | 0 |
| 14:15 | 0 | 0.0 | 402 ms | 0 |
| 14:30 | 0 | 0.0 | — | 2 |
| 14:45 | 0 | 0.0 | — | 2 |
| 15:00 | 0 | 0.0 | 324 ms | 0 |
| 15:15 | 0 | 0.0 | 453 ms | 1 |
| 15:30 | 0 | 0.0 | 189 ms | 0 |
| 15:45 | 0 | 0.0 | 432 ms | 1 |
| 16:00 | 0 | 0.0 | — | 2 |
| 16:15 | 0 | 0.0 | — | 2 |
| 16:30 | 0 | 0.0 | — | 1 |
| 16:45 | 0 | 0.0 | 510 ms | 1 |
| 17:00 | 0 | 0.0 | — | 1 |
| 17:15 | 0 | 0.0 | 144 ms | 0 |
| 17:30 | 0 | 0.0 | — | 2 |
| 17:45 | 0 | 0.0 | — | 1 |
| 18:00 | 0 | 0.0 | 291 ms | 1 |
| 18:15 | 0 | 0.0 | — | 2 |
| 18:30 | 0 | 0.0 | 202 ms | 0 |
| 18:45 | 0 | 0.0 | — | 1 |
Reliability
43.24%Uptime · 30 days
43.24%Uptime · 90 days
4 / 4Outages · 30 / 90 days
29 minAverage 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 Connecticut unemployment 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
Having trouble with Connecticut unemployment?
One report per service every 10 minutes from this network. No account.
Follow Connecticut unemployment
Get an email when Connecticut unemployment goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Connecticut unemployment alerts to Slack, Discord or a webhook — free.
Questions
Is Connecticut unemployment down right now?
Something is off: our checks are slower than usual or had a single recent failure.
Connecticut unemployment not working for me but the status is fine. What now?
If Connecticut 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 Connecticut unemployment's side.
How does Damn is it down decide Connecticut 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 Connecticut unemployment checked?
About every five minutes. The cron runs each minute and rotates through the catalog, so a full pass takes a few minutes.