Delay in processing of modifications
Adyen reports a delay in the processing of modifications, such as refunds, captures and cancellations, in the Payments component. Adyen identified the issue and resolved it. The outage lasted 39 minutes.
State
Resolved
Started
Lasted
39 min
Worst impact
Degraded
Timeline
2 updatesIdentified
39 min 100%
Updates
Times in UTCAs posted by Adyen
We have identified an issue resulting in a delay in the processing of modifications (such as refunds, captures and cancellations) as of 23:18 CET. Our engineering team is engaged in resolving this issue. We will provide an update as soon as we have more information.
Affected components
1Adyen in the last 90 days
Full historyIncidents in 90 days
19
Days with an incident
11
Median duration
3 h 38 min
This incident
82% shorter than the median
Other Adyen incidents
All incidentsAdyen·Settlement delay for a subset of SEPA Direct Debit transactions
Adyen reports a delay in settlement for some SEPA Direct Debit transactions. The affected transactions were processed between November 7 and 9, 2026, and the Settlement and payouts component is affected. Adyen identified the issue and expects the delayed settlements to complete by the end of the day CET on November 11, 2026.
Adyen·JSC CB PRIVATBANK is experiencing higher refusal rates
Adyen reports higher refusal rates for JSC CB PRIVATBANK payments. Payment methods and issuers are affected. Adyen identified the issue outside its platform. The incident is resolved. The outage lasted 4 hours and 1 minute.
Adyen·Pix is experiencing offer conversion issues
Adyen reports that Pix offer conversion does not work. This problem affects the Payment methods and issuers component. Adyen resolved the incident after 1 hour and 54 minutes.
Adyen·PayU LATAM is experiencing higher error and decline rates
Adyen reports that PayU LATAM payment methods and issuers have higher error and decline rates. Adyen later confirmed that PayU LATAM resolved the issue. The outage lasted about 13 hours.
Adyen·MB WAY is experiencing higher error rates
Adyen reports higher error rates for MB WAY transactions on the Payment methods and issuers component. Adyen identified the issue outside its platform and contacted MB WAY. The incident is resolved. It lasted about 12 hours and 42 minutes.
Follow Adyen
Your coding agent knows when Adyen is down, and tells you when a failure is theirs, not yours. You can also get Adyen 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 "adyen" and tell me if Adyen 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=adyen/feed subscribe https://outages.live/feed.xml?providers=adyenFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane