Intersolve is experiencing higher error rates
Adyen reports higher error rates for transactions through Intersolve. The problem affects Payment methods and issuers. Adyen identified the issue outside its platform and contacted Intersolve.
State
Identified
Started
Ongoing for
2 h 4 min
Worst impact
Notice
Timeline
1 updateIdentified
2 h 4 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 Intersolve starting at 18:15 CET. We have contacted Intersolve 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
11
Days with an incident
4
Median duration
3 h 32 min
This incident
42% shorter than the median
Other Adyen incidents
All incidentsAdyen·Missing or changed payout descriptors for a subset of payouts
Adyen reports missing or changed payout descriptors for a subset of payouts in Settlement and payouts. Adyen identified an external issue that started on November 2, 2026. The engineering teams are engaged and are investigating.
Adyen·Givex is experiencing higher error rates on TEST
Givex transactions on TEST have higher error rates. The problem affects the Payment methods and issuers component. Adyen reports the cause is identified and is outside the Adyen platform. LIVE transactions with Givex are not affected. Adyen contacted Givex and will give an update.
Adyen·Swish is experiencing higher refusal rates
Adyen reports higher refusal rates for Swish transactions on the Payment methods and issuers component. Adyen identified the issue outside its platform and contacted Swish. The incident is resolved and lasted 2 hours and 11 minutes.
Adyen·Swish is experiencing higher error rates
Swish payments fail more often for the Payment methods and issuers component. Adyen reports that the issue is resolved. The outage lasted 51 minutes.
Adyen·Partial payout delay for USD payouts
Adyen reports delayed payouts for a subset of USD and EUR transactions through wire and instant transfers, and for cross-border transfers in all currencies. The problem affects Settlement and payouts. Adyen reports that the incident is resolved. It lasted about 3 hours and 36 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