Vendor reports: partial outageResolved · vendor status “resolved”Official status API
Investigating elevated 500s for generation endpoints
Reported by Stability AI · AI & ML · source last read 4 min ago
- Vendor start
- Sep 14, 2026, 16:33 UTC
- Vendor's clock
- Resolved
- Sep 14, 2026, 20:41 UTC
- Vendor's clock
- First seen by Statuswall
- Before tracking began
- Statuswall's clock
- Duration
- 4 h 8 min
- From vendor start and resolution
Summary
Built from the facts below, no AI
Potential impact, not a confirmed outage of your systems.
What the vendor confirmed
What is unknown
Last update in these facts: 2026-09-14 20:41 UTC · summary s1, evidence 9c251295a86ce2d2
Evidence (7)
- E1Stability AI reports partial outage. (vendor) source (opens in a new tab)
- E2Vendor title: "Investigating elevated 500s for generation endpoints". (vendor) source (opens in a new tab)
- E3Vendor status word: "resolved". (vendor) source (opens in a new tab)
- E4Vendor-reported start: 2026-09-14 16:33 UTC. (vendor) source (opens in a new tab)
- E5The vendor did not state which regions are affected. (Statuswall)
- E6The vendor attached no components. (Statuswall)
- E7Vendor-reported resolution: 2026-09-14 20:41 UTC. (vendor)
Affected scope
Not stated by the vendor
Components: not stated by the vendor
No region Statuswall recognises is stated for this incident (place names and provider-specific codes are not converted). It is not assumed to be global.
Potential relevance
Stability AI is not in your stack. Follow it to see whether reports like this fall inside the regions you use.
Timeline
Vendor times come from the vendor. “Seen by Statuswall” times are when Statuswall noticed a change, which can lag the vendor by a few minutes. Statuswall does not store the vendor's update text; read it on the official page.
- Sep 14, 2026, 16:33 UTCVendor-reported startVendor time
- Sep 14, 2026, 20:41 UTCVendor-reported resolutionVendor time
No changes observed yet. Statuswall began recording changes on incidents in November 2026.