User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / AI
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps 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. Every report with a known place can appear on the map. Updates every minute.
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.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last checked 13 min ago. Last stored result reached it in 130 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 16 | 0 | 0.0 | 1300 ms | 0 |
| Mon 18 | 0 | 0.0 | 61 ms | 0 |
| Mon 20 | 0 | 0.0 | 76 ms | 0 |
| Mon 22 | 0 | 0.0 | 108 ms | 0 |
| Tue 00 | 0 | 0.0 | 101 ms | 0 |
| Tue 02 | 0 | 0.0 | 54 ms | 0 |
| Tue 04 | 0 | 0.0 | 88 ms | 0 |
| Tue 06 | 0 | 0.0 | 57 ms | 0 |
| Tue 09 | 0 | 0.0 | 41 ms | 0 |
| Tue 11 | 0 | 0.0 | 68 ms | 0 |
| Tue 13 | 0 | 0.0 | 109 ms | 0 |
| Tue 15 | 0 | 0.0 | 84 ms | 0 |
| Tue 17 | 0 | 0.0 | 120 ms | 0 |
| Tue 20 | 0 | 0.0 | 76 ms | 0 |
| Tue 22 | 0 | 0.0 | 87 ms | 0 |
| Wed 00 | 0 | 0.0 | 118 ms | 0 |
| Wed 02 | 0 | 0.0 | 51 ms | 0 |
| Wed 05 | 0 | 0.0 | 43 ms | 0 |
| Wed 07 | 0 | 0.0 | 98 ms | 0 |
| Wed 09 | 0 | 0.0 | 66 ms | 0 |
| Wed 11 | 0 | 0.0 | 92 ms | 0 |
| Wed 13 | 0 | 0.0 | 50 ms | 0 |
| Wed 15 | 0 | 0.0 | 62 ms | 0 |
| Wed 18 | 0 | 0.0 | 230 ms | 0 |
| Wed 20 | 0 | 0.0 | 93 ms | 0 |
| Wed 22 | 0 | 0.0 | 99 ms | 0 |
| Thu 00 | 0 | 0.0 | 105 ms | 0 |
| Thu 02 | 0 | 0.0 | 148 ms | 0 |
| Thu 04 | 0 | 0.0 | 104 ms | 0 |
| Thu 06 | 0 | 0.0 | 39 ms | 0 |
| Thu 08 | 0 | 0.0 | 71 ms | 0 |
| Thu 10 | 0 | 0.0 | 214 ms | 0 |
| Thu 12 | 0 | 0.0 | 56 ms | 0 |
| Thu 15 | 0 | 0.0 | 95 ms | 0 |
| Thu 17 | 0 | 0.0 | 119 ms | 0 |
| Thu 19 | 0 | 0.0 | 49 ms | 0 |
| Thu 21 | 0 | 0.0 | 74 ms | 0 |
| Thu 23 | 0 | 0.0 | 84 ms | 0 |
| Fri 01 | 0 | 0.0 | 89 ms | 0 |
| Fri 03 | 0 | 0.0 | 52 ms | 0 |
| Fri 05 | 0 | 0.0 | 78 ms | 0 |
| Fri 07 | 0 | 0.0 | 64 ms | 0 |
| Fri 09 | 0 | 0.0 | 32 ms | 0 |
| Fri 10 | 0 | 0.0 | 29 ms | 0 |
| Fri 12 | 0 | 0.0 | 145 ms | 0 |
| Fri 14 | 0 | 0.0 | 39 ms | 0 |
| Fri 16 | 0 | 0.0 | 84 ms | 0 |
| Fri 18 | 0 | 0.0 | 107 ms | 0 |
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.
No outages on record for BriefCatch yet. Outages of 10 minutes or more get their own page here.
One report per service every 10 minutes from this network. No account.
Get an email when BriefCatch goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send BriefCatch alerts to Slack, Discord or a webhook — free.
We track BriefCatch (briefcatch.com) as part of the AI group. Enhance legal writing with BriefCatch—the AI-powered legal software trusted by lawyers and judges to edit, refine, and elevate every document you write.
BriefCatch publishes an official status page at status.briefcatch.com; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong 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: 71 ms average, 29–145 ms range across 16 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public BriefCatch incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
71 ms on average over the last 24 hours (29–145 ms).
Yes, at https://status.briefcatch.com.
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 BriefCatch here at once, the problem is on BriefCatch'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 BriefCatch. 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.