Stripe reported "Elevated Amazon Pay errors" on its status page at 2026-10-15 02:06 UTC.

Stripe lists these components: Global payments, Acquirers and payment methods.

When did the incident start and end?

It started at 2026-10-15 02:06 UTC and ended at 2026-10-15 02:18 UTC. It lasted 12 min.

How do I get alerts for Stripe?

Subscribe to the Stripe live feed over RSS or in Slack, or add the outages.live MCP server to your coding agent.

Where does this information come from?

From the official status page of Stripe. outages.live reads it every few minutes and keeps every update.

StripeIncident · 2026-10-15 02:06 UTC

Elevated Amazon Pay errors

ResolvedOfficial update

From 01:30–01:56 UTC, we saw elevated error rates on Amazon Pay payments due to issues with an upstream payment processor. This is now resolved.

The latest update from Stripe.

State

Resolved

Started

18 d ago

2026-10-15 02:06 UTC

Lasted

12 min

until 2026-10-15 02:18 UTC

Worst impact

Notice

Timeline

2 updates

02:0602:0902:1202:1502:18

NoticeUpdate postedTimes in UTC

Investigating

12 min 100%

Updates

Times in UTC

As posted by Stripe

Resolved2026-10-15 02:18 UTC

From 01:30–01:56 UTC, we saw elevated error rates on Amazon Pay payments due to issues with an upstream payment processor. This is now resolved.

Investigating2026-10-15 02:06 UTC

We're currently investigating elevated error rates and response times with Amazon Pay payments. We'll post an update soon.

Affected components

Global paymentsAcquirers and payment methods

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.

Prompt

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.

RSS

https://outages.cc/feed.xml?providers=stripe

Slack

/feed subscribe https://outages.cc/feed.xml?providers=stripe

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane