Skip to content

Outage tracker / Stripe

Is Stripe down?

I'm having a problem

Vendor reports no incidentWhat Stripe reports

Stripe reports no incident on its status page.

As of the last successful poll, 2026-11-05 14:52 UTC.

Stripe's status page

Our regional reading

This is our own reading from outside, shown beside the vendor's statement. It is not counted as a separate outage.

Checks passingchecked moments ago

Our checks of Stripe pass from all 10 regions we check.

As of Nov 5, 2026, 2:59 PM UTC, RealUptime's checks of Stripe passed in all 10 regions that returned a reading.

Front-door and live API checks

our check readinglive · checked Nov 5, 2026, 2:59 PM UTC
US-East485 msChecks passing
US-West574 msChecks passing
Europe118 msChecks passing
Asia-Pacific1395 msChecks passing
US-Central646 msChecks passing
Canada3073 msChecks passing
UK484 msChecks passing
Southeast Asia746 msChecks passing
Australia869 msChecks passing
South America796 msChecks passing
their status pagetheir claim, not our reading

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

Stripe response time, by region

US-East
558msp95 · 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-10-07 UTC: p95 266ms2026-10-08 UTC: p95 279ms2026-10-09 UTC: p95 269ms2026-10-10 UTC: p95 324ms2026-10-11 UTC: p95 302ms2026-10-12 UTC: p95 286ms2026-10-13 UTC: p95 304ms2026-10-14 UTC: p95 279ms2026-10-15 UTC: p95 334ms2026-10-16 UTC: p95 318ms2026-10-17 UTC: p95 895ms2026-10-18 UTC: p95 1.1s2026-10-19 UTC: p95 693ms2026-10-20 UTC: p95 573ms2026-10-21 UTC: p95 566ms2026-10-22 UTC: p95 501ms2026-10-23 UTC: p95 460ms2026-10-24 UTC: p95 452ms2026-10-25 UTC: p95 428ms2026-10-26 UTC: p95 817ms2026-10-27 UTC: p95 538ms2026-10-28 UTC: p95 636ms2026-10-29 UTC: p95 515ms2026-10-30 UTC: p95 601ms2026-10-31 UTC: p95 546ms2026-11-01 UTC: p95 594ms2026-11-02 UTC: p95 1.1s2026-11-03 UTC: p95 644ms2026-11-04 UTC: p95 650ms2026-11-05 UTC: p95 558ms
Oct 7Oct 21Nov 5
US-West
1.1sp95 · latest
2.5s1.3s0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 579ms2026-10-08 UTC: p95 605ms2026-10-09 UTC: p95 986ms2026-10-10 UTC: p95 636ms2026-10-11 UTC: p95 448ms2026-10-12 UTC: p95 642ms2026-10-13 UTC: p95 702ms2026-10-14 UTC: p95 612ms2026-10-15 UTC: p95 586ms2026-10-16 UTC: p95 561ms2026-10-17 UTC: p95 2.0s2026-10-18 UTC: p95 2.3s2026-10-19 UTC: p95 2.3s2026-10-20 UTC: p95 2.2s2026-10-21 UTC: p95 2.1s2026-10-22 UTC: p95 2.3s2026-10-23 UTC: p95 2.2s2026-10-24 UTC: p95 2.1s2026-10-25 UTC: p95 2.2s2026-10-26 UTC: p95 2.3s2026-10-27 UTC: p95 2.2s2026-10-28 UTC: p95 2.2s2026-10-29 UTC: p95 2.1s2026-10-30 UTC: p95 2.2s2026-10-31 UTC: p95 2.1s2026-11-01 UTC: p95 2.3s2026-11-02 UTC: p95 2.2s2026-11-03 UTC: p95 1.2s2026-11-04 UTC: p95 1.2s2026-11-05 UTC: p95 1.1s
Oct 7Oct 21Nov 5
Europe
479msp95 · 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-10-07 UTC: p95 254ms2026-10-08 UTC: p95 204ms2026-10-09 UTC: p95 172ms2026-10-10 UTC: p95 212ms2026-10-11 UTC: p95 138ms2026-10-12 UTC: p95 210ms2026-10-13 UTC: p95 165ms2026-10-14 UTC: p95 124ms2026-10-15 UTC: p95 150ms2026-10-16 UTC: p95 130ms2026-10-17 UTC: p95 183ms2026-10-18 UTC: p95 344ms2026-10-19 UTC: p95 435ms2026-10-20 UTC: p95 335ms2026-10-21 UTC: p95 283ms2026-10-22 UTC: p95 363ms2026-10-23 UTC: p95 268ms2026-10-24 UTC: p95 202ms2026-10-25 UTC: p95 238ms2026-10-26 UTC: p95 303ms2026-10-27 UTC: p95 293ms2026-10-28 UTC: p95 350ms2026-10-29 UTC: p95 295ms2026-10-30 UTC: p95 316ms2026-10-31 UTC: p95 280ms2026-11-01 UTC: p95 296ms2026-11-02 UTC: p95 355ms2026-11-03 UTC: p95 352ms2026-11-04 UTC: p95 385ms2026-11-05 UTC: p95 479ms
Oct 7Oct 21Nov 5
Asia-Pacific
1.1sp95 · latest
2s1s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 369ms2026-10-08 UTC: p95 490ms2026-10-09 UTC: p95 408ms2026-10-10 UTC: p95 381ms2026-10-11 UTC: p95 373ms2026-10-12 UTC: p95 405ms2026-10-13 UTC: p95 531ms2026-10-14 UTC: p95 384ms2026-10-15 UTC: p95 550ms2026-10-16 UTC: p95 399ms2026-10-17 UTC: p95 983ms2026-10-18 UTC: p95 1.2s2026-10-19 UTC: p95 1.2s2026-10-20 UTC: p95 1.2s2026-10-21 UTC: p95 1.2s2026-10-22 UTC: p95 1.1s2026-10-23 UTC: p95 1.2s2026-10-24 UTC: p95 1.3s2026-10-25 UTC: p95 1.2s2026-10-26 UTC: p95 1.4s2026-10-27 UTC: p95 1.3s2026-10-28 UTC: p95 1.2s2026-10-29 UTC: p95 1.1s2026-10-30 UTC: p95 1.2s2026-10-31 UTC: p95 1.2s2026-11-01 UTC: p95 1.3s2026-11-02 UTC: p95 1.4s2026-11-03 UTC: p95 869ms2026-11-04 UTC: p95 1.1s2026-11-05 UTC: p95 1.1s
Oct 7Oct 21Nov 5
US-Central
955msp95 · latest
2.5s1.3s0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 436ms2026-10-08 UTC: p95 974ms2026-10-09 UTC: p95 703ms2026-10-10 UTC: p95 616ms2026-10-11 UTC: p95 573ms2026-10-12 UTC: p95 1.3s2026-10-13 UTC: p95 542ms2026-10-14 UTC: p95 1.1s2026-10-15 UTC: p95 584ms2026-10-16 UTC: p95 822ms2026-10-17 UTC: p95 649ms2026-10-18 UTC: p95 616ms2026-10-19 UTC: p95 917ms2026-10-20 UTC: p95 992ms2026-10-21 UTC: p95 1.9s2026-10-22 UTC: p95 2.0s2026-10-23 UTC: p95 2.2s2026-10-24 UTC: p95 1.9s2026-10-25 UTC: p95 1.9s2026-10-26 UTC: p95 2.0s2026-10-27 UTC: p95 2.1s2026-10-28 UTC: p95 2.0s2026-10-29 UTC: p95 1.9s2026-10-30 UTC: p95 2.0s2026-10-31 UTC: p95 1.9s2026-11-01 UTC: p95 1.9s2026-11-02 UTC: p95 1.9s2026-11-03 UTC: p95 903ms2026-11-04 UTC: p95 908ms2026-11-05 UTC: p95 955ms
Oct 7Oct 21Nov 5
Canada
828msp95 · 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-10-07 UTC: p95 966ms2026-10-08 UTC: p95 469ms2026-10-09 UTC: p95 602ms2026-10-10 UTC: p95 914ms2026-10-11 UTC: p95 532ms2026-10-12 UTC: p95 740ms2026-10-13 UTC: p95 1.0s2026-10-14 UTC: p95 450ms2026-10-15 UTC: p95 1.1s2026-10-16 UTC: p95 977ms2026-10-17 UTC: p95 1.6s2026-10-18 UTC: p95 1.8s2026-10-19 UTC: p95 1.9s2026-10-20 UTC: p95 1.7s2026-10-21 UTC: p95 1.7s2026-10-22 UTC: p95 1.7s2026-10-23 UTC: p95 1.7s2026-10-24 UTC: p95 1.7s2026-10-25 UTC: p95 1.8s2026-10-26 UTC: p95 1.9s2026-10-27 UTC: p95 1.6s2026-10-28 UTC: p95 1.7s2026-10-29 UTC: p95 1.5s2026-10-30 UTC: p95 1.5s2026-10-31 UTC: p95 1.4s2026-11-01 UTC: p95 1.6s2026-11-02 UTC: p95 1.8s2026-11-03 UTC: p95 1.0s2026-11-04 UTC: p95 903ms2026-11-05 UTC: p95 828ms
Oct 7Oct 21Nov 5
UK
612msp95 · 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-10-07 UTC: p95 225ms2026-10-08 UTC: p95 284ms2026-10-09 UTC: p95 277ms2026-10-10 UTC: p95 337ms2026-10-11 UTC: p95 280ms2026-10-12 UTC: p95 308ms2026-10-13 UTC: p95 348ms2026-10-14 UTC: p95 226ms2026-10-15 UTC: p95 308ms2026-10-16 UTC: p95 370ms2026-10-17 UTC: p95 277ms2026-10-18 UTC: p95 463ms2026-10-19 UTC: p95 539ms2026-10-20 UTC: p95 555ms2026-10-21 UTC: p95 585ms2026-10-22 UTC: p95 634ms2026-10-23 UTC: p95 572ms2026-10-24 UTC: p95 596ms2026-10-25 UTC: p95 572ms2026-10-26 UTC: p95 575ms2026-10-27 UTC: p95 573ms2026-10-28 UTC: p95 654ms2026-10-29 UTC: p95 615ms2026-10-30 UTC: p95 717ms2026-10-31 UTC: p95 555ms2026-11-01 UTC: p95 572ms2026-11-02 UTC: p95 555ms2026-11-03 UTC: p95 715ms2026-11-04 UTC: p95 441ms2026-11-05 UTC: p95 612ms
Oct 7Oct 21Nov 5
Southeast Asia
1.4sp95 · 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-10-07 UTC: p95 776ms2026-10-08 UTC: p95 638ms2026-10-09 UTC: p95 640ms2026-10-10 UTC: p95 682ms2026-10-11 UTC: p95 623ms2026-10-12 UTC: p95 582ms2026-10-13 UTC: p95 509ms2026-10-14 UTC: p95 543ms2026-10-15 UTC: p95 806ms2026-10-16 UTC: p95 745ms2026-10-17 UTC: p95 1.2s2026-10-18 UTC: p95 1.4s2026-10-19 UTC: p95 1.6s2026-10-20 UTC: p95 915ms2026-10-21 UTC: p95 1.3s2026-10-22 UTC: p95 1.4s2026-10-23 UTC: p95 1.6s2026-10-24 UTC: p95 1.2s2026-10-25 UTC: p95 1.5s2026-10-26 UTC: p95 1.5s2026-10-27 UTC: p95 1.4s2026-10-28 UTC: p95 1.2s2026-10-29 UTC: p95 1.2s2026-10-30 UTC: p95 1.3s2026-10-31 UTC: p95 1.3s2026-11-01 UTC: p95 1.7s2026-11-02 UTC: p95 1.1s2026-11-03 UTC: p95 1.1s2026-11-04 UTC: p95 1.2s2026-11-05 UTC: p95 1.4s
Oct 7Oct 21Nov 5
Australia
1.7sp95 · latest
2.5s1.3s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 1.2s2026-10-08 UTC: p95 848ms2026-10-09 UTC: p95 740ms2026-10-10 UTC: p95 833ms2026-10-11 UTC: p95 782ms2026-10-12 UTC: p95 735ms2026-10-13 UTC: p95 706ms2026-10-14 UTC: p95 688ms2026-10-15 UTC: p95 778ms2026-10-16 UTC: p95 659ms2026-10-17 UTC: p95 1.5s2026-10-18 UTC: p95 2.0s2026-10-19 UTC: p95 1.9s2026-10-20 UTC: p95 1.8s2026-10-21 UTC: p95 1.9s2026-10-22 UTC: p95 2.0s2026-10-23 UTC: p95 1.9s2026-10-24 UTC: p95 1.9s2026-10-25 UTC: p95 1.8s2026-10-26 UTC: p95 1.9s2026-10-27 UTC: p95 2.0s2026-10-28 UTC: p95 2.0s2026-10-29 UTC: p95 2.0s2026-10-30 UTC: p95 1.9s2026-10-31 UTC: p95 1.9s2026-11-01 UTC: p95 1.9s2026-11-02 UTC: p95 1.7s2026-11-03 UTC: p95 1.6s2026-11-04 UTC: p95 1.6s2026-11-05 UTC: p95 1.7s
Oct 7Oct 21Nov 5
South America
2.1sp95 · latest
10s5s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 10s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 788ms2026-10-08 UTC: p95 811ms2026-10-09 UTC: p95 1.1s2026-10-10 UTC: p95 1.1s2026-10-11 UTC: p95 1.1s2026-10-12 UTC: p95 1.0s2026-10-13 UTC: p95 950ms2026-10-14 UTC: p95 874ms2026-10-15 UTC: p95 1.1s2026-10-16 UTC: p95 693ms2026-10-17 UTC: p95 1.5s2026-10-18 UTC: p95 1.6s2026-10-19 UTC: p95 1.6s2026-10-20 UTC: p95 1.6s2026-10-21 UTC: p95 1.7s2026-10-22 UTC: p95 1.8s2026-10-23 UTC: p95 7.3s2026-10-24 UTC: p95 1.6s2026-10-25 UTC: p95 1.6s2026-10-26 UTC: p95 1.7s2026-10-27 UTC: p95 1.7s2026-10-28 UTC: p95 2.4s2026-10-29 UTC: p95 1.6s2026-10-30 UTC: p95 1.7s2026-10-31 UTC: p95 1.6s2026-11-01 UTC: p95 1.6s2026-11-02 UTC: p95 1.5s2026-11-03 UTC: p95 1.6s2026-11-04 UTC: p95 1.5s2026-11-05 UTC: p95 2.1s
Oct 7Oct 21Nov 5

Check your own site while you wait on Stripe

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: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • APIUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • AuthprimaryUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • DashboardUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • Files APIUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • Stripe.jsUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing

Email me when Stripe reports an incident on its status page, and again when it reports it resolved.

Get an email when Stripe reports an incident

Email me when Stripe reports an incident on its status page, and again when it reports it resolved. No account, no card.

Delivery channel

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

This is Stripe's own statement from its status page, with our regional reading beside it.

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 our checks show, and what people reported

  • North America
    Checks passingUS-East, US-West, US-Central, Canada
    • US-East
      Checks passinglatency: 485msstatus code: 401checked: Nov 5, 2026, 2:58 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
      Checks passinglatency: 574msstatus code: 401checked: Nov 5, 2026, 2:57 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
      Checks passinglatency: 646msstatus code: 401checked: Nov 5, 2026, 2:59 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
      Checks passinglatency: 3073msstatus code: 401checked: Nov 5, 2026, 2:57 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
    Checks passinglatency: 796msstatus code: 401checked: Nov 5, 2026, 2: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
    Checks passingEurope, UK
    • Europe
      Checks passinglatency: 118msstatus code: 401checked: Nov 5, 2026, 2:57 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
      Checks passinglatency: 484msstatus code: 401checked: Nov 5, 2026, 2:59 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
    Checks passingAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Checks passinglatency: 1395msstatus code: 401checked: Nov 5, 2026, 2:57 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
      Checks passinglatency: 746msstatus code: 401checked: Nov 5, 2026, 2:57 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
      Checks passinglatency: 869msstatus code: 401checked: Nov 5, 2026, 2:58 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 probe events

Elevated Instant Payouts failures, 2h 5mdeclared on their status page2026-11-01
Elevated Issuing errors from 17:13 - 20:41 UTC, 4h 36mdeclared on their status page2026-10-28
Elevated Blik errors, 1hdeclared on their status page2026-10-24
Elevated Bancontact errors, 3h 36mdeclared on their status page2026-10-22
Elevated Bancontact errors, 2h 25mdeclared on their status page2026-10-22
Spike in cancellations and expired errors with PayByBank payments, 2h 18mdeclared on their status page2026-10-20
Elevated Revolut Pay errors, 9h 33mdeclared on their status page2026-10-20
Elevated declines on Mastercard, 2h 18mdeclared on their status page2026-10-15

check 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 check readings and Stripe's own claim at the time, side by side.

Full check history for Stripe: 90 days of check results by region, month-by-month uptime by our checks, and every probe event 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

Run a service people depend on? Give them a status page on your own domain, checked every minute from six regions, for $9 a month. Get Starter

Put this badge in your README

Stripe uptime by RealUptime's checksLive, from this page's own readings.
[![Stripe uptime by RealUptime's checks](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 by RealUptime's checks" height="20"></a>

Share of checks passed over 30 days; the window is printed on it. If our readings go stale it says stale, and if we have no readings it says so and shows no color. How the badge works.

To cite this page: RealUptime, "Is Stripe down?", https://realuptime.io/outages/stripe. The readings change with every check, so give the date you read them.

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
secondary
https://js.stripe.com/v3/
secondary
https://dashboard.stripe.com/login
secondary
https://files.stripe.com/v1/files

What our check can and cannot see

A pass means the service's servers answered with the sign-in refusal they give any request that is not signed in. It does not show that sign-in works or that anything behind the sign-in wall responds.

Host checked: api.stripe.com

RealUptime is not affiliated with Stripe; the name identifies what we checked, 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 passing check there says an API answered, though it still does not show that every feature of the service works for you. Read the full methodology.