Elevated API Errors
From 00:32 UTC to 01:01 UTC, we saw elevated API errors. This issue is now resolved.
The latest update from Stripe.
State
Resolved
Started
36 d ago
2026-09-27 01:03 UTC
Lasted
19 min
until 2026-09-27 01:21 UTC
Worst impact
Partial outage
Timeline
2 updatesInvestigating
19 min 100%
Updates
Times in UTCAs posted by Stripe
From 00:32 UTC to 01:01 UTC, we saw elevated API errors. This issue is now resolved.
Starting 00:32 UTC, we’ve seen elevated failures with the API. We’re investigating and will post an update as soon as possible.
Affected components
2Follow 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.cc/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.cc/feed.xml?providers=stripe/feed subscribe https://outages.cc/feed.xml?providers=stripeFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane