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 206 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Nov 7 | 0 | 0.0 | 187 ms | 0 |
| Nov 7 | 0 | 0.0 | 588 ms | 0 |
| Nov 8 | 0 | 0.0 | 203 ms | 0 |
| Nov 8 | 0 | 0.0 | 556 ms | 0 |
| Nov 8 | 0 | 0.0 | 379 ms | 0 |
| Nov 8 | 0 | 0.0 | 517 ms | 0 |
| Nov 9 | 0 | 0.0 | 232 ms | 0 |
| Nov 9 | 0 | 0.0 | 372 ms | 0 |
| Nov 9 | 0 | 0.0 | 548 ms | 0 |
| Nov 9 | 0 | 0.0 | 438 ms | 0 |
| Nov 10 | 0 | 0.0 | 521 ms | 0 |
| Nov 10 | 0 | 0.0 | 543 ms | 0 |
| Nov 10 | 0 | 0.0 | 582 ms | 0 |
| Nov 10 | 0 | 0.0 | 233 ms | 0 |
| Nov 11 | 0 | 0.0 | 565 ms | 0 |
| Nov 11 | 0 | 0.0 | 395 ms | 0 |
| Nov 11 | 0 | 0.0 | 532 ms | 0 |
| Nov 11 | 0 | 0.0 | 483 ms | 0 |
| Nov 12 | 0 | 0.0 | 402 ms | 0 |
| Nov 12 | 0 | 0.0 | 545 ms | 0 |
| Nov 12 | 0 | 0.0 | 496 ms | 0 |
| Nov 12 | 0 | 0.0 | 541 ms | 0 |
| Nov 13 | 0 | 0.0 | 526 ms | 0 |
| Nov 13 | 0 | 0.0 | 196 ms | 0 |
| Nov 13 | 0 | 0.0 | 559 ms | 0 |
| Nov 13 | 0 | 0.0 | 206 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 Stablecog 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 Stablecog goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Stablecog alerts to Slack, Discord or a webhook — free.
Stablecog, at stablecog.com, is one of the AI services we monitor. Create amazing art in seconds with AI. Free, multilingual and open-source AI image generator using Stable Diffusion, FLUX, and Kandinsky.
Stablecog publishes an official status page at status.stablecog.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 7 days of checks. No public incidents logged since monitoring began 7 days ago.
Response time over the last 24 hours: 431 ms average, 152–603 ms range across 14 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Stablecog incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
431 ms on average over the last 24 hours (152–603 ms).
Yes, at https://status.stablecog.com.
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 Stablecog here at once, the problem is on Stablecog'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 Stablecog. 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.