Elevated API Processing Errors
Stripe API users have trouble with elevated processing errors and higher error rates. The error rates are back to normal. Stripe reports that engineers monitor the system and check that the problem is fully resolved.
State
Monitoring
Started
Ongoing for
4 h 3 min
Worst impact
Notice
Timeline
3 updatesInvestigating
55 min 23%
Monitoring
3 h 8 min 77%
Updates
Times in UTCAs posted by Stripe
From 02:34 to 03:01 UTC on November 14th, users experienced elevated Stripe API error rates. Error rates have returned to normal, and our engineers are monitoring and validating that the issue is fully resolved.
We are seeing elevated HTTP processing errors on the Stripe API. Our engineers are engaged and investigating.
We're currently investigating elevated rate limits affecting some merchants. We will post further updates once we have more information.
Affected components
1Stripe in the last 90 days
Full historyIncidents in 90 days
28
Days with an incident
23
Median duration
1 h 43 min
This incident
2.3× the median
Other Stripe incidents
All incidentsStripe·Elevated Instant Payouts failures
From 05:00–14:00 UTC on November 1, 2026, Instant Payouts to cards experienced elevated failure rates due to issuer-bank maintenance affecting payment networks, primarily impacting the US and Canada. This issue is now resolved, and payment processing has returned to normal.
Stripe·Elevated Issuing errors from 17:13 - 20:41 UTC
From 17:15 - 20:41 UTC, Stripe Issuing cards that were created or updated between 17:15–17:54 UTC experienced elevated error rates for API requests. The majority of errors subsided by 19:32 UTC, with full resolution occurring at 20:41 UTC. We have corrected the affected card data, and this issue is now resolved.
Stripe·Elevated Blik errors
From 17:12 to 17:40 UTC on October 24th, there was a partial service disruption of the Blik payment method. Some users may have experienced increased error rates for transactions processed through the Blik payment method. This issue was external to Stripe and is now resolved.
Stripe·Elevated Bancontact errors
From 21:03 to 23:46 UTC on October 22, there was a partial service disruption of the Bancontact payment method. Some users may have experienced increased error rates for transactions processed through the Bancontact payment method. This issue was external to Stripe and is now resolved.
Stripe·Elevated Bancontact errors
From 14:08 - 16:26 UTC there was a partial service disruption of the Bancontact payment method. Users may have experienced increased error rates for transactions processed through the Bancontact payment method. This issue was external to Stripe and is now resolved.
Follow Stripe
Your coding agent knows when Stripe is down, and tells you when a failure is theirs, not yours. You can also get Stripe incidents in a feed reader or in Slack.
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.
Add it as a remote MCP server named "outages" at https://outages.live/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.
Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "stripe" and tell me if Stripe has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.Paste this into any coding agent. It adds the server with its own MCP setup.
https://outages.live/feed.xml?providers=stripe/feed subscribe https://outages.live/feed.xml?providers=stripeFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane