PayU LATAM is experiencing higher error and decline rates
Adyen reports higher error and decline rates for the PayU LATAM payment method in Latin America. Adyen identified the problem outside its platform and states that PayU LATAM is unavailable. Adyen is contacting PayU LATAM and will give an update.
State
Identified
Started
Ongoing for
1 h 49 min
Worst impact
Notice
Timeline
1 updateIdentified
1 h 49 min 100%
Updates
Times in UTCAs posted by Adyen
We have identified an issue outside of our platform resulting in unavailability of the PayU LATAM starting at 13:50 CEST. We are contacting PayU LATAM 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
15
Days with an incident
6
Median duration
3 h 28 min
This incident
48% shorter than the median
Other Adyen incidents
All incidentsAdyen·MB WAY is experiencing higher error rates
MB WAY payments have higher error rates in the Payment methods and issuers component. Adyen identified the problem and reports it is outside the Adyen platform. Adyen contacted MB WAY and will give an update when available.
Adyen·Multibanco is experiencing higher error rates
Multibanco payments fail more often on Adyen. The problem affects the Payment methods and issuers component. Adyen identified a problem outside its platform and contacted Multibanco. Adyen will give an update when it is available.
Adyen·MoMo is experiencing higher error rates
MoMo payments through Payment methods and issuers had higher error rates. Adyen identified an issue outside its platform at 02:40 CET. The incident is resolved and lasted 150 minutes.
Adyen·Intersolve is experiencing higher error rates
Adyen reports higher error rates for transactions through Intersolve, which affect the Payment methods and issuers component. Adyen identified the problem outside its platform. The incident is resolved. It lasted 2 hours and 19 minutes.
Adyen·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. Engineering teams are engaged and continue to investigate.
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.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 "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.cc/feed.xml?providers=adyen/feed subscribe https://outages.cc/feed.xml?providers=adyenFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane