Elevated PayNow errors
PayNow payments had elevated errors and this affected the Acquirers and payment methods component. Stripe reports that the problem was external and is now resolved. It lasted from 16:20 to 21:40 UTC.
State
Resolved
Started
Lasted
4 h 38 min
Worst impact
Notice
Timeline
2 updatesInvestigating
4 h 38 min 100%
Updates
Times in UTCAs posted by Stripe
From 16:20-21:40 UTC, we saw elevated errors with the PayNow payment method. The issue was external to Stripe and is now resolved.
As of 17:31 UTC, we've seen elevated errors on PayNow payments. We're continuing to investigate and will post further updates.
Affected components
1Stripe in the last 90 days
Full historyIncidents in 90 days
29
Days with an incident
22
Median duration
2 h 5 min
This incident
2.2× the median
Other Stripe incidents
All incidentsStripe·Elevated API Processing Errors
Stripe API error rates increased. The Stripe API was affected. Stripe reports that the issue is resolved. The increase lasted from 02:34 to 03:01 UTC on November 14th.
Stripe·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.
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