User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / AI
Is Finout down?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Is it just me?
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Your browser → finout.io—
Your browser → us—
Our checksReaching it
Official · ReportsAll clear · Near baseline
DNS (1.1.1.1 · Google)—
Your provider—
Connection—
Upstream—
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.
Live outage map
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.
What's broken
Recent reports
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.
Our checks
Reaching it
Last checked 33 min ago. Last stored result reached it in 212 ms.
Official status
All clear
All Systems Operational Official status page
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 20 | 0 | 0.0 | 303 ms | 0 |
| Mon 22 | 0 | 0.0 | 327 ms | 0 |
| Tue 00 | 0 | 0.0 | 287 ms | 0 |
| Tue 03 | 0 | 0.0 | 327 ms | 0 |
| Tue 05 | 0 | 0.0 | 213 ms | 0 |
| Tue 07 | 0 | 0.0 | 284 ms | 0 |
| Tue 09 | 0 | 0.0 | 223 ms | 0 |
| Tue 11 | 0 | 0.0 | 283 ms | 0 |
| Tue 13 | 0 | 0.0 | 254 ms | 0 |
| Tue 15 | 0 | 0.0 | 313 ms | 0 |
| Tue 18 | 0 | 0.0 | 461 ms | 0 |
| Tue 20 | 0 | 0.0 | 383 ms | 0 |
| Tue 22 | 0 | 0.0 | 368 ms | 0 |
| Wed 00 | 0 | 0.0 | 293 ms | 0 |
| Wed 03 | 0 | 0.0 | 328 ms | 0 |
| Wed 05 | 0 | 0.0 | 287 ms | 0 |
| Wed 07 | 0 | 0.0 | 453 ms | 0 |
| Wed 09 | 0 | 0.0 | 252 ms | 0 |
| Wed 12 | 0 | 0.0 | 246 ms | 0 |
| Wed 14 | 0 | 0.0 | 291 ms | 0 |
| Wed 16 | 0 | 0.0 | 430 ms | 0 |
| Wed 18 | 0 | 0.0 | 317 ms | 0 |
| Wed 20 | 0 | 0.0 | 198 ms | 0 |
| Wed 22 | 0 | 0.0 | 296 ms | 0 |
| Thu 01 | 0 | 0.0 | 336 ms | 0 |
| Thu 03 | 0 | 0.0 | 280 ms | 0 |
| Thu 05 | 0 | 0.0 | 331 ms | 0 |
| Thu 07 | 0 | 0.0 | 244 ms | 0 |
| Thu 09 | 0 | 0.0 | 394 ms | 0 |
| Thu 11 | 0 | 0.0 | 300 ms | 0 |
| Thu 13 | 0 | 0.0 | 292 ms | 0 |
| Thu 15 | 0 | 0.0 | 301 ms | 0 |
| Thu 17 | 0 | 0.0 | 300 ms | 0 |
| Thu 19 | 0 | 0.0 | 608 ms | 0 |
| Thu 21 | 0 | 0.0 | 333 ms | 0 |
| Thu 23 | 0 | 0.0 | 234 ms | 0 |
| Fri 01 | 0 | 0.0 | 249 ms | 0 |
| Fri 03 | 0 | 0.0 | 360 ms | 0 |
| Fri 05 | 0 | 0.0 | 317 ms | 0 |
| Fri 08 | 0 | 0.0 | 238 ms | 0 |
| Fri 10 | 0 | 0.0 | 326 ms | 0 |
| Fri 12 | 0 | 0.0 | 270 ms | 0 |
| Fri 14 | 0 | 0.0 | 266 ms | 0 |
| Fri 16 | 0 | 0.0 | 212 ms | 0 |
| Fri 18 | 0 | 0.0 | 352 ms | 0 |
| Fri 19 | 0 | 0.0 | 364 ms | 0 |
| Fri 20 | 0 | 0.0 | 260 ms | 0 |
| Fri 22 | 0 | 0.0 | 212 ms | 0 |
Reliability
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.
Embed this status: free live Finout badge
Free, no iframe or script. Updates every minute and links back here. More options on the embed page · badge docs · JSON · MCP server
Past outages
No outages on record for Finout yet. Outages of 10 minutes or more get their own page here.
Having trouble with Finout?
One report per service every 10 minutes from this network. No account.
Follow Finout
Get an email when Finout goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Finout alerts to Slack, Discord or a webhook — free.
About Finout
We track Finout (finout.io) as part of the AI group. Finout unifies cloud, AI, and SaaS spend in one FinOps platform: prove ROI, optimize costs down to the token level, and eliminate waste automatically
Finout publishes an official status page at status.finout.io; 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 7 days of checks. No public incidents logged since monitoring began 7 days ago.
Response time over the last 24 hours: 281 ms average, 208–364 ms range across 14 successful checks.
Questions
Is Finout down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
When was Finout last down?
We have not recorded a public Finout incident since monitoring began 7 days ago.
What is Finout's uptime?
From our own checks: 100% over 7 days of checks.
How fast does Finout respond?
281 ms on average over the last 24 hours (208–364 ms).
Does Finout have an official status page?
Yes, at https://status.finout.io.
Finout not working for me but the status is fine. What now?
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 Finout here at once, the problem is on Finout'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 Finout. 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.