Diners Europe is experiencing higher error rates
Diners Europe payments on the Payment methods and issuers component had higher error rates. Adyen resolved the incident. The outage lasted about 3 hours and 8 minutes.
State
Resolved
Started
Lasted
3 h 8 min
Worst impact
Notice
Timeline
2 updatesIdentified
3 h 8 min 100%
Updates
Times in UTCAs posted by Adyen
We have identified an issue outside of our platform resulting in higher error rates for transactions processed through Diners Europe starting at 04:28 CET. We have contacted Diners Europe and we will provide an update as soon as it becomes available.
Affected components
1Adyen in the last 90 days
Full historyIncidents in 90 days
22
Days with an incident
12
Median duration
3 h 40 min
This incident
About the median
Other Adyen incidents
All incidentsAdyen·Increased timeouts and refusal rate for a subset of Pix refunds
Pix refunds show increased timeouts and refusals for a subset of transactions. The problem affects Payment methods and issuers. Adyen identified the cause and the fix is in progress.
Adyen·GCash Philippines is experiencing offer conversion issues
GCash Philippines offer conversion does not work. The issue affects the Payment methods and issuers component. Adyen reports that the issue is resolved. It lasted about 17 hours and 47 minutes.
Adyen·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.
Adyen·Settlement delay for a subset of SEPA Direct Debit transactions
Adyen reports a settlement delay for a subset of SEPA Direct Debit transactions. The delay affects SEPA Direct Debit transactions processed between November 7 and 9, 2026. Adyen reports that the incident is resolved, and it lasted about 30 hours.
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.
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