User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Productivity
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 193 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 01 | 0 | 0.0 | 81 ms | 0 |
| Mon 03 | 0 | 0.0 | 86 ms | 0 |
| Mon 05 | 0 | 0.0 | 117 ms | 0 |
| Mon 08 | 0 | 0.0 | 105 ms | 0 |
| Mon 10 | 0 | 0.0 | 71 ms | 0 |
| Mon 12 | 0 | 0.0 | 84 ms | 0 |
| Mon 14 | 0 | 0.0 | 115 ms | 0 |
| Mon 16 | 0 | 0.0 | 104 ms | 0 |
| Mon 18 | 0 | 0.0 | 83 ms | 0 |
| Mon 20 | 0 | 0.0 | 94 ms | 0 |
| Mon 22 | 0 | 0.0 | 110 ms | 0 |
| Tue 00 | 0 | 0.0 | 182 ms | 0 |
| Tue 02 | 0 | 0.0 | 224 ms | 0 |
| Tue 05 | 0 | 0.0 | 278 ms | 0 |
| Tue 07 | 0 | 0.0 | 92 ms | 0 |
| Tue 09 | 0 | 0.0 | 103 ms | 0 |
| Tue 11 | 0 | 0.0 | 97 ms | 0 |
| Tue 13 | 0 | 0.0 | 87 ms | 0 |
| Tue 15 | 0 | 0.0 | 119 ms | 0 |
| Tue 18 | 0 | 0.0 | 361 ms | 0 |
| Tue 20 | 0 | 0.0 | 101 ms | 0 |
| Tue 22 | 0 | 0.0 | 140 ms | 0 |
| Wed 00 | 0 | 0.0 | 77 ms | 0 |
| Wed 03 | 0 | 0.0 | 101 ms | 0 |
| Wed 05 | 0 | 0.0 | 204 ms | 0 |
| Wed 07 | 0 | 0.0 | 78 ms | 0 |
| Wed 09 | 0 | 0.0 | 69 ms | 0 |
| Wed 12 | 0 | 0.0 | 176 ms | 0 |
| Wed 14 | 0 | 0.0 | 70 ms | 0 |
| Wed 16 | 0 | 0.0 | 189 ms | 0 |
| Wed 18 | 0 | 0.0 | 165 ms | 0 |
| Wed 20 | 0 | 0.0 | 258 ms | 0 |
| Wed 22 | 0 | 0.0 | 163 ms | 0 |
| Thu 00 | 0 | 0.0 | 116 ms | 0 |
| Thu 03 | 0 | 0.0 | 106 ms | 0 |
| Thu 05 | 0 | 0.0 | 194 ms | 0 |
| Thu 07 | 0 | 0.0 | 129 ms | 0 |
| Thu 09 | 0 | 0.0 | 96 ms | 0 |
| Thu 11 | 0 | 0.0 | 66 ms | 0 |
| Thu 13 | 0 | 0.0 | 210 ms | 0 |
| Thu 15 | 0 | 0.0 | 167 ms | 0 |
| Thu 17 | 0 | 0.0 | 199 ms | 0 |
| Thu 19 | 0 | 0.0 | 88 ms | 0 |
| Thu 21 | 0 | 0.0 | 78 ms | 0 |
| Thu 23 | 0 | 0.0 | 101 ms | 0 |
| Fri 01 | 0 | 0.0 | 112 ms | 0 |
| Fri 03 | 0 | 0.0 | 249 ms | 0 |
| Fri 05 | 0 | 0.0 | 193 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 7 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Fluidstack 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 Fluidstack goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Fluidstack alerts to Slack, Discord or a webhook — free.
Fluidstack is listed in our Productivity category and checked at fluidstack.io. We build compute faster than anyone on the planet. Gigawatt data centers, built in America, delivered in months. We're hiring the people who build them.
Fluidstack publishes an official status page at status.fluidstack.io; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with productivity services: files not syncing, editors not loading, and sign-in problems.
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: 138 ms average, 66–249 ms range across 12 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Fluidstack incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
138 ms on average over the last 24 hours (66–249 ms).
Yes, at https://status.fluidstack.io.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For productivity services, watch for files not syncing, editors not loading, and sign-in problems. If many people report Fluidstack here at once, the problem is on Fluidstack'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 Fluidstack. 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.