User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / AI
Is OpenCase down?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Is it just me?
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Your browser → opencase.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. Every report with a known place can appear on the map. Updates every minute.
What's broken
Recent reports
Each row is a time, a coarse place, and a problem type from a new report. Optional notes stay private. Places with fewer than 3 reports in the last 8 days are shown without a location.
No public reports yet.
Our checks
Reaching it
Last checked 2 hr ago. Last stored result reached it in 103 ms.
Official status
All clear
No active incidents in the official feed Official status page
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 12 | 0 | 0.0 | 108 ms | 0 |
| Mon 14 | 0 | 0.0 | 126 ms | 0 |
| Mon 16 | 0 | 0.0 | 168 ms | 0 |
| Mon 18 | 0 | 0.0 | 124 ms | 0 |
| Mon 20 | 0 | 0.0 | 138 ms | 0 |
| Mon 23 | 0 | 0.0 | 297 ms | 0 |
| Tue 01 | 0 | 0.0 | 205 ms | 0 |
| Tue 03 | 0 | 0.0 | 338 ms | 0 |
| Tue 05 | 0 | 0.0 | 199 ms | 0 |
| Tue 07 | 0 | 0.0 | 96 ms | 0 |
| Tue 09 | 0 | 0.0 | 221 ms | 0 |
| Tue 11 | 0 | 0.0 | 167 ms | 0 |
| Tue 13 | 0 | 0.0 | 268 ms | 0 |
| Tue 16 | 0 | 0.0 | 135 ms | 0 |
| Tue 18 | 0 | 0.0 | 182 ms | 0 |
| Tue 20 | 0 | 0.0 | 165 ms | 0 |
| Tue 22 | 0 | 0.0 | 156 ms | 0 |
| Wed 01 | 0 | 0.0 | 143 ms | 0 |
| Wed 03 | 0 | 0.0 | 225 ms | 0 |
| Wed 05 | 0 | 0.0 | 179 ms | 0 |
| Wed 07 | 0 | 0.0 | 195 ms | 0 |
| Wed 10 | 0 | 0.0 | 224 ms | 0 |
| Wed 12 | 0 | 0.0 | 248 ms | 0 |
| Wed 14 | 0 | 0.0 | 186 ms | 0 |
| Wed 16 | 0 | 0.0 | 182 ms | 0 |
| Wed 18 | 0 | 0.0 | 119 ms | 0 |
| Wed 20 | 0 | 0.0 | 156 ms | 0 |
| Wed 23 | 0 | 0.0 | 181 ms | 0 |
| Thu 01 | 0 | 0.0 | 238 ms | 0 |
| Thu 03 | 0 | 0.0 | 213 ms | 0 |
| Thu 05 | 0 | 0.0 | 228 ms | 0 |
| Thu 07 | 0 | 0.0 | 264 ms | 0 |
| Thu 09 | 0 | 0.0 | 213 ms | 0 |
| Thu 11 | 0 | 0.0 | 87 ms | 0 |
| Thu 13 | 0 | 0.0 | 185 ms | 0 |
| Thu 15 | 0 | 0.0 | 206 ms | 0 |
| Thu 17 | 0 | 0.0 | 88 ms | 0 |
| Thu 19 | 0 | 0.0 | 83 ms | 0 |
| Thu 21 | 0 | 0.0 | 198 ms | 0 |
| Fri 00 | 0 | 0.0 | 146 ms | 0 |
| Fri 02 | 0 | 0.0 | 215 ms | 0 |
| Fri 04 | 0 | 0.0 | 107 ms | 0 |
| Fri 06 | 0 | 0.0 | 290 ms | 0 |
| Fri 08 | 0 | 0.0 | 155 ms | 0 |
| Fri 10 | 0 | 0.0 | 106 ms | 0 |
| Fri 11 | 0 | 0.0 | 104 ms | 0 |
| Fri 12 | 0 | 0.0 | 97 ms | 0 |
| Fri 14 | 0 | 0.0 | 103 ms | 0 |
Reliability
100%Uptime · 30 days
100%Uptime · 90 days
0 / 0Outages · 30 / 90 days
—Average outage
100% uptime · No user reports in the last 24h
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 7 days of data so far, so the 90-day numbers fill in over time.
Embed this status: free live OpenCase badge
Free, no iframe or script. Updates every minute and links back here. More options on the embed page · badge docs · JSON · MCP server
Past outages
No outages on record for OpenCase yet. Outages of 10 minutes or more get their own page here.
Having trouble with OpenCase?
One report per service every 10 minutes from this network. No account.
Follow OpenCase
Get an email when OpenCase goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send OpenCase alerts to Slack, Discord or a webhook — free.
About OpenCase
OpenCase is listed in our AI category and checked at opencase.com. Legal AI that answers research questions with real case law, statutes, and regulations — citations verified against their primary source. Built for lawyers.
OpenCase publishes an official status page at status.opencase.com; when we can read it, its incident level is folded into the status shown here.
Typical issues with AI services: slow or failed responses, rate-limit errors, and API timeouts.
Measured uptime from our checks: 100% over 7 days of checks. No public incidents logged since monitoring began 7 days ago.
Response time over the last 24 hours: 142 ms average, 83–290 ms range across 13 successful checks.
Questions
Is OpenCase down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
When was OpenCase last down?
We have not recorded a public OpenCase incident since monitoring began 7 days ago.
What is OpenCase's uptime?
From our own checks: 100% over 7 days of checks.
How fast does OpenCase respond?
142 ms on average over the last 24 hours (83–290 ms).
Does OpenCase have an official status page?
Yes, at https://status.opencase.com.
OpenCase not working for me but the status is fine. What now?
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For AI services, watch for slow or failed responses, rate-limit errors, and API timeouts. If many people report OpenCase here at once, the problem is on OpenCase's side.
How we detect and verify outages · Dispute this report · We review disputes within 24 hours.
Community comments
Share what you are seeing with OpenCase. No account needed. Comments are public, separate from outage reports. Do not include personal information.
No links or domains. 3 comments per service and 6 total per hour, per device and network. New contributors get one visible comment; further comments wait for review.