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 6 min ago. Last stored result reached it in 118 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 13 | 0 | 0.0 | 41 ms | 0 |
| Mon 15 | 0 | 0.0 | 289 ms | 0 |
| Mon 17 | 0 | 0.0 | 378 ms | 0 |
| Mon 19 | 0 | 0.0 | 351 ms | 0 |
| Mon 21 | 0 | 0.0 | 267 ms | 0 |
| Mon 23 | 0 | 0.0 | 105 ms | 0 |
| Tue 01 | 0 | 0.0 | 116 ms | 0 |
| Tue 04 | 0 | 0.0 | 464 ms | 0 |
| Tue 06 | 0 | 0.0 | 135 ms | 0 |
| Tue 08 | 0 | 0.0 | 265 ms | 0 |
| Tue 10 | 0 | 0.0 | 336 ms | 0 |
| Tue 12 | 0 | 0.0 | 407 ms | 0 |
| Tue 14 | 0 | 0.0 | 398 ms | 0 |
| Tue 16 | 0 | 0.0 | 354 ms | 0 |
| Tue 19 | 0 | 0.0 | 170 ms | 0 |
| Tue 21 | 0 | 0.0 | 372 ms | 0 |
| Tue 23 | 0 | 0.0 | 113 ms | 0 |
| Wed 01 | 0 | 0.0 | 446 ms | 0 |
| Wed 04 | 0 | 0.0 | 230 ms | 0 |
| Wed 06 | 0 | 0.0 | 328 ms | 0 |
| Wed 08 | 0 | 0.0 | 45 ms | 0 |
| Wed 10 | 0 | 0.0 | 414 ms | 0 |
| Wed 13 | 0 | 0.0 | 348 ms | 0 |
| Wed 15 | 0 | 0.0 | 373 ms | 0 |
| Wed 17 | 0 | 0.0 | 463 ms | 0 |
| Wed 19 | 0 | 0.0 | 147 ms | 0 |
| Wed 21 | 0 | 0.0 | 372 ms | 0 |
| Wed 23 | 0 | 0.0 | 713 ms | 0 |
| Thu 02 | 0 | 0.0 | 215 ms | 0 |
| Thu 04 | 0 | 0.0 | 134 ms | 0 |
| Thu 06 | 0 | 0.0 | 233 ms | 0 |
| Thu 08 | 0 | 0.0 | 46 ms | 0 |
| Thu 10 | 0 | 0.0 | 347 ms | 0 |
| Thu 12 | 0 | 0.0 | 424 ms | 0 |
| Thu 14 | 0 | 0.0 | 345 ms | 0 |
| Thu 16 | 0 | 0.0 | 404 ms | 0 |
| Thu 18 | 0 | 0.0 | 104 ms | 0 |
| Thu 20 | 0 | 0.0 | 333 ms | 0 |
| Thu 22 | 0 | 0.0 | 62 ms | 0 |
| Fri 00 | 0 | 0.0 | 138 ms | 0 |
| Fri 02 | 0 | 0.0 | 63 ms | 0 |
| Fri 04 | 0 | 0.0 | 220 ms | 0 |
| Fri 06 | 0 | 0.0 | 340 ms | 0 |
| Fri 08 | 0 | 0.0 | 310 ms | 0 |
| Fri 11 | 0 | 0.0 | 170 ms | 0 |
| Fri 13 | 0 | 0.0 | 81 ms | 0 |
| Fri 15 | 0 | 0.0 | 309 ms | 0 |
| Fri 17 | 0 | 0.0 | 118 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 Flowable IT 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 Flowable IT goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Flowable IT alerts to Slack, Discord or a webhook — free.
Flowable IT, at flowable.com, is one of the AI services we monitor. Reliable AI for high-stakes processes in regulated industries. Orchestrate AI agents, people and systems with built-in governance, traceability and open standards (BPMN, CMMN, DMN).
Flowable IT publishes an official status page at status.flowable.com; when we can read it, its incident level is folded into the status shown here.
Typical issues 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: 198 ms average, 17–369 ms range across 15 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Flowable IT incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
198 ms on average over the last 24 hours (17–369 ms).
Yes, at https://status.flowable.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 Flowable IT here at once, the problem is on Flowable IT'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 Flowable IT. 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.