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 2 min ago. Last stored result reached it in 380 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 17 | 0 | 0.0 | 3089 ms | 0 |
| Mon 19 | 0 | 0.0 | 1769 ms | 0 |
| Mon 22 | 0 | 0.0 | 1066 ms | 0 |
| Tue 00 | 0 | 0.0 | 364 ms | 0 |
| Tue 02 | 0 | 0.0 | 366 ms | 0 |
| Tue 04 | 0 | 0.0 | 412 ms | 0 |
| Tue 06 | 0 | 0.0 | 369 ms | 0 |
| Tue 08 | 0 | 0.0 | 358 ms | 0 |
| Tue 10 | 0 | 0.0 | 274 ms | 0 |
| Tue 12 | 0 | 0.0 | 374 ms | 0 |
| Tue 15 | 0 | 0.0 | 382 ms | 0 |
| Tue 17 | 0 | 0.0 | 462 ms | 0 |
| Tue 19 | 0 | 0.0 | 568 ms | 0 |
| Tue 21 | 0 | 0.0 | 530 ms | 0 |
| Wed 00 | 0 | 0.0 | 323 ms | 0 |
| Wed 02 | 0 | 0.0 | 300 ms | 0 |
| Wed 04 | 0 | 0.0 | 406 ms | 0 |
| Wed 06 | 0 | 0.0 | 405 ms | 0 |
| Wed 09 | 0 | 0.0 | 387 ms | 0 |
| Wed 11 | 0 | 0.0 | 354 ms | 0 |
| Wed 13 | 0 | 0.0 | 397 ms | 0 |
| Wed 15 | 0 | 0.0 | 526 ms | 0 |
| Wed 17 | 0 | 0.0 | 300 ms | 0 |
| Wed 19 | 0 | 0.0 | 255 ms | 0 |
| Wed 22 | 0 | 0.0 | 756 ms | 0 |
| Thu 00 | 0 | 0.0 | 426 ms | 0 |
| Thu 03 | 0 | 0.0 | 424 ms | 0 |
| Thu 04 | 0 | 0.0 | 382 ms | 0 |
| Thu 06 | 0 | 0.0 | 471 ms | 0 |
| Thu 08 | 0 | 0.0 | 428 ms | 0 |
| Thu 10 | 0 | 0.0 | 374 ms | 0 |
| Thu 12 | 0 | 0.0 | 382 ms | 0 |
| Thu 15 | 0 | 0.0 | 421 ms | 0 |
| Thu 17 | 0 | 0.0 | 358 ms | 0 |
| Thu 19 | 0 | 0.0 | 366 ms | 0 |
| Thu 21 | 0 | 0.0 | 253 ms | 0 |
| Thu 23 | 0 | 0.0 | 362 ms | 0 |
| Fri 01 | 0 | 0.0 | 375 ms | 0 |
| Fri 03 | 0 | 0.0 | 291 ms | 0 |
| Fri 05 | 0 | 0.0 | 363 ms | 0 |
| Fri 07 | 0 | 0.0 | 372 ms | 0 |
| Fri 09 | 0 | 0.0 | 353 ms | 0 |
| Fri 10 | 0 | 0.0 | 214 ms | 0 |
| Fri 12 | 0 | 0.0 | 368 ms | 0 |
| Fri 14 | 0 | 0.0 | 333 ms | 0 |
| Fri 16 | 0 | 0.0 | 237 ms | 0 |
| Fri 17 | 0 | 0.0 | 427 ms | 0 |
| Fri 18 | 0 | 0.0 | 380 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 8 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Document Crunch 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 Document Crunch goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Document Crunch alerts to Slack, Discord or a webhook — free.
We track Document Crunch (documentcrunch.com) as part of the AI group. Streamline construction document review and risk analysis with smart, AI-powered management tools built for construction to mitigate project risk.
Document Crunch publishes an official status page at status.documentcrunch.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 8 days of checks. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 335 ms average, 214–427 ms range across 14 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Document Crunch incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
335 ms on average over the last 24 hours (214–427 ms).
Yes, at https://status.documentcrunch.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 Document Crunch here at once, the problem is on Document Crunch'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 Document Crunch. 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.