Is Stability AI down?

What this Stability AI status page covers

This page covers two related Stability AI access points:

• Website: stability.ai
• API host: api.stability.ai

These hosts can have different availability. The website may open while an API request fails, or the website may be inaccessible while an API integration continues to respond. Identify the exact symptom before treating it as a general outage: a blank page, DNS failure, connection timeout, refused connection, TLS error, HTTP error, authentication failure, or API-specific response.

For API users, a successful connection does not necessarily mean the request is valid. Authentication, endpoint selection, permissions, request parameters, account configuration, rate limits, and upstream processing can all cause failures unrelated to a complete Stability AI outage.

Troubleshooting Stability AI availability

1. Check whether the problem is widespread

Open stability.ai in a private window, then test the relevant API request against api.stability.ai if you use the API. Compare the result on another device or network. Failures reproduced across independent networks and access paths make a service-side problem more plausible; a failure limited to one environment points first to a local, account, or request-specific cause.

Record the exact error rather than only noting that Stability AI is “down.” DNS errors, refused connections, timeouts, TLS failures, HTTP 4xx responses, and HTTP 5xx responses require different follow-up steps.

2. If the Stability AI website does not load

• Refresh once, then try a private window or another browser.
• Test a different network, such as mobile data, to distinguish a local connection or routing problem from a broader availability issue.
• If only your usual browser fails, temporarily disable extensions and clear cached site data for stability.ai.
• If the error mentions DNS, a refused connection, a timeout, or TLS, capture that message before changing DNS, VPN, proxy, firewall, or certificate settings.

3. If the API fails while the website works

Check the request before treating the failure as a platform outage:

• Confirm that the intended api.stability.ai host and endpoint are being used.
• Check the HTTP status and response body. A 4xx response generally points to a request, credential, permission, account, or rate-related issue; a 5xx response is more consistent with a server-side or upstream failure.
• Verify required authentication and parameters without exposing API keys in logs or support reports.
• Test whether the same request fails consistently and whether a simpler, previously successful request works.
• Retry cautiously after a short interval only when the response suggests a temporary network or server problem. Avoid replaying requests that could create duplicate work or charges.

4. If only one account, token, endpoint, or payload fails

A problem limited to one account or request is less consistent with a platform-wide outage. Recheck credentials, permissions, endpoint selection, request formatting, payload size or content, and any account-specific limits shown in the response. Preserve the complete error response and timestamp for escalation, while removing secrets and sensitive input data.

5. If the issue is local or network-specific

Compare networks and check whether other HTTPS sites work. A VPN, proxy, firewall, DNS resolver, security product, or network route may block or misdirect access to Stability AI. Browser restarts will not correct every network problem, so capture the exact error first and avoid changing DNS or certificate settings blindly.

6. When to escalate

Provide the affected host, endpoint, timestamp and time zone, HTTP status, response body, request or correlation ID if available, and whether the issue reproduces elsewhere. Never include API keys, authorization headers, private prompts, or sensitive generated content in a public report.