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 2 hr ago. Last stored result reached it in 218 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 21 | 0 | 0.0 | 250 ms | 0 |
| Mon 23 | 0 | 0.0 | 356 ms | 0 |
| Tue 01 | 0 | 0.0 | 294 ms | 0 |
| Tue 03 | 0 | 0.0 | 240 ms | 0 |
| Tue 05 | 0 | 0.0 | 320 ms | 0 |
| Tue 07 | 0 | 0.0 | 214 ms | 0 |
| Tue 09 | 0 | 0.0 | 299 ms | 0 |
| Tue 11 | 0 | 0.0 | 288 ms | 0 |
| Tue 14 | 0 | 0.0 | 265 ms | 0 |
| Tue 16 | 0 | 0.0 | 196 ms | 0 |
| Tue 18 | 0 | 0.0 | 378 ms | 0 |
| Tue 20 | 0 | 0.0 | 277 ms | 0 |
| Tue 23 | 0 | 0.0 | 201 ms | 0 |
| Wed 01 | 0 | 0.0 | 484 ms | 0 |
| Wed 03 | 0 | 0.0 | 305 ms | 0 |
| Wed 05 | 0 | 0.0 | 236 ms | 0 |
| Wed 07 | 0 | 0.0 | 298 ms | 0 |
| Wed 10 | 0 | 0.0 | 302 ms | 0 |
| Wed 12 | 0 | 0.0 | 315 ms | 0 |
| Wed 14 | 0 | 0.0 | 347 ms | 0 |
| Wed 16 | 0 | 0.0 | 223 ms | 0 |
| Wed 18 | 0 | 0.0 | 303 ms | 0 |
| Wed 20 | 0 | 0.0 | 243 ms | 0 |
| Wed 23 | 0 | 0.0 | 201 ms | 0 |
| Thu 01 | 0 | 0.0 | 288 ms | 0 |
| Thu 02 | 0 | 0.0 | 351 ms | 0 |
| Thu 04 | 0 | 0.0 | 230 ms | 0 |
| Thu 06 | 0 | 0.0 | 234 ms | 0 |
| Thu 08 | 0 | 0.0 | 206 ms | 0 |
| Thu 10 | 0 | 0.0 | 209 ms | 0 |
| Thu 12 | 0 | 0.0 | 203 ms | 0 |
| Thu 14 | 0 | 0.0 | 282 ms | 0 |
| Thu 16 | 0 | 0.0 | 185 ms | 0 |
| Thu 18 | 0 | 0.0 | 307 ms | 0 |
| Thu 20 | 0 | 0.0 | 200 ms | 0 |
| Thu 22 | 0 | 0.0 | 327 ms | 0 |
| Fri 00 | 0 | 0.0 | 360 ms | 0 |
| Fri 02 | 0 | 0.0 | 449 ms | 0 |
| Fri 04 | 0 | 0.0 | 435 ms | 0 |
| Fri 07 | 0 | 0.0 | 311 ms | 0 |
| Fri 09 | 0 | 0.0 | 153 ms | 0 |
| Fri 10 | 0 | 0.0 | 264 ms | 0 |
| Fri 12 | 0 | 0.0 | 275 ms | 0 |
| Fri 14 | 0 | 0.0 | 236 ms | 0 |
| Fri 16 | 0 | 0.0 | 249 ms | 0 |
| Fri 18 | 0 | 0.0 | 397 ms | 0 |
| Fri 20 | 0 | 0.0 | 234 ms | 0 |
| Fri 22 | 0 | 0.0 | 218 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 Chutes 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 Chutes goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Chutes alerts to Slack, Discord or a webhook — free.
Chutes is listed in our AI category and checked at chutes.ai. Chutes is a decentralized, serverless inference platform for open-source AI models. Call them via an OpenAI-compatible API, including TEE-protected models.
Chutes publishes an official status page at status.chutes.ai; 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 7 days of checks. No public incidents logged since monitoring began 7 days ago.
Response time over the last 24 hours: 296 ms average, 153–449 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 Chutes incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
296 ms on average over the last 24 hours (153–449 ms).
Yes, at https://status.chutes.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 Chutes here at once, the problem is on Chutes'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 Chutes. 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.