Skip to content

Outage tracker / Stability AI

Is Stability AI down?

I'm having a problem

Operationalchecked 10 minutes ago

We reached Stability AI from all 10 regions we check.

As of Oct 5, 2026, 8:07 PM UTC, Stability AI answered RealUptime's probes in all 10 regions that returned a reading.

Functional endpoints verified

No outage recorded in the 44 days we have measured Stability AI (since Aug 22, 2026).

our independent probeslive · checked Oct 5, 2026, 8:07 PM UTC
US-East435 msOperational
US-West237 msOperational
Europe1035 msOperational
Asia-Pacific225 msOperational
US-Central135 msOperational
Canada163 msOperational
UK387 msOperational
Southeast Asia909 msOperational
Australia692 msOperational
South America248 msOperational
their status pagetheir claim, not our reading

Stability AI reports: All systems operational (“All Systems Operational”)

from Stability AI's own status page, checked Oct 5, 2026, 8:13 PM UTC
Our probes and Stability AI's own status page agree: both show Stability AI as reachable right now.

Stability AI's own component breakdown, as they publish it

  • Stability.ai Platform & ServicesOperational

These are Stability AI's components, named and scored by Stability AI. We do not map them onto the functions we check above, because we have no way to know which of their components our checks touch. Two lists, side by side, neither one rewriting the other.

This is Stability AI's own claim about their service, shown separately from what we measured. We never change our own numbers based on what a vendor reports, and this reading never changes theirs. Read both.

Stability AI response time, by region

