User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / AI
Is FloQast 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 → floqast.com—
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 35 min ago. Last stored result reached it in 97 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 |
|---|---|---|---|---|
| Tue 02 | 0 | 0.0 | 134 ms | 0 |
| Tue 04 | 0 | 0.0 | 80 ms | 0 |
| Tue 06 | 0 | 0.0 | 79 ms | 0 |
| Tue 08 | 0 | 0.0 | 73 ms | 0 |
| Tue 10 | 0 | 0.0 | 34 ms | 0 |
| Tue 12 | 0 | 0.0 | 63 ms | 0 |
| Tue 15 | 0 | 0.0 | 141 ms | 0 |
| Tue 17 | 0 | 0.0 | 69 ms | 0 |
| Tue 19 | 0 | 0.0 | 58 ms | 0 |
| Tue 21 | 0 | 0.0 | 84 ms | 0 |
| Wed 00 | 0 | 0.0 | 106 ms | 0 |
| Wed 02 | 0 | 0.0 | 49 ms | 0 |
| Wed 04 | 0 | 0.0 | 121 ms | 0 |
| Wed 06 | 0 | 0.0 | 60 ms | 0 |
| Wed 09 | 0 | 0.0 | 33 ms | 0 |
| Wed 11 | 0 | 0.0 | 72 ms | 0 |
| Wed 13 | 0 | 0.0 | 62 ms | 0 |
| Wed 15 | 0 | 0.0 | 83 ms | 0 |
| Wed 17 | 0 | 0.0 | 81 ms | 0 |
| Wed 19 | 0 | 0.0 | 80 ms | 0 |
| Wed 21 | 0 | 0.0 | 103 ms | 0 |
| Wed 23 | 0 | 0.0 | 87 ms | 0 |
| Thu 01 | 0 | 0.0 | 79 ms | 0 |
| Thu 03 | 0 | 0.0 | 94 ms | 0 |
| Thu 05 | 0 | 0.0 | 120 ms | 0 |
| Thu 07 | 0 | 0.0 | 103 ms | 0 |
| Thu 09 | 0 | 0.0 | 69 ms | 0 |
| Thu 11 | 0 | 0.0 | 60 ms | 0 |
| Thu 13 | 0 | 0.0 | 44 ms | 0 |
| Thu 15 | 0 | 0.0 | 45 ms | 0 |
| Thu 17 | 0 | 0.0 | 45 ms | 0 |
| Thu 19 | 0 | 0.0 | 158 ms | 0 |
| Thu 22 | 0 | 0.0 | 115 ms | 0 |
| Fri 00 | 0 | 0.0 | 82 ms | 0 |
| Fri 02 | 0 | 0.0 | 47 ms | 0 |
| Fri 04 | 0 | 0.0 | 70 ms | 0 |
| Fri 06 | 0 | 0.0 | 54 ms | 0 |
| Fri 08 | 0 | 0.0 | 54 ms | 0 |
| Fri 10 | 0 | 0.0 | 45 ms | 0 |
| Fri 12 | 0 | 0.0 | 106 ms | 0 |
| Fri 14 | 0 | 0.0 | 94 ms | 0 |
| Fri 16 | 0 | 0.0 | 79 ms | 0 |
| Fri 17 | 0 | 0.0 | 90 ms | 0 |
| Fri 18 | 0 | 0.0 | 70 ms | 0 |
| Fri 19 | 0 | 0.0 | 107 ms | 0 |
| Fri 20 | 0 | 0.0 | 149 ms | 0 |
| Fri 22 | 0 | 0.0 | 68 ms | 0 |
| Sat 00 | 0 | 0.0 | 97 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 8 days of data so far, so the 90-day numbers fill in over time.
Embed this status: free live FloQast 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 FloQast yet. Outages of 10 minutes or more get their own page here.
Having trouble with FloQast?
One report per service every 10 minutes from this network. No account.
Follow FloQast
Get an email when FloQast goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send FloQast alerts to Slack, Discord or a webhook — free.
About FloQast
FloQast is listed in our AI category and checked at floqast.com. AI agents that automate reconciliations, close workflows, and journal entries — fully auditable, human-approved every step. Trusted by 3,500+ teams worldwide.
FloQast publishes an official status page at status.floqast.com; when we can read it, its incident level is folded into the status shown here.
Typical issues 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: 78 ms average, 34–149 ms range across 16 successful checks.
Questions
Is FloQast down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
When was FloQast last down?
We have not recorded a public FloQast incident since monitoring began 8 days ago.
What is FloQast's uptime?
From our own checks: 100% over 8 days of checks.
How fast does FloQast respond?
78 ms on average over the last 24 hours (34–149 ms).
Does FloQast have an official status page?
Yes, at https://status.floqast.com.
FloQast 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 FloQast here at once, the problem is on FloQast'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 FloQast. 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.