Stripe is up and responding in 97 ms.
Checked 2 minutes ago · monitored around the clock · stripe.com
24-hour uptime: 100%
Is it Stripe, or is it you? Test your own connection against Stripe — one verdict in 10 seconds.Stripe is up and responding in 97 ms. That reading is from itsnotyou's monitoring servers, 2 minutes ago.
It can be either — that's the hard part. The status on this page is measured from itsnotyou's monitoring servers, so Stripe can look healthy here while your own connection is the real problem. The itsnotyou test checks both at once and returns a single verdict in about 10 seconds.
A slow Stripe usually comes down to one of two things: Stripe's own servers are responding slowly — itsnotyou measures time to first byte, and anything over 1500 ms is flagged as slow — or your local connection is the bottleneck. Running the test tells the two apart.
Stripe is probed every few minutes, around the clock, from itsnotyou's monitoring servers. The verdict and the 24-hour response-time history on this page update automatically.
A decline comes back with a card_error and a decline code such as insufficient_funds or do_not_honor — that is the issuing bank refusing, and Stripe is working perfectly. Only api_error responses and 5xx status codes indicate a problem on Stripe's side.