US-East
419msp95 · latest
2s1s0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 861ms2026-09-07 UTC: p95 1.0s2026-09-08 UTC: p95 1.1s2026-09-09 UTC: p95 1.0s2026-09-10 UTC: p95 965ms2026-09-11 UTC: p95 997ms2026-09-12 UTC: p95 1.1s2026-09-13 UTC: p95 1.1s2026-09-14 UTC: p95 856ms2026-09-15 UTC: p95 434ms2026-09-16 UTC: p95 382ms2026-09-17 UTC: p95 341ms2026-09-18 UTC: p95 355ms2026-09-19 UTC: p95 338ms2026-09-20 UTC: p95 354ms2026-09-21 UTC: p95 468ms2026-09-22 UTC: p95 422ms2026-09-23 UTC: p95 405ms2026-09-24 UTC: p95 313ms2026-09-25 UTC: p95 473ms2026-09-26 UTC: p95 318ms2026-09-27 UTC: p95 345ms2026-09-28 UTC: p95 366ms2026-09-29 UTC: p95 376ms2026-09-30 UTC: p95 378ms2026-10-01 UTC: p95 358ms2026-10-02 UTC: p95 364ms2026-10-03 UTC: p95 343ms2026-10-04 UTC: p95 462ms2026-10-05 UTC: p95 419ms
Sep 6Sep 20Oct 5
US-West
390msp95 · latest
1s500ms0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 398ms2026-09-07 UTC: p95 505ms2026-09-08 UTC: p95 434ms2026-09-09 UTC: p95 368ms2026-09-10 UTC: p95 349ms2026-09-11 UTC: p95 381ms2026-09-12 UTC: p95 333ms2026-09-13 UTC: p95 502ms2026-09-14 UTC: p95 300ms2026-09-15 UTC: p95 351ms2026-09-16 UTC: p95 285ms2026-09-17 UTC: p95 258ms2026-09-18 UTC: p95 276ms2026-09-19 UTC: p95 238ms2026-09-20 UTC: p95 261ms2026-09-21 UTC: p95 347ms2026-09-22 UTC: p95 351ms2026-09-23 UTC: p95 386ms2026-09-24 UTC: p95 350ms2026-09-25 UTC: p95 382ms2026-09-26 UTC: p95 356ms2026-09-27 UTC: p95 378ms2026-09-28 UTC: p95 394ms2026-09-29 UTC: p95 394ms2026-09-30 UTC: p95 406ms2026-10-01 UTC: p95 384ms2026-10-02 UTC: p95 359ms2026-10-03 UTC: p95 378ms2026-10-04 UTC: p95 400ms2026-10-05 UTC: p95 390ms
Sep 6Sep 20Oct 5
Europe
678msp95 · latest
1s500ms0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 771ms2026-09-07 UTC: p95 699ms2026-09-08 UTC: p95 770ms2026-09-09 UTC: p95 773ms2026-09-10 UTC: p95 740ms2026-09-11 UTC: p95 765ms2026-09-12 UTC: p95 769ms2026-09-13 UTC: p95 659ms2026-09-14 UTC: p95 720ms2026-09-15 UTC: p95 674ms2026-09-16 UTC: p95 551ms2026-09-17 UTC: p95 701ms2026-09-18 UTC: p95 664ms2026-09-19 UTC: p95 625ms2026-09-20 UTC: p95 600ms2026-09-21 UTC: p95 539ms2026-09-22 UTC: p95 806ms2026-09-23 UTC: p95 762ms2026-09-24 UTC: p95 749ms2026-09-25 UTC: p95 822ms2026-09-26 UTC: p95 715ms2026-09-27 UTC: p95 707ms2026-09-28 UTC: p95 828ms2026-09-29 UTC: p95 819ms2026-09-30 UTC: p95 761ms2026-10-01 UTC: p95 838ms2026-10-02 UTC: p95 858ms2026-10-03 UTC: p95 900ms2026-10-04 UTC: p95 800ms2026-10-05 UTC: p95 678ms
Sep 6Sep 20Oct 5
Asia-Pacific
652msp95 · latest
1s500ms0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 880ms2026-09-07 UTC: p95 834ms2026-09-08 UTC: p95 848ms2026-09-09 UTC: p95 869ms2026-09-10 UTC: p95 692ms2026-09-11 UTC: p95 728ms2026-09-12 UTC: p95 804ms2026-09-13 UTC: p95 883ms2026-09-14 UTC: p95 781ms2026-09-15 UTC: p95 636ms2026-09-16 UTC: p95 621ms2026-09-17 UTC: p95 701ms2026-09-18 UTC: p95 560ms2026-09-19 UTC: p95 612ms2026-09-20 UTC: p95 635ms2026-09-21 UTC: p95 752ms2026-09-22 UTC: p95 647ms2026-09-23 UTC: p95 663ms2026-09-24 UTC: p95 724ms2026-09-25 UTC: p95 645ms2026-09-26 UTC: p95 628ms2026-09-27 UTC: p95 579ms2026-09-28 UTC: p95 564ms2026-09-29 UTC: p95 614ms2026-09-30 UTC: p95 823ms2026-10-01 UTC: p95 626ms2026-10-02 UTC: p95 864ms2026-10-03 UTC: p95 604ms2026-10-04 UTC: p95 649ms2026-10-05 UTC: p95 652ms
Sep 6Sep 20Oct 5
US-Central
349msp95 · latest
1s500ms0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 853ms2026-09-07 UTC: p95 850ms2026-09-08 UTC: p95 832ms2026-09-09 UTC: p95 800ms2026-09-10 UTC: p95 911ms2026-09-11 UTC: p95 987ms2026-09-12 UTC: p95 888ms2026-09-13 UTC: p95 947ms2026-09-14 UTC: p95 868ms2026-09-15 UTC: p95 456ms2026-09-16 UTC: p95 393ms2026-09-17 UTC: p95 375ms2026-09-18 UTC: p95 336ms2026-09-19 UTC: p95 343ms2026-09-20 UTC: p95 353ms2026-09-21 UTC: p95 344ms2026-09-22 UTC: p95 467ms2026-09-23 UTC: p95 401ms2026-09-24 UTC: p95 543ms2026-09-25 UTC: p95 361ms2026-09-26 UTC: p95 342ms2026-09-27 UTC: p95 361ms2026-09-28 UTC: p95 415ms2026-09-29 UTC: p95 361ms2026-09-30 UTC: p95 349ms2026-10-01 UTC: p95 424ms2026-10-02 UTC: p95 369ms2026-10-03 UTC: p95 526ms2026-10-04 UTC: p95 429ms2026-10-05 UTC: p95 349ms
Sep 6Sep 20Oct 5
Canada
376msp95 · latest
1s500ms0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 566ms2026-09-07 UTC: p95 636ms2026-09-08 UTC: p95 515ms2026-09-09 UTC: p95 546ms2026-09-10 UTC: p95 696ms2026-09-11 UTC: p95 651ms2026-09-12 UTC: p95 682ms2026-09-13 UTC: p95 882ms2026-09-14 UTC: p95 776ms2026-09-15 UTC: p95 467ms2026-09-16 UTC: p95 495ms2026-09-17 UTC: p95 511ms2026-09-18 UTC: p95 468ms2026-09-19 UTC: p95 438ms2026-09-20 UTC: p95 471ms2026-09-21 UTC: p95 417ms2026-09-22 UTC: p95 401ms2026-09-23 UTC: p95 527ms2026-09-24 UTC: p95 403ms2026-09-25 UTC: p95 433ms2026-09-26 UTC: p95 393ms2026-09-27 UTC: p95 454ms2026-09-28 UTC: p95 390ms2026-09-29 UTC: p95 415ms2026-09-30 UTC: p95 450ms2026-10-01 UTC: p95 498ms2026-10-02 UTC: p95 449ms2026-10-03 UTC: p95 427ms2026-10-04 UTC: p95 507ms2026-10-05 UTC: p95 376ms
Sep 6Sep 20Oct 5
UK
723msp95 · latest
1s500ms0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 741ms2026-09-07 UTC: p95 774ms2026-09-08 UTC: p95 801ms2026-09-09 UTC: p95 692ms2026-09-10 UTC: p95 605ms2026-09-11 UTC: p95 707ms2026-09-12 UTC: p95 697ms2026-09-13 UTC: p95 698ms2026-09-14 UTC: p95 841ms2026-09-15 UTC: p95 558ms2026-09-16 UTC: p95 609ms2026-09-17 UTC: p95 627ms2026-09-18 UTC: p95 649ms2026-09-19 UTC: p95 601ms2026-09-20 UTC: p95 612ms2026-09-21 UTC: p95 579ms2026-09-22 UTC: p95 688ms2026-09-23 UTC: p95 449ms2026-09-24 UTC: p95 653ms2026-09-25 UTC: p95 636ms2026-09-26 UTC: p95 571ms2026-09-27 UTC: p95 523ms2026-09-28 UTC: p95 650ms2026-09-29 UTC: p95 637ms2026-09-30 UTC: p95 697ms2026-10-01 UTC: p95 671ms2026-10-02 UTC: p95 652ms2026-10-03 UTC: p95 621ms2026-10-04 UTC: p95 755ms2026-10-05 UTC: p95 723ms
Sep 6Sep 20Oct 5
Southeast Asia
1.0sp95 · latest
2s1s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 877ms2026-09-07 UTC: p95 821ms2026-09-08 UTC: p95 918ms2026-09-09 UTC: p95 888ms2026-09-10 UTC: p95 881ms2026-09-11 UTC: p95 899ms2026-09-12 UTC: p95 840ms2026-09-13 UTC: p95 909ms2026-09-14 UTC: p95 870ms2026-09-15 UTC: p95 767ms2026-09-16 UTC: p95 790ms2026-09-17 UTC: p95 770ms2026-09-18 UTC: p95 805ms2026-09-19 UTC: p95 819ms2026-09-20 UTC: p95 866ms2026-09-21 UTC: p95 825ms2026-09-22 UTC: p95 712ms2026-09-23 UTC: p95 795ms2026-09-24 UTC: p95 946ms2026-09-25 UTC: p95 776ms2026-09-26 UTC: p95 831ms2026-09-27 UTC: p95 804ms2026-09-28 UTC: p95 794ms2026-09-29 UTC: p95 932ms2026-09-30 UTC: p95 677ms2026-10-01 UTC: p95 794ms2026-10-02 UTC: p95 728ms2026-10-03 UTC: p95 857ms2026-10-04 UTC: p95 1.0s2026-10-05 UTC: p95 1.0s
Sep 6Sep 20Oct 5
Australia
723msp95 · latest
2s1s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 904ms2026-09-07 UTC: p95 819ms2026-09-08 UTC: p95 930ms2026-09-09 UTC: p95 896ms2026-09-10 UTC: p95 1.0s2026-09-11 UTC: p95 924ms2026-09-12 UTC: p95 929ms2026-09-13 UTC: p95 953ms2026-09-14 UTC: p95 976ms2026-09-15 UTC: p95 784ms2026-09-16 UTC: p95 730ms2026-09-17 UTC: p95 803ms2026-09-18 UTC: p95 843ms2026-09-19 UTC: p95 713ms2026-09-20 UTC: p95 726ms2026-09-21 UTC: p95 720ms2026-09-22 UTC: p95 903ms2026-09-23 UTC: p95 756ms2026-09-24 UTC: p95 716ms2026-09-25 UTC: p95 719ms2026-09-26 UTC: p95 713ms2026-09-27 UTC: p95 731ms2026-09-28 UTC: p95 723ms2026-09-29 UTC: p95 762ms2026-09-30 UTC: p95 736ms2026-10-01 UTC: p95 614ms2026-10-02 UTC: p95 754ms2026-10-03 UTC: p95 702ms2026-10-04 UTC: p95 699ms2026-10-05 UTC: p95 723ms
Sep 6Sep 20Oct 5
South America
1.5sp95 · latest
2s1s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 1.2s2026-09-07 UTC: p95 1.2s2026-09-08 UTC: p95 1.3s2026-09-09 UTC: p95 1.3s2026-09-10 UTC: p95 1.3s2026-09-11 UTC: p95 1.2s2026-09-12 UTC: p95 1.3s2026-09-13 UTC: p95 1.2s2026-09-14 UTC: p95 1.1s2026-09-15 UTC: p95 850ms2026-09-16 UTC: p95 1.1s2026-09-17 UTC: p95 1.1s2026-09-18 UTC: p95 1.0s2026-09-19 UTC: p95 1.1s2026-09-20 UTC: p95 940ms2026-09-21 UTC: p95 997ms2026-09-22 UTC: p95 877ms2026-09-23 UTC: p95 993ms2026-09-24 UTC: p95 1.1s2026-09-25 UTC: p95 906ms2026-09-26 UTC: p95 973ms2026-09-27 UTC: p95 1.0s2026-09-28 UTC: p95 1.0s2026-09-29 UTC: p95 1.0s2026-09-30 UTC: p95 983ms2026-10-01 UTC: p95 1.2s2026-10-02 UTC: p95 1.4s2026-10-03 UTC: p95 1.4s2026-10-04 UTC: p95 1.6s2026-10-05 UTC: p95 1.5s
Sep 6Sep 20Oct 5

