PayU LATAM is experiencing higher error rates
PayU LATAM transactions through the Payment methods and issuers component had higher error rates. Adyen reports that the incident is resolved. It lasted 71 minutes.
State
Resolved
Started
Lasted
1 h 11 min
Worst impact
Notice
Timeline
2 updatesIdentified
1 h 11 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 PayU LATAM starting at 23:05 CET. We have contacted 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
26
Days with an incident
15
Median duration
3 h 36 min
This incident
67% shorter than the median
Other Adyen incidents
All incidentsAdyen·MoMo is experiencing higher error rates
We have identified an issue outside of our platform resulting in higher error rates for transactions processed through MoMo starting at 13:53 CET. We have contacted MoMo and we will provide an update as soon as it becomes available.
Adyen·Cartes Bancaires 3D Secure is experiencing higher error rates
Adyen reports higher error rates for Cartes Bancaires 3D Secure authentications. The problem affects Payment methods and issuers. Adyen resolved the incident after 54 minutes.
Adyen·Apple Pay is experiencing unexpected transaction volume fluctuations
Apple Pay transactions are not stable for the Payment methods and issuers component. Adyen reports that the issue is resolved. The incident lasted from 18:32 to 20:48 UTC on 17 November 2026.
Adyen·Increased timeouts and refusal rate for a subset of Pix refunds
Adyen reports increased timeouts and a higher refusal rate for some Pix refunds. The problem affects the Payment methods and issuers component. Adyen resolved this incident, which lasted about 11 hours and 15 minutes.
Adyen·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.
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