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 1 hr ago. Last stored result reached it in 1385 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 20 | 0 | 0.0 | 1409 ms | 0 |
| Mon 22 | 0 | 0.0 | 1322 ms | 0 |
| Tue 00 | 0 | 0.0 | 1169 ms | 0 |
| Tue 02 | 0 | 0.0 | 4109 ms | 0 |
| Tue 04 | 0 | 0.0 | 1383 ms | 0 |
| Tue 07 | 0 | 0.0 | 1306 ms | 0 |
| Tue 09 | 0 | 0.0 | 1149 ms | 0 |
| Tue 11 | 0 | 0.0 | 1428 ms | 0 |
| Tue 13 | 0 | 0.0 | 1239 ms | 0 |
| Tue 15 | 0 | 0.0 | 1330 ms | 0 |
| Tue 17 | 0 | 0.0 | 1314 ms | 0 |
| Tue 20 | 0 | 0.0 | 1388 ms | 0 |
| Tue 22 | 0 | 0.0 | 1337 ms | 0 |
| Wed 00 | 0 | 0.0 | 1247 ms | 0 |
| Wed 02 | 0 | 0.0 | 1408 ms | 0 |
| Wed 05 | 0 | 0.0 | 1284 ms | 0 |
| Wed 07 | 0 | 0.0 | 1304 ms | 0 |
| Wed 09 | 0 | 0.0 | 1476 ms | 0 |
| Wed 11 | 0 | 0.0 | 1525 ms | 0 |
| Wed 14 | 0 | 0.0 | 1292 ms | 0 |
| Wed 16 | 0 | 0.0 | 1610 ms | 0 |
| Wed 18 | 0 | 0.0 | 1504 ms | 0 |
| Wed 20 | 0 | 0.0 | 1354 ms | 0 |
| Wed 22 | 0 | 0.0 | 1335 ms | 0 |
| Thu 00 | 0 | 0.0 | 1313 ms | 0 |
| Thu 02 | 0 | 0.0 | 1264 ms | 0 |
| Thu 04 | 0 | 0.0 | 1277 ms | 0 |
| Thu 07 | 0 | 0.0 | 1256 ms | 0 |
| Thu 09 | 0 | 0.0 | 1357 ms | 0 |
| Thu 11 | 0 | 0.0 | 1335 ms | 0 |
| Thu 13 | 0 | 0.0 | 1392 ms | 0 |
| Thu 15 | 0 | 0.0 | 1292 ms | 0 |
| Thu 17 | 0 | 0.0 | 1355 ms | 0 |
| Thu 19 | 0 | 0.0 | 1340 ms | 0 |
| Thu 21 | 0 | 0.0 | 1593 ms | 0 |
| Thu 23 | 0 | 0.0 | 1261 ms | 0 |
| Fri 01 | 0 | 0.0 | 1264 ms | 0 |
| Fri 03 | 0 | 0.0 | 1560 ms | 0 |
| Fri 05 | 0 | 0.0 | 1276 ms | 0 |
| Fri 07 | 0 | 0.0 | 1349 ms | 0 |
| Fri 09 | 0 | 0.0 | 1422 ms | 0 |
| Fri 11 | 0 | 0.0 | 1229 ms | 0 |
| Fri 12 | 0 | 0.0 | 1391 ms | 0 |
| Fri 14 | 0 | 0.0 | 1384 ms | 0 |
| Fri 16 | 0 | 0.0 | 1442 ms | 0 |
| Fri 17 | 0 | 0.0 | 1483 ms | 0 |
| Fri 18 | 0 | 0.0 | 1511 ms | 0 |
| Fri 19 | 0 | 0.0 | 1385 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 BIMcollab 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 BIMcollab goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send BIMcollab alerts to Slack, Discord or a webhook — free.
BIMcollab, at bimcollab.com, is one of the AI services we monitor. BIMcollab offers platforms for BIM coordination, model checking, issue management, takeoffs, document management, and asset management.
BIMcollab publishes an official status page at status.bimcollab.com; when we can read it, its incident level is folded into the status shown here.
Common problems for 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: 1396 ms average, 1229–1593 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 BIMcollab incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
1396 ms on average over the last 24 hours (1229–1593 ms).
Yes, at https://status.bimcollab.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 BIMcollab here at once, the problem is on BIMcollab'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 BIMcollab. 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.