StatOSS

Stripe API uptime

Stripe API, checked by StatOSS every 5 minutes from Helsinki in Finland, Falkenstein in Germany, Copenhagen in Denmark, Ashburn in the USA, Singapore and Sydney in Australia. Measured from outside, with every outage dated in UTC.

api.stripe.com/v1/chargesEvery 5 minutes

Stripe API is up.

Up for 51 d 10 h. Last checked 2026-11-20 18:55 UTC from Falkenstein, Germany: 401 in 88 ms.

Last 24 hours

Up for 51 d 10 h100% passed

288 checks, median 89 ms from Falkenstein, all passed

95% under 95 ms

Response time by region
EuropeEurope89 ms
N. AmericaNorth America34 ms
AsiaAsia95 ms
OceaniaOceania34 ms

Medians over this range, on one scale up to 200 ms.

Last 90 days

Up for 51 d 10 h100% passed

14,805 checks, median 92 ms from Falkenstein, all passed

95% under 158 ms

Response time by region
EuropeEurope92 ms
N. AmericaNorth America75 ms
AsiaAsia99 ms
OceaniaOceania59 ms

Medians over this range, on one scale up to 200 ms. Europe's places are scaled to Falkenstein, its fastest shared place.

Each bar of the first strip is one check, five minutes apart; each bar of the second is a day. Height is response time, red is a failed check, amber a timeout. Times are UTC, as of 2026-11-20 18:56 UTC.

In the last 30 days Stripe API passed 8,863 of 8,863 checks, 100%.

No outage since checks began on 30 Sep 2026.

Availability

The share of checks that passed, and the outages that began, in each window up to now.

LastPassedChecksOutages
24 hours100%288 of 2880
7 days100%2,015 of 2,0150
30 days100%8,863 of 8,8630
90 daysNot enough history yet: checks began on 30 Sep 2026

A year of checks is kept; the year's figure appears here once there is a year of them.

Response time by location

Over the last 7 days, from the checks that passed: the time from the start of the request to the answer's headers, with the DNS lookup, the connection and TLS included.

FromMedian95th percentileMeanChecks
Falkenstein, Germany90 ms96 ms90 ms420
Helsinki, Finland131 ms137 ms132 ms43
Ashburn, USA39 ms143 ms60 ms503
Copenhagen, Denmark99 ms123 ms103 ms42
Singapore89 ms272 ms120 ms504
Sydney, Australia42 ms198 ms73 ms504

Outages

None detected since checks began on 30 Sep 2026.

What is checked

Online payments, subscriptions and invoices, used by a large share of the web's checkouts.

StatOSS sends GET https://api.stripe.com/v1/charges and counts the check as passed on status 401 within 10 seconds. The API's charges endpoint, on api.stripe.com, where every server-side Stripe call goes. Without a key it answers 401 and asks for one.

Checkout pages, the dashboard and webhook deliveries to you are separate, and are not checked.

Stripe API reports its own incidents at status.stripe.com. The figures here are measured from outside and can differ from it in both directions.

How it is measured

  • One check every 5 minutes, from one location at a time in turn: Helsinki in Finland, Falkenstein in Germany, Copenhagen in Denmark, Ashburn in the USA, Singapore and Sydney in Australia.
  • A check fails when no answer comes within 10 seconds, when the connection or TLS fails, or when the answer is not status 401.
  • A failed check is repeated at once from a second location, and counts only when that location fails too, or cannot answer within 20 seconds.
  • Two failed checks in a row make an outage, dated from the second, and the first check that passes ends it. A failure shorter than 10 minutes may not make one, and times are good to about 5 minutes.
  • Availability is the share of checks that passed. There are no maintenance windows: every check counts.

It is the same check a StatOSS status page runs for its owner, with the same rules; the docs on checks have the details.