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 1 hr ago. Last stored result reached it in 374 ms.
All clear
All systems operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 19 | 0 | 0.0 | 103 ms | 0 |
| Mon 21 | 0 | 0.0 | 369 ms | 0 |
| Mon 23 | 0 | 0.0 | 155 ms | 0 |
| Tue 01 | 0 | 0.0 | 369 ms | 0 |
| Tue 03 | 0 | 0.0 | 375 ms | 0 |
| Tue 05 | 0 | 0.0 | 292 ms | 0 |
| Tue 08 | 0 | 0.0 | 440 ms | 0 |
| Tue 10 | 0 | 0.0 | 246 ms | 0 |
| Tue 12 | 0 | 0.0 | 230 ms | 0 |
| Tue 14 | 0 | 0.0 | 315 ms | 0 |
| Tue 16 | 0 | 0.0 | 518 ms | 0 |
| Tue 18 | 0 | 0.0 | 716 ms | 0 |
| Tue 21 | 0 | 0.0 | 793 ms | 0 |
| Tue 23 | 0 | 0.0 | 506 ms | 0 |
| Wed 01 | 0 | 0.0 | 588 ms | 0 |
| Wed 03 | 0 | 0.0 | 284 ms | 0 |
| Wed 06 | 0 | 0.0 | 345 ms | 0 |
| Wed 08 | 0 | 0.0 | 246 ms | 0 |
| Wed 10 | 0 | 0.0 | 324 ms | 0 |
| Wed 12 | 0 | 0.0 | 363 ms | 0 |
| Wed 14 | 0 | 0.0 | 245 ms | 0 |
| Wed 16 | 0 | 0.0 | 448 ms | 0 |
| Wed 19 | 0 | 0.0 | 331 ms | 0 |
| Wed 21 | 0 | 0.0 | 373 ms | 0 |
| Wed 23 | 0 | 0.0 | 540 ms | 0 |
| Thu 01 | 0 | 0.0 | 431 ms | 0 |
| Thu 03 | 0 | 0.0 | 178 ms | 0 |
| Thu 05 | 0 | 0.0 | 1987 ms | 0 |
| Thu 07 | 0 | 0.0 | 996 ms | 0 |
| Thu 09 | 0 | 0.0 | 1726 ms | 0 |
| Thu 11 | 0 | 0.0 | 1483 ms | 0 |
| Thu 13 | 0 | 0.0 | 321 ms | 0 |
| Thu 15 | 0 | 0.0 | 1369 ms | 0 |
| Thu 17 | 0 | 0.0 | 360 ms | 0 |
| Thu 19 | 0 | 0.0 | 305 ms | 0 |
| Thu 21 | 0 | 0.0 | 354 ms | 0 |
| Thu 23 | 0 | 0.0 | 267 ms | 0 |
| Fri 01 | 0 | 0.0 | 513 ms | 0 |
| Fri 03 | 0 | 0.0 | 1476 ms | 0 |
| Fri 05 | 0 | 0.0 | 379 ms | 0 |
| Fri 07 | 0 | 0.0 | 236 ms | 0 |
| Fri 09 | 0 | 0.0 | 77 ms | 0 |
| Fri 10 | 0 | 0.0 | 299 ms | 0 |
| Fri 12 | 0 | 0.0 | 362 ms | 0 |
| Fri 14 | 0 | 0.0 | 1556 ms | 0 |
| Fri 16 | 0 | 0.0 | 329 ms | 0 |
| Fri 18 | 0 | 0.0 | 2417 ms | 0 |
| Fri 20 | 0 | 0.0 | 374 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 Flux 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 Flux goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Flux alerts to Slack, Discord or a webhook — free.
Flux is listed in our AI category and checked at flux.ai. Flux is an AI hardware engineer. Design your device, route your PCB, and refine traces through chat. Build in your browser.
Flux publishes an official status page at status.flux.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. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 665 ms average, 77–2417 ms range across 13 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Flux incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
665 ms on average over the last 24 hours (77–2417 ms).
Yes, at https://status.flux.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 Flux here at once, the problem is on Flux'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 Flux. 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.