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 19 min ago. Last stored result reached it in 147 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 | 293 ms | 0 |
| Mon 18 | 0 | 0.0 | 234 ms | 0 |
| Mon 20 | 0 | 0.0 | 268 ms | 0 |
| Mon 22 | 0 | 0.0 | 308 ms | 0 |
| Tue 00 | 0 | 0.0 | 209 ms | 0 |
| Tue 03 | 0 | 0.0 | 201 ms | 0 |
| Tue 05 | 0 | 0.0 | 258 ms | 0 |
| Tue 07 | 0 | 0.0 | 229 ms | 0 |
| Tue 09 | 0 | 0.0 | 155 ms | 0 |
| Tue 11 | 0 | 0.0 | 190 ms | 0 |
| Tue 13 | 0 | 0.0 | 292 ms | 0 |
| Tue 15 | 0 | 0.0 | 241 ms | 0 |
| Tue 18 | 0 | 0.0 | 203 ms | 0 |
| Tue 20 | 0 | 0.0 | 249 ms | 0 |
| Tue 22 | 0 | 0.0 | 107 ms | 0 |
| Wed 00 | 0 | 0.0 | 255 ms | 0 |
| Wed 03 | 0 | 0.0 | 207 ms | 0 |
| Wed 05 | 0 | 0.0 | 227 ms | 0 |
| Wed 07 | 0 | 0.0 | 161 ms | 0 |
| Wed 09 | 0 | 0.0 | 234 ms | 0 |
| Wed 12 | 0 | 0.0 | 164 ms | 0 |
| Wed 14 | 0 | 0.0 | 177 ms | 0 |
| Wed 16 | 0 | 0.0 | 280 ms | 0 |
| Wed 18 | 0 | 0.0 | 221 ms | 0 |
| Wed 20 | 0 | 0.0 | 633 ms | 0 |
| Wed 22 | 0 | 0.0 | 942 ms | 0 |
| Thu 00 | 0 | 0.0 | 1267 ms | 0 |
| Thu 02 | 0 | 0.0 | 96 ms | 0 |
| Thu 04 | 0 | 0.0 | 1037 ms | 0 |
| Thu 06 | 0 | 0.0 | 644 ms | 0 |
| Thu 08 | 0 | 0.0 | 176 ms | 0 |
| Thu 10 | 0 | 0.0 | 567 ms | 0 |
| Thu 12 | 0 | 0.0 | 520 ms | 0 |
| Thu 15 | 0 | 0.0 | 632 ms | 0 |
| Thu 17 | 0 | 0.0 | 680 ms | 0 |
| Thu 19 | 0 | 0.0 | 499 ms | 0 |
| Thu 21 | 0 | 0.0 | 146 ms | 0 |
| Thu 22 | 0 | 0.0 | 340 ms | 0 |
| Fri 00 | 0 | 0.0 | 285 ms | 0 |
| Fri 02 | 0 | 0.0 | 208 ms | 0 |
| Fri 04 | 0 | 0.0 | 384 ms | 0 |
| Fri 07 | 0 | 0.0 | 272 ms | 0 |
| Fri 09 | 0 | 0.0 | 383 ms | 0 |
| Fri 11 | 0 | 0.0 | 261 ms | 0 |
| Fri 12 | 0 | 0.0 | 181 ms | 0 |
| Fri 14 | 0 | 0.0 | 234 ms | 0 |
| Fri 16 | 0 | 0.0 | 147 ms | 0 |
| Fri 17 | 0 | 0.0 | 182 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 6 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Adaptive 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 Adaptive goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Adaptive alerts to Slack, Discord or a webhook — free.
We track Adaptive (adaptive.build) as part of the AI group. AI agents handle job costing, AP, billing, and WIP for construction companies. Works with QuickBooks, Foundation, and Sage. No ERP migration needed.
Adaptive publishes an official status page at status.adaptive.build; 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 6 days of checks. No public incidents logged since monitoring began 6 days ago.
Response time over the last 24 hours: 271 ms average, 146–499 ms range across 13 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Adaptive incident since monitoring began 6 days ago.
From our own checks: 100% over 6 days of checks.
271 ms on average over the last 24 hours (146–499 ms).
Yes, at https://status.adaptive.build.
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 Adaptive here at once, the problem is on Adaptive'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 Adaptive. 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.