Givex is experiencing higher error rates
Adyen reports higher error rates for transactions through Givex. This affects the Payment methods and issuers component. Adyen identified an issue outside of its platform and contacted Givex.
State
Identified
Started
2 h ago
2026-11-01 21:25 UTC
Ongoing for
1 h 31 min
Worst impact
Notice
Timeline
1 updateIdentified
1 h 31 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 16:20 CEST. We have contacted Givex 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
1
Days with an incident
1
Median duration
Not enough data
This incident
Not comparable
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