Stability AI Outage History
2 incidents recorded over the last 365 days, 2 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded Stability AI Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Sep 14, 2026 | Investigating elevated 500s for generation endpoints🟢 This incident has been resolved. All systems are now operating normally. We apologize for any inconvenience this may have caused and thank you for your patience. | 4h 7m | Resolved |
| Nov 18, 2025 | Public REST API outageThe Cloudflare outage issue has been resolved. All our services and APIs are operating normally. We apologize for any inconvenience this may have caused and thank you for your patience. | 5 min | Resolved |
Hear about the next one while it is open
Everything above is a record written after the fact. We can email you when the next Stability AI incident opens instead, at the point where knowing still changes what you do.
Free, no password, no card. Unsubscribe in one click.
How to Read This Stability AI Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Stability AI acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single Stability AI outage in this window ran 4h 7m, against a mean recovery of 2h 6m. If you depend on Stability AI in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.