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 44 min ago. Last stored result reached it in 382 ms.
All clear
All systems operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Nov 6 | 0 | 0.0 | 370 ms | 0 |
| Nov 7 | 0 | 0.0 | 254 ms | 0 |
| Nov 7 | 0 | 0.0 | 259 ms | 0 |
| Nov 7 | 0 | 0.0 | 135 ms | 0 |
| Nov 7 | 0 | 0.0 | 165 ms | 0 |
| Nov 8 | 0 | 0.0 | 206 ms | 0 |
| Nov 8 | 0 | 0.0 | 217 ms | 0 |
| Nov 8 | 0 | 0.0 | 165 ms | 0 |
| Nov 8 | 0 | 0.0 | 254 ms | 0 |
| Nov 9 | 0 | 0.0 | 275 ms | 0 |
| Nov 9 | 0 | 0.0 | 243 ms | 0 |
| Nov 9 | 0 | 0.0 | 260 ms | 0 |
| Nov 9 | 0 | 0.0 | 134 ms | 0 |
| Nov 10 | 0 | 0.0 | 227 ms | 0 |
| Nov 10 | 0 | 0.0 | 202 ms | 0 |
| Nov 10 | 0 | 0.0 | 226 ms | 0 |
| Nov 10 | 0 | 0.0 | 235 ms | 0 |
| Nov 11 | 0 | 0.0 | 258 ms | 0 |
| Nov 11 | 0 | 0.0 | 264 ms | 0 |
| Nov 11 | 0 | 0.0 | 350 ms | 0 |
| Nov 11 | 0 | 0.0 | 399 ms | 0 |
| Nov 12 | 0 | 0.0 | 251 ms | 0 |
| Nov 12 | 0 | 0.0 | 205 ms | 0 |
| Nov 12 | 0 | 0.0 | 290 ms | 0 |
| Nov 12 | 0 | 0.0 | 408 ms | 0 |
| Nov 13 | 0 | 0.0 | 347 ms | 0 |
| Nov 13 | 0 | 0.0 | 204 ms | 0 |
| Nov 13 | 0 | 0.0 | 218 ms | 0 |
| Nov 13 | 0 | 0.0 | 312 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.
One report per service every 10 minutes from this network. No account.
Get an email when fonio goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send fonio alerts to Slack, Discord or a webhook — free.
We track fonio (fonio.ai) as part of the AI group. Never miss a customer call. fonio’s AI phone assistant answers calls 24/7, books appointments and handles common questions, giving your team time back.
fonio publishes an official status page at status.fonio.ai; 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. We logged 2 public incidents since monitoring began 8 days ago.
Response time over the last 24 hours: 300 ms average, 109–849 ms range across 16 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
The most recent public incident we recorded started 2026-11-09 and lasted 16 h 52 min. 2 incidents since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
300 ms on average over the last 24 hours (109–849 ms).
Yes, at https://status.fonio.ai.
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 fonio here at once, the problem is on fonio'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 fonio. 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.