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 39 min ago. Last stored result reached it in 321 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 05 | 0 | 0.0 | 404 ms | 0 |
| Mon 07 | 0 | 0.0 | 158 ms | 0 |
| Mon 09 | 0 | 0.0 | 799 ms | 0 |
| Mon 11 | 0 | 0.0 | 441 ms | 0 |
| Mon 13 | 0 | 0.0 | 324 ms | 0 |
| Mon 15 | 0 | 0.0 | 181 ms | 0 |
| Mon 17 | 0 | 0.0 | 469 ms | 0 |
| Mon 20 | 0 | 0.0 | 364 ms | 0 |
| Mon 22 | 0 | 0.0 | 250 ms | 0 |
| Tue 00 | 0 | 0.0 | 232 ms | 0 |
| Tue 02 | 0 | 0.0 | 196 ms | 0 |
| Tue 04 | 0 | 0.0 | 393 ms | 0 |
| Tue 06 | 0 | 0.0 | 265 ms | 0 |
| Tue 08 | 0 | 0.0 | 148 ms | 0 |
| Tue 10 | 0 | 0.0 | 411 ms | 0 |
| Tue 12 | 0 | 0.0 | 187 ms | 0 |
| Tue 15 | 0 | 0.0 | 242 ms | 0 |
| Tue 17 | 0 | 0.0 | 984 ms | 0 |
| Tue 19 | 0 | 0.0 | 239 ms | 0 |
| Tue 21 | 0 | 0.0 | 221 ms | 0 |
| Wed 00 | 0 | 0.0 | 233 ms | 0 |
| Wed 02 | 0 | 0.0 | 252 ms | 0 |
| Wed 04 | 0 | 0.0 | 226 ms | 0 |
| Wed 06 | 0 | 0.0 | 197 ms | 0 |
| Wed 09 | 0 | 0.0 | 149 ms | 0 |
| Wed 11 | 0 | 0.0 | 156 ms | 0 |
| Wed 13 | 0 | 0.0 | 162 ms | 0 |
| Wed 15 | 0 | 0.0 | 458 ms | 0 |
| Wed 17 | 0 | 0.0 | 144 ms | 0 |
| Wed 19 | 0 | 0.0 | 166 ms | 0 |
| Wed 22 | 0 | 0.0 | 173 ms | 0 |
| Thu 00 | 0 | 0.0 | 295 ms | 0 |
| Thu 02 | 0 | 0.0 | 219 ms | 0 |
| Thu 04 | 0 | 0.0 | 229 ms | 0 |
| Thu 06 | 0 | 0.0 | 225 ms | 0 |
| Thu 07 | 0 | 0.0 | 213 ms | 0 |
| Thu 09 | 0 | 0.0 | 333 ms | 0 |
| Thu 11 | 0 | 0.0 | 165 ms | 0 |
| Thu 13 | 0 | 0.0 | 333 ms | 0 |
| Thu 15 | 0 | 0.0 | 214 ms | 0 |
| Thu 17 | 0 | 0.0 | 175 ms | 0 |
| Thu 19 | 0 | 0.0 | 368 ms | 0 |
| Thu 21 | 0 | 0.0 | 353 ms | 0 |
| Thu 23 | 0 | 0.0 | 398 ms | 0 |
| Fri 02 | 0 | 0.0 | 416 ms | 0 |
| Fri 04 | 0 | 0.0 | 355 ms | 0 |
| Fri 05 | 0 | 0.0 | 371 ms | 0 |
| Fri 07 | 0 | 0.0 | 321 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 Findstack 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 Findstack goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Findstack alerts to Slack, Discord or a webhook — free.
We track Findstack (findstack.com) as part of the AI group. Compare the best business software, check reviews, and find the latest deals for AI, CRM, ERP, HR, sales, and marketing software.
Findstack publishes an official status page at status.findstack.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: 317 ms average, 165–416 ms range across 12 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Findstack incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
317 ms on average over the last 24 hours (165–416 ms).
Yes, at https://status.findstack.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 Findstack here at once, the problem is on Findstack'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 Findstack. 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.