Is it Stability AI, or is it you?

Watching an outage above does not tell you whether your own connection or site is also having a problem. Enter your own URL for one live check, right now, no signup. This checks the site you enter, not Stability AI -- it cannot diagnose Stability AI's own systems.

What we measured, function by function

Stability AI answers on more than one surface, and they can fail apart. Each row is one surface, checked from the same regions. The verdict above follows the api row, because that is the surface we treat as this service's own; a failure on any other row is a partial outage, not a full one.

  • WebUS-East: OperationalUS-West: OperationalEurope: OperationalAsia-Pacific: OperationalUS-Central: OperationalCanada: OperationalUK: OperationalSoutheast Asia: OperationalAustralia: OperationalSouth America: Operational
  • APIprimaryUS-East: OperationalUS-West: OperationalEurope: OperationalAsia-Pacific: OperationalUS-Central: OperationalCanada: OperationalUK: OperationalSoutheast Asia: OperationalAustralia: OperationalSouth America: Operational

Get an email when we see Stability AI go down, and when it is back

Get told when we measure this

We will tell you when our probes stop reaching Stability AI, and again when they can reach it again. That is our own measurement from ten regions, not Stability AI's status page. No account, no card.

Delivery channel

Double opt-in: nothing is sent until you click the link in the confirmation email. One email when a measured outage opens, one when it closes, and a one-click unsubscribe in every one. We do not send anything else to this address.

