Skip to content

Outage tracker / Stripe

Is Stripe down?

I'm having a problem

Operationalchecked moments ago

We reached Stripe from all 10 regions we check.

As of Oct 5, 2026, 9:04 PM UTC, Stripe answered RealUptime's probes in all 10 regions that returned a reading.

Functional endpoints verified

No outage recorded in the 58 days we have measured Stripe (since Aug 8, 2026).

our independent probeslive · checked Oct 5, 2026, 9:04 PM UTC
US-East204 msOperational
US-West807 msOperational
Europe89 msOperational
Asia-Pacific101 msOperational
US-Central168 msOperational
Canada363 msOperational
UK68 msOperational
Southeast Asia368 msOperational
Australia282 msOperational
South America372 msOperational
their status pagetheir claim, not our reading

Stripe publishes no status feed we can read, so the only independent reading here is ours on the left.

Stripe response time, by region

US-East
284msp95 · latest
500ms250ms0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 500ms. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 278ms2026-09-07 UTC: p95 228ms2026-09-08 UTC: p95 214ms2026-09-09 UTC: p95 255ms2026-09-10 UTC: p95 233ms2026-09-11 UTC: p95 261ms2026-09-12 UTC: p95 254ms2026-09-13 UTC: p95 236ms2026-09-14 UTC: p95 288ms2026-09-15 UTC: p95 297ms2026-09-16 UTC: p95 345ms2026-09-17 UTC: p95 331ms2026-09-18 UTC: p95 339ms2026-09-19 UTC: p95 353ms2026-09-20 UTC: p95 320ms2026-09-21 UTC: p95 339ms2026-09-22 UTC: p95 329ms2026-09-23 UTC: p95 374ms2026-09-24 UTC: p95 430ms2026-09-25 UTC: p95 352ms2026-09-26 UTC: p95 350ms2026-09-27 UTC: p95 378ms2026-09-28 UTC: p95 360ms2026-09-29 UTC: p95 356ms2026-09-30 UTC: p95 333ms2026-10-01 UTC: p95 330ms2026-10-02 UTC: p95 346ms2026-10-03 UTC: p95 298ms2026-10-04 UTC: p95 291ms2026-10-05 UTC: p95 284ms
Sep 6Sep 20Oct 5
US-West
644msp95 · latest
2s1s0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 484ms2026-09-07 UTC: p95 522ms2026-09-08 UTC: p95 558ms2026-09-09 UTC: p95 368ms2026-09-10 UTC: p95 428ms2026-09-11 UTC: p95 337ms2026-09-12 UTC: p95 377ms2026-09-13 UTC: p95 317ms2026-09-14 UTC: p95 338ms2026-09-15 UTC: p95 452ms2026-09-16 UTC: p95 1.1s2026-09-17 UTC: p95 1.2s2026-09-18 UTC: p95 366ms2026-09-19 UTC: p95 494ms2026-09-20 UTC: p95 548ms2026-09-21 UTC: p95 598ms2026-09-22 UTC: p95 1.0s2026-09-23 UTC: p95 736ms2026-09-24 UTC: p95 714ms2026-09-25 UTC: p95 1.1s2026-09-26 UTC: p95 879ms2026-09-27 UTC: p95 518ms2026-09-28 UTC: p95 558ms2026-09-29 UTC: p95 607ms2026-09-30 UTC: p95 640ms2026-10-01 UTC: p95 616ms2026-10-02 UTC: p95 696ms2026-10-03 UTC: p95 692ms2026-10-04 UTC: p95 607ms2026-10-05 UTC: p95 644ms
Sep 6Sep 20Oct 5
Europe
236msp95 · latest
500ms250ms0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 500ms. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 157ms2026-09-07 UTC: p95 180ms2026-09-08 UTC: p95 128ms2026-09-09 UTC: p95 133ms2026-09-10 UTC: p95 155ms2026-09-11 UTC: p95 292ms2026-09-12 UTC: p95 165ms2026-09-13 UTC: p95 214ms2026-09-14 UTC: p95 254ms2026-09-15 UTC: p95 196ms2026-09-16 UTC: p95 148ms2026-09-17 UTC: p95 145ms2026-09-18 UTC: p95 124ms2026-09-19 UTC: p95 135ms2026-09-20 UTC: p95 134ms2026-09-21 UTC: p95 143ms2026-09-22 UTC: p95 130ms2026-09-23 UTC: p95 166ms2026-09-24 UTC: p95 195ms2026-09-25 UTC: p95 184ms2026-09-26 UTC: p95 187ms2026-09-27 UTC: p95 210ms2026-09-28 UTC: p95 228ms2026-09-29 UTC: p95 177ms2026-09-30 UTC: p95 194ms2026-10-01 UTC: p95 220ms2026-10-02 UTC: p95 298ms2026-10-03 UTC: p95 326ms2026-10-04 UTC: p95 246ms2026-10-05 UTC: p95 236ms
Sep 6Sep 20Oct 5
Asia-Pacific
417msp95 · latest
500ms250ms0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 500ms. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 332ms2026-09-07 UTC: p95 299ms2026-09-08 UTC: p95 280ms2026-09-09 UTC: p95 341ms2026-09-10 UTC: p95 267ms2026-09-11 UTC: p95 283ms2026-09-12 UTC: p95 297ms2026-09-13 UTC: p95 244ms2026-09-14 UTC: p95 253ms2026-09-15 UTC: p95 245ms2026-09-16 UTC: p95 260ms2026-09-17 UTC: p95 288ms2026-09-18 UTC: p95 295ms2026-09-19 UTC: p95 328ms2026-09-20 UTC: p95 294ms2026-09-21 UTC: p95 403ms2026-09-22 UTC: p95 458ms2026-09-23 UTC: p95 469ms2026-09-24 UTC: p95 362ms2026-09-25 UTC: p95 334ms2026-09-26 UTC: p95 429ms2026-09-27 UTC: p95 451ms2026-09-28 UTC: p95 371ms2026-09-29 UTC: p95 370ms2026-09-30 UTC: p95 385ms2026-10-01 UTC: p95 373ms2026-10-02 UTC: p95 382ms2026-10-03 UTC: p95 353ms2026-10-04 UTC: p95 475ms2026-10-05 UTC: p95 417ms
Sep 6Sep 20Oct 5
US-Central
1.1sp95 · latest
2s1s0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 595ms2026-09-07 UTC: p95 557ms2026-09-08 UTC: p95 646ms2026-09-09 UTC: p95 704ms2026-09-10 UTC: p95 605ms2026-09-11 UTC: p95 644ms2026-09-12 UTC: p95 801ms2026-09-13 UTC: p95 581ms2026-09-14 UTC: p95 512ms2026-09-15 UTC: p95 849ms2026-09-16 UTC: p95 544ms2026-09-17 UTC: p95 546ms2026-09-18 UTC: p95 533ms2026-09-19 UTC: p95 563ms2026-09-20 UTC: p95 518ms2026-09-21 UTC: p95 545ms2026-09-22 UTC: p95 562ms2026-09-23 UTC: p95 675ms2026-09-24 UTC: p95 833ms2026-09-25 UTC: p95 650ms2026-09-26 UTC: p95 773ms2026-09-27 UTC: p95 610ms2026-09-28 UTC: p95 580ms2026-09-29 UTC: p95 476ms2026-09-30 UTC: p95 700ms2026-10-01 UTC: p95 735ms2026-10-02 UTC: p95 915ms2026-10-03 UTC: p95 560ms2026-10-04 UTC: p95 1.1s2026-10-05 UTC: p95 1.1s
Sep 6Sep 20Oct 5
Canada
1.2sp95 · latest
2s1s0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 605ms2026-09-07 UTC: p95 684ms2026-09-08 UTC: p95 495ms2026-09-09 UTC: p95 446ms2026-09-10 UTC: p95 386ms2026-09-11 UTC: p95 403ms2026-09-12 UTC: p95 486ms2026-09-13 UTC: p95 528ms2026-09-14 UTC: p95 524ms2026-09-15 UTC: p95 617ms2026-09-16 UTC: p95 514ms2026-09-17 UTC: p95 732ms2026-09-18 UTC: p95 704ms2026-09-19 UTC: p95 477ms2026-09-20 UTC: p95 458ms2026-09-21 UTC: p95 358ms2026-09-22 UTC: p95 393ms2026-09-23 UTC: p95 339ms2026-09-24 UTC: p95 600ms2026-09-25 UTC: p95 583ms2026-09-26 UTC: p95 490ms2026-09-27 UTC: p95 440ms2026-09-28 UTC: p95 528ms2026-09-29 UTC: p95 468ms2026-09-30 UTC: p95 500ms2026-10-01 UTC: p95 478ms2026-10-02 UTC: p95 922ms2026-10-03 UTC: p95 740ms2026-10-04 UTC: p95 826ms2026-10-05 UTC: p95 1.2s
Sep 6Sep 20Oct 5
UK
235msp95 · latest
500ms250ms0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 500ms. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 277ms2026-09-07 UTC: p95 249ms2026-09-08 UTC: p95 219ms2026-09-09 UTC: p95 216ms2026-09-10 UTC: p95 257ms2026-09-11 UTC: p95 237ms2026-09-12 UTC: p95 235ms2026-09-13 UTC: p95 200ms2026-09-14 UTC: p95 205ms2026-09-15 UTC: p95 253ms2026-09-16 UTC: p95 229ms2026-09-17 UTC: p95 380ms2026-09-18 UTC: p95 342ms2026-09-19 UTC: p95 337ms2026-09-20 UTC: p95 315ms2026-09-21 UTC: p95 333ms2026-09-22 UTC: p95 349ms2026-09-23 UTC: p95 314ms2026-09-24 UTC: p95 292ms2026-09-25 UTC: p95 252ms2026-09-26 UTC: p95 273ms2026-09-27 UTC: p95 262ms2026-09-28 UTC: p95 265ms2026-09-29 UTC: p95 298ms2026-09-30 UTC: p95 278ms2026-10-01 UTC: p95 381ms2026-10-02 UTC: p95 287ms2026-10-03 UTC: p95 251ms2026-10-04 UTC: p95 315ms2026-10-05 UTC: p95 235ms
Sep 6Sep 20Oct 5
Southeast Asia
682msp95 · 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 794ms2026-09-07 UTC: p95 632ms2026-09-08 UTC: p95 623ms2026-09-09 UTC: p95 731ms2026-09-10 UTC: p95 697ms2026-09-11 UTC: p95 682ms2026-09-12 UTC: p95 597ms2026-09-13 UTC: p95 885ms2026-09-14 UTC: p95 767ms2026-09-15 UTC: p95 662ms2026-09-16 UTC: p95 596ms2026-09-17 UTC: p95 532ms2026-09-18 UTC: p95 834ms2026-09-19 UTC: p95 659ms2026-09-20 UTC: p95 734ms2026-09-21 UTC: p95 950ms2026-09-22 UTC: p95 1.1s2026-09-23 UTC: p95 1.2s2026-09-24 UTC: p95 1.1s2026-09-25 UTC: p95 965ms2026-09-26 UTC: p95 909ms2026-09-27 UTC: p95 856ms2026-09-28 UTC: p95 855ms2026-09-29 UTC: p95 848ms2026-09-30 UTC: p95 734ms2026-10-01 UTC: p95 600ms2026-10-02 UTC: p95 654ms2026-10-03 UTC: p95 778ms2026-10-04 UTC: p95 612ms2026-10-05 UTC: p95 682ms
Sep 6Sep 20Oct 5
Australia
850msp95 · 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 704ms2026-09-07 UTC: p95 764ms2026-09-08 UTC: p95 604ms2026-09-09 UTC: p95 655ms2026-09-10 UTC: p95 634ms2026-09-11 UTC: p95 668ms2026-09-12 UTC: p95 845ms2026-09-13 UTC: p95 934ms2026-09-14 UTC: p95 572ms2026-09-15 UTC: p95 619ms2026-09-16 UTC: p95 651ms2026-09-17 UTC: p95 718ms2026-09-18 UTC: p95 748ms2026-09-19 UTC: p95 666ms2026-09-20 UTC: p95 849ms2026-09-21 UTC: p95 653ms2026-09-22 UTC: p95 727ms2026-09-23 UTC: p95 581ms2026-09-24 UTC: p95 610ms2026-09-25 UTC: p95 662ms2026-09-26 UTC: p95 997ms2026-09-27 UTC: p95 864ms2026-09-28 UTC: p95 796ms2026-09-29 UTC: p95 668ms2026-09-30 UTC: p95 889ms2026-10-01 UTC: p95 1.0s2026-10-02 UTC: p95 706ms2026-10-03 UTC: p95 725ms2026-10-04 UTC: p95 1.1s2026-10-05 UTC: p95 850ms
Sep 6Sep 20Oct 5
South America
1.0sp95 · 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.1s2026-09-07 UTC: p95 853ms2026-09-08 UTC: p95 940ms2026-09-09 UTC: p95 782ms2026-09-10 UTC: p95 1.0s2026-09-11 UTC: p95 1.1s2026-09-12 UTC: p95 806ms2026-09-13 UTC: p95 749ms2026-09-14 UTC: p95 803ms2026-09-15 UTC: p95 763ms2026-09-16 UTC: p95 964ms2026-09-17 UTC: p95 1.1s2026-09-18 UTC: p95 1.2s2026-09-19 UTC: p95 1.2s2026-09-20 UTC: p95 1.3s2026-09-21 UTC: p95 1.2s2026-09-22 UTC: p95 798ms2026-09-23 UTC: p95 787ms2026-09-24 UTC: p95 916ms2026-09-25 UTC: p95 815ms2026-09-26 UTC: p95 1.1s2026-09-27 UTC: p95 813ms2026-09-28 UTC: p95 1.1s2026-09-29 UTC: p95 790ms2026-09-30 UTC: p95 1.1s2026-10-01 UTC: p95 974ms2026-10-02 UTC: p95 877ms2026-10-03 UTC: p95 1.1s2026-10-04 UTC: p95 1.0s2026-10-05 UTC: p95 1.0s
Sep 6Sep 20Oct 5

Is it Stripe, 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 Stripe -- it cannot diagnose Stripe's own systems.

What we measured, function by function

Stripe 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 auth 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
  • APIUS-East: OperationalUS-West: OperationalEurope: OperationalAsia-Pacific: OperationalUS-Central: OperationalCanada: OperationalUK: OperationalSoutheast Asia: OperationalAustralia: OperationalSouth America: Operational
  • AuthprimaryUS-East: OperationalUS-West: OperationalEurope: OperationalAsia-Pacific: OperationalUS-Central: OperationalCanada: OperationalUK: OperationalSoutheast Asia: OperationalAustralia: OperationalSouth America: Operational

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

Get told when we measure this

We will tell you when our probes stop reaching Stripe, and again when they can reach it again. That is our own measurement from ten regions, not Stripe'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: 204msstatus code: 401checked: Oct 5, 2026, 9:02 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach Stripe normally. We do not have enough reports from US-East to say anything about what people there are seeing.
    • US-West
      Operationallatency: 807msstatus code: 401checked: Oct 5, 2026, 9:01 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach Stripe normally. We do not have enough reports from US-West to say anything about what people there are seeing.
    • US-Central
      Operationallatency: 168msstatus code: 401checked: Oct 5, 2026, 9:01 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach Stripe normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
    • Canada
      Operationallatency: 363msstatus code: 401checked: Oct 5, 2026, 9:01 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach Stripe normally. We do not have enough reports from Canada to say anything about what people there are seeing.
  • South America
    Operationallatency: 372msstatus code: 401checked: Oct 5, 2026, 8:59 PM UTC
    0 people in the last 5 minutesNot enough reports to sayOur South America probes reach Stripe normally. We do not have enough reports from South America to say anything about what people there are seeing.
  • Europe
    OperationalEurope, UK
    • Europe
      Operationallatency: 89msstatus code: 401checked: Oct 5, 2026, 9:03 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach Stripe normally. We do not have enough reports from Europe to say anything about what people there are seeing.
    • UK
      Operationallatency: 68msstatus code: 401checked: Oct 5, 2026, 9:01 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur UK probes reach Stripe 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: 101msstatus code: 401checked: Oct 5, 2026, 9:04 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach Stripe normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
    • Southeast Asia
      Operationallatency: 368msstatus code: 401checked: Oct 5, 2026, 9:00 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach Stripe normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
    • Australia
      Operationallatency: 282msstatus code: 401checked: Oct 5, 2026, 9:01 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach Stripe 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 Stripe, 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 Stripe yet, which is not evidence that nothing is wrong.

Recent outages

No outages on record yet for Stripe.

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

We have been measuring Stripe since August 8, 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 Stripe covering any window you pick, with our measurements and Stripe's own claim at the time, side by side.

Full availability history for Stripe: 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

Stripe uptime measured by RealUptimeLive, from this page's own readings.
[![Stripe uptime measured by RealUptime](https://realuptime.io/outages/stripe/badge.svg?days=30)](https://realuptime.io/outages/stripe)
<a href="https://realuptime.io/outages/stripe"><img src="https://realuptime.io/outages/stripe/badge.svg?days=30" alt="Stripe 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 Stripe's SLA implies, from our measurement

At or above your target

We measured none of downtime for Stripe 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 Stripe'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: auth surface
https://api.stripe.com/v1/charges
secondary
https://status.stripe.com/
secondaryfunctional: live API
https://api.stripe.com/v1/balance
RealUptime is not affiliated with Stripe; the name identifies what we measured, and nothing here speaks for Stripe's own team. We send a single web request to Stripe from 10 regions on our own schedule and time the response. We do not see inside Stripe's systems, do not use an account or real transaction, and are not the same signal Stripe's own team has access to. Treat this as one external data point, not a verdict. At least one endpoint we check for Stripe 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.