Givex is experiencing higher error rates
Givex has higher error rates for transactions through the Payment methods and issuers component. Adyen identified the cause as an issue outside its platform. The incident started at 06:30 CET, and Adyen will give an update when one is available.
State
Identified
Started
Ongoing for
1 h 4 min
Worst impact
Notice
Timeline
1 updateIdentified
1 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 Givex starting at 06:30 CET. We will provide an update as soon as it becomes available.
Affected components
1Adyen in the last 90 days
Full historyIncidents in 90 days
34
Days with an incident
19
Median duration
3 h 28 min
This incident
69% shorter than the median
Other Adyen incidents
All incidentsAdyen·Intersolve is experiencing higher error rates
Adyen reports higher error rates for payment methods and issuers through Intersolve. Adyen identified an issue outside its platform and contacted Intersolve. The incident is resolved and lasted about 2 hours 53 minutes.
Adyen·Intersolve is experiencing higher error rates
Intersolve payment methods and issuers had higher transaction error rates on Adyen. Adyen identified the issue outside its platform. The incident is resolved and lasted about 13 hours.
Adyen·Multibanco is experiencing higher error rates
Multibanco payments have higher error rates. This affects the Payment methods and issuers component. Adyen reports that the issue is resolved and lasted 2 hours and 56 minutes.
Adyen·Cellulant is experiencing offer conversion issues
Cellulant offer conversion does not work for the Payment methods and issuers component. Adyen reports that the incident is resolved and lasted about 5 hours and 6 minutes.
Adyen·PayU LATAM is experiencing higher error rates
Adyen reports higher error rates for transactions processed through PayU LATAM. The Payment methods and issuers component is affected. The incident is resolved. It lasted 53 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