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 186 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 18 | 0 | 0.0 | 277 ms | 0 |
| Mon 20 | 0 | 0.0 | 438 ms | 0 |
| Mon 22 | 0 | 0.0 | 667 ms | 0 |
| Tue 00 | 0 | 0.0 | 572 ms | 0 |
| Tue 02 | 0 | 0.0 | 283 ms | 0 |
| Tue 04 | 0 | 0.0 | 521 ms | 0 |
| Tue 07 | 0 | 0.0 | 222 ms | 0 |
| Tue 09 | 0 | 0.0 | 543 ms | 0 |
| Tue 11 | 0 | 0.0 | 555 ms | 0 |
| Tue 13 | 0 | 0.0 | 582 ms | 0 |
| Tue 15 | 0 | 0.0 | 514 ms | 0 |
| Tue 18 | 0 | 0.0 | 217 ms | 0 |
| Tue 20 | 0 | 0.0 | 604 ms | 0 |
| Tue 22 | 0 | 0.0 | 206 ms | 0 |
| Wed 00 | 0 | 0.0 | 565 ms | 0 |
| Wed 03 | 0 | 0.0 | 196 ms | 0 |
| Wed 05 | 0 | 0.0 | 622 ms | 0 |
| Wed 07 | 0 | 0.0 | 629 ms | 0 |
| Wed 09 | 0 | 0.0 | 160 ms | 0 |
| Wed 12 | 0 | 0.0 | 553 ms | 0 |
| Wed 14 | 0 | 0.0 | 532 ms | 0 |
| Wed 16 | 0 | 0.0 | 182 ms | 0 |
| Wed 18 | 0 | 0.0 | 244 ms | 0 |
| Wed 20 | 0 | 0.0 | 483 ms | 0 |
| Wed 22 | 0 | 0.0 | 566 ms | 0 |
| Thu 01 | 0 | 0.0 | 583 ms | 0 |
| Thu 03 | 0 | 0.0 | 221 ms | 0 |
| Thu 05 | 0 | 0.0 | 411 ms | 0 |
| Thu 07 | 0 | 0.0 | 160 ms | 0 |
| Thu 09 | 0 | 0.0 | 545 ms | 0 |
| Thu 11 | 0 | 0.0 | 551 ms | 0 |
| Thu 13 | 0 | 0.0 | 177 ms | 0 |
| Thu 15 | 0 | 0.0 | 496 ms | 0 |
| Thu 17 | 0 | 0.0 | 530 ms | 0 |
| Thu 19 | 0 | 0.0 | 167 ms | 0 |
| Thu 21 | 0 | 0.0 | 580 ms | 0 |
| Thu 23 | 0 | 0.0 | 551 ms | 0 |
| Fri 01 | 0 | 0.0 | 603 ms | 0 |
| Fri 03 | 0 | 0.0 | 526 ms | 0 |
| Fri 05 | 0 | 0.0 | 463 ms | 0 |
| Fri 08 | 0 | 0.0 | 196 ms | 0 |
| Fri 10 | 0 | 0.0 | 299 ms | 0 |
| Fri 12 | 0 | 0.0 | 586 ms | 0 |
| Fri 14 | 0 | 0.0 | 460 ms | 0 |
| Fri 16 | 0 | 0.0 | 552 ms | 0 |
| Fri 17 | 0 | 0.0 | 565 ms | 0 |
| Fri 18 | 0 | 0.0 | 537 ms | 0 |
| Fri 19 | 0 | 0.0 | 186 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: 465 ms average, 152–629 ms range across 15 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.
465 ms on average over the last 24 hours (152–629 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.