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 3 min ago. Last stored result reached it in 542 ms.
All clear
All systems operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Nov 6 | 0 | 0.0 | 507 ms | 0 |
| Nov 7 | 0 | 0.0 | 522 ms | 0 |
| Nov 7 | 0 | 0.0 | 507 ms | 0 |
| Nov 7 | 0 | 0.0 | 525 ms | 0 |
| Nov 7 | 0 | 0.0 | 531 ms | 0 |
| Nov 8 | 0 | 0.0 | 532 ms | 0 |
| Nov 8 | 0 | 0.0 | 544 ms | 0 |
| Nov 8 | 0 | 0.0 | 543 ms | 0 |
| Nov 8 | 0 | 0.0 | 515 ms | 0 |
| Nov 9 | 0 | 0.0 | 527 ms | 0 |
| Nov 9 | 0 | 0.0 | 518 ms | 0 |
| Nov 9 | 0 | 0.0 | 556 ms | 0 |
| Nov 9 | 0 | 0.0 | 571 ms | 0 |
| Nov 10 | 0 | 0.0 | 422 ms | 0 |
| Nov 10 | 0 | 0.0 | 589 ms | 0 |
| Nov 10 | 0 | 0.0 | 503 ms | 0 |
| Nov 10 | 0 | 0.0 | 629 ms | 0 |
| Nov 11 | 0 | 0.0 | 534 ms | 0 |
| Nov 11 | 0 | 0.0 | 529 ms | 0 |
| Nov 11 | 0 | 0.0 | 576 ms | 0 |
| Nov 11 | 0 | 0.0 | 582 ms | 0 |
| Nov 12 | 0 | 0.0 | 567 ms | 0 |
| Nov 12 | 0 | 0.0 | 563 ms | 0 |
| Nov 12 | 0 | 0.0 | 475 ms | 0 |
| Nov 12 | 0 | 0.0 | 498 ms | 0 |
| Nov 13 | 0 | 0.0 | 541 ms | 0 |
| Nov 13 | 0 | 0.0 | 563 ms | 0 |
| Nov 13 | 0 | 0.0 | 527 ms | 0 |
| Nov 13 | 0 | 0.0 | 507 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: 529 ms average, 408–599 ms range across 18 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.
529 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.