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 34 min ago. Last stored result reached it in 576 ms.
All clear
All systems operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 22 | 0 | 0.0 | 560 ms | 0 |
| Tue 00 | 0 | 0.0 | 602 ms | 0 |
| Tue 02 | 0 | 0.0 | 394 ms | 0 |
| Tue 04 | 0 | 0.0 | 422 ms | 0 |
| Tue 06 | 0 | 0.0 | 589 ms | 0 |
| Tue 08 | 0 | 0.0 | 555 ms | 0 |
| Tue 11 | 0 | 0.0 | 633 ms | 0 |
| Tue 13 | 0 | 0.0 | 513 ms | 0 |
| Tue 15 | 0 | 0.0 | 436 ms | 0 |
| Tue 17 | 0 | 0.0 | 503 ms | 0 |
| Tue 20 | 0 | 0.0 | 636 ms | 0 |
| Tue 22 | 0 | 0.0 | 622 ms | 0 |
| Wed 00 | 0 | 0.0 | 534 ms | 0 |
| Wed 02 | 0 | 0.0 | 558 ms | 0 |
| Wed 05 | 0 | 0.0 | 490 ms | 0 |
| Wed 07 | 0 | 0.0 | 529 ms | 0 |
| Wed 09 | 0 | 0.0 | 574 ms | 0 |
| Wed 11 | 0 | 0.0 | 522 ms | 0 |
| Wed 13 | 0 | 0.0 | 586 ms | 0 |
| Wed 15 | 0 | 0.0 | 565 ms | 0 |
| Wed 18 | 0 | 0.0 | 582 ms | 0 |
| Wed 20 | 0 | 0.0 | 464 ms | 0 |
| Wed 22 | 0 | 0.0 | 585 ms | 0 |
| Thu 00 | 0 | 0.0 | 536 ms | 0 |
| Thu 02 | 0 | 0.0 | 598 ms | 0 |
| Thu 04 | 0 | 0.0 | 567 ms | 0 |
| Thu 06 | 0 | 0.0 | 620 ms | 0 |
| Thu 07 | 0 | 0.0 | 462 ms | 0 |
| Thu 09 | 0 | 0.0 | 594 ms | 0 |
| Thu 11 | 0 | 0.0 | 532 ms | 0 |
| Thu 13 | 0 | 0.0 | 417 ms | 0 |
| Thu 15 | 0 | 0.0 | 475 ms | 0 |
| Thu 17 | 0 | 0.0 | 621 ms | 0 |
| Thu 19 | 0 | 0.0 | 477 ms | 0 |
| Thu 21 | 0 | 0.0 | 581 ms | 0 |
| Thu 23 | 0 | 0.0 | 498 ms | 0 |
| Fri 01 | 0 | 0.0 | 488 ms | 0 |
| Fri 02 | 0 | 0.0 | 549 ms | 0 |
| Fri 04 | 0 | 0.0 | 541 ms | 0 |
| Fri 06 | 0 | 0.0 | 527 ms | 0 |
| Fri 08 | 0 | 0.0 | 506 ms | 0 |
| Fri 10 | 0 | 0.0 | 599 ms | 0 |
| Fri 11 | 0 | 0.0 | 599 ms | 0 |
| Fri 13 | 0 | 0.0 | 451 ms | 0 |
| Fri 15 | 0 | 0.0 | 574 ms | 0 |
| Fri 17 | 0 | 0.0 | 559 ms | 0 |
| Fri 18 | 0 | 0.0 | 507 ms | 0 |
| Fri 19 | 0 | 0.0 | 535 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 Onflo 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 Onflo goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Onflo alerts to Slack, Discord or a webhook — free.
We track Onflo (onflo.com) as part of the AI group. Onflo is the AI-powered platform for K-12 schools: one system for help desk, assets, facilities, HR, telephony and an AI chatbot.
Onflo publishes an official status page at status.onflo.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 8 days of checks. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 531 ms average, 408–599 ms range across 16 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Onflo incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
531 ms on average over the last 24 hours (408–599 ms).
Yes, at https://status.onflo.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 Onflo here at once, the problem is on Onflo'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 Onflo. 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.