outages.live
Live
AdyenIncident · 2026-11-02 11:20 UTC

INTERSOLVE is experiencing higher error rates

NoticeOfficial update
0

INTERSOLVE transactions through Payment methods and issuers have higher error rates. Adyen identified the problem outside the Adyen platform. The issue started at 09:00 CET.

State

Identified

Started

1 h ago

2026-11-02 11:20 UTC

Ongoing for

1 h 29 min

Worst impact

Notice

Timeline

1 update
11:2011:4212:0512:2712:49
NoticeUpdate postedTimes in UTC

Identified

1 h 29 min 100%

Updates

Times in UTC

As posted by Adyen

Identified2026-11-02 11:21 UTC

We have identified an issue outside of our platform resulting in higher error rates for transactions processed through INTERSOLVE with pluxee starting at 09:00 CET.

Affected components

1
Payment methods and issuers

Adyen in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

2

Days with an incident

2

Median duration

3 h 40 min

This incident

59% shorter than the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

3 h 40 min
median 3 h 40 min
90 days agoToday

Other Adyen incidents

All incidents

Adyen·Givex is experiencing higher error rates

Adyen reports higher error rates for transactions processed through Givex on the Payment methods and issuers component. Adyen identified the problem outside its platform and contacted Givex. The incident is resolved and lasted 3 hours and 41 minutes.

Resolvedresolved 12 h ago

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.

Prompt
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.

RSS
https://outages.live/feed.xml?providers=adyen
Slack
/feed subscribe https://outages.live/feed.xml?providers=adyen

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane