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-10-14 04:50 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 Oct 14, 2026, 4:52 AM 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 Oct 14, 2026, 4:52 AM UTC
US-East142 msChecks passing
US-West161 msChecks passing
Europe94 msChecks passing
Asia-Pacific101 msChecks passing
US-Central186 msChecks passing
Canada293 msChecks passing
UK60 msChecks passing
Southeast Asia261 msChecks passing
Australia176 msChecks passing
South America572 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
280msp95 · 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-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 283ms2026-10-06 UTC: p95 370ms2026-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 280ms
Sep 15Sep 29Oct 14
US-West
568msp95 · 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-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 760ms2026-10-06 UTC: p95 596ms2026-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 568ms
Sep 15Sep 29Oct 14
Europe
170msp95 · 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-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 232ms2026-10-06 UTC: p95 243ms2026-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 170ms
Sep 15Sep 29Oct 14
Asia-Pacific
397msp95 · 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-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 416ms2026-10-06 UTC: p95 408ms2026-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 397ms
Sep 15Sep 29Oct 14
US-Central
551msp95 · 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-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.1s2026-10-06 UTC: p95 647ms2026-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 551ms
Sep 15Sep 29Oct 14
Canada
491msp95 · 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-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.2s2026-10-06 UTC: p95 781ms2026-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 491ms
Sep 15Sep 29Oct 14
UK
201msp95 · 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-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 242ms2026-10-06 UTC: p95 247ms2026-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 201ms
Sep 15Sep 29Oct 14
Southeast Asia
600msp95 · 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-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 702ms2026-10-06 UTC: p95 623ms2026-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 600ms
Sep 15Sep 29Oct 14
Australia
815msp95 · 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-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 878ms2026-10-06 UTC: p95 1.0s2026-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 815ms
Sep 15Sep 29Oct 14
South America
804msp95 · 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-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.0s2026-10-06 UTC: p95 1.0s2026-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 804ms
Sep 15Sep 29Oct 14

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

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: 142msstatus code: 401checked: Oct 14, 2026, 4:51 AM 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: 161msstatus code: 401checked: Oct 14, 2026, 4:51 AM 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: 186msstatus code: 401checked: Oct 14, 2026, 4:50 AM 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: 293msstatus code: 401checked: Oct 14, 2026, 4:48 AM 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: 572msstatus code: 401checked: Oct 14, 2026, 4:50 AM 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: 94msstatus code: 401checked: Oct 14, 2026, 4:51 AM 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: 60msstatus code: 401checked: Oct 14, 2026, 4:49 AM 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: 101msstatus code: 401checked: Oct 14, 2026, 4:51 AM 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: 261msstatus code: 401checked: Oct 14, 2026, 4:52 AM 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: 176msstatus code: 401checked: Oct 14, 2026, 4:52 AM 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 Swish errors, 6h 33mdeclared on their status page2026-10-06
Elevated API errors, 25mdeclared on their status page2026-10-01
Visa authorization errors, 1h 39mdeclared on their status page2026-09-30
Elevated API Errors, 19mdeclared on their status page2026-09-27
Elevated Klarna errors, 1h 19mdeclared on their status page2026-09-25
Elevated API errors, 33mdeclared on their status page2026-09-23
API call success rate drop, 2h 15mdeclared on their status page2026-09-22
Stripe Support Systems issue, 39mdeclared on their status page2026-09-20

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

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"></a>

The badge shows the share of our checks that passed 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 and shows no color. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.

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.

Checking a site of your own? The free website down checker sends it one request and reports the answer, and the SLA calculator shows how much downtime an uptime figure allows.

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

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.