What are you seeing? (optional)

No account needed, and we never store your IP address. Reports are counted separately from our own measurements and are always shown as unverified.

What we measured, and what people reported

  • North America
    OperationalUS-East, US-West, US-Central, Canada
    • US-East
      Operationallatency: 435msstatus code: 401checked: Oct 5, 2026, 7:57 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach Stability AI normally. We do not have enough reports from US-East to say anything about what people there are seeing.
    • US-West
      Operationallatency: 237msstatus code: 401checked: Oct 5, 2026, 8:07 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach Stability AI normally. We do not have enough reports from US-West to say anything about what people there are seeing.
    • US-Central
      Operationallatency: 135msstatus code: 401checked: Oct 5, 2026, 7:44 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach Stability AI normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
    • Canada
      Operationallatency: 163msstatus code: 401checked: Oct 5, 2026, 7:49 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach Stability AI normally. We do not have enough reports from Canada to say anything about what people there are seeing.
  • South America
    Operationallatency: 248msstatus code: 401checked: Oct 5, 2026, 7:53 PM UTC
    0 people in the last 5 minutesNot enough reports to sayOur South America probes reach Stability AI normally. We do not have enough reports from South America to say anything about what people there are seeing.
  • Europe
    OperationalEurope, UK
    • Europe
      Operationallatency: 1035msstatus code: 401checked: Oct 5, 2026, 7:53 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach Stability AI normally. We do not have enough reports from Europe to say anything about what people there are seeing.
    • UK
      Operationallatency: 387msstatus code: 401checked: Oct 5, 2026, 7:53 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur UK probes reach Stability AI normally. We do not have enough reports from UK to say anything about what people there are seeing.
  • Asia Pacific
    OperationalAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Operationallatency: 225msstatus code: 401checked: Oct 5, 2026, 8:06 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach Stability AI normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
    • Southeast Asia
      Operationallatency: 909msstatus code: 401checked: Oct 5, 2026, 7:53 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach Stability AI normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
    • Australia
      Operationallatency: 692msstatus code: 401checked: Oct 5, 2026, 8:02 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach Stability AI normally. We do not have enough reports from Australia to say anything about what people there are seeing.

Somewhere else or not sure: 0 people in the last 5 minutes

These are unverified reports from people using Stability AI, counted separately from what our own probes measure. Anyone can file one, no account is needed, and the region on a report is chosen by the person filing it. We never open, extend or close an outage in our record based on report volume: only our own measurements do that. We have not received any reports for Stability AI yet, which is not evidence that nothing is wrong.

Recent outages

Investigating elevated 500s for generation endpoints, 4h 8mdeclared on their status page2026-09-14
Public REST API outage, 5mdeclared on their status page2025-11-18

measured entries are our own probes' readings; declared entries are the vendor's. How this check works

We have been measuring Stability AI since August 22, 2026. We show nothing from before that date, and we never add an outage we did not observe ourselves, from any source.

Need this in writing? Generate an SLA evidence report for Stability AI covering any window you pick, with our measurements and Stability AI's own claim at the time, side by side.

Full availability history for Stability AI: 90-day availability by region, month-by-month uptime, and every incident on record.

Monitor your own site the same way

This page shows what we see when we check this service, using the same ten regions, for a site you run. RealUptime Monitor watches your own servers from inside your network, and it starts free.

Start monitoring your own servers

Put this badge in your README

Stability AI uptime measured by RealUptimeLive, from this page's own readings.
[![Stability AI uptime measured by RealUptime](https://realuptime.io/outages/stability-ai/badge.svg?days=30)](https://realuptime.io/outages/stability-ai)
<a href="https://realuptime.io/outages/stability-ai"><img src="https://realuptime.io/outages/stability-ai/badge.svg?days=30" alt="Stability AI uptime measured by RealUptime"></a>

The badge shows the share of our probes that succeeded over the last 30 days, and the window is printed on it so the number always says what period it covers. If our readings go stale it says stale, and if we have no readings it says so: it will not show green on data we cannot vouch for. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.

What Stability AI's SLA implies, from our measurement

At or above your target

We measured none of downtime for Stability AI over the last 30 days, which is 100% uptime by our reading. A 99.9% target allows 43 minutes over that period.

By our measurement there is no shortfall to claim for this period.

This is computed from our own probe measurements, not from Stability AI's SLA instrumentation. Their contract is normally measured against their own systems, with their own exclusions and a claim window, so their figure and ours will differ. Use this to start the conversation and ask for their number. It is not legal advice and it is not a determination of what you are owed.

What we check

primaryfunctional: live API
https://api.stability.ai/v1/engines/list
secondary
https://stability.ai/
secondary
https://status.stability.ai/api/v2/status.json
RealUptime is not affiliated with Stability AI; the name identifies what we measured, and nothing here speaks for Stability AI's own team. We send a single web request to Stability AI from 10 regions on our own schedule and time the response. We do not see inside Stability AI's systems, do not use an account or real transaction, and are not the same signal Stability AI's own team has access to. Treat this as one external data point, not a verdict. At least one endpoint we check for Stability AI is a real functional API call (marked “functional” above), not just a landing page, so a clean read there is a stronger signal than reachability alone, though it still does not cover every feature of the service. Read the full methodology.