outages.live
Live
AdyenIncident ·

Pix is experiencing offer conversion issues

ResolvedOfficial update
0

Adyen reports offer conversion issues with Pix. The problem affects the Payment methods and issuers component. Adyen resolved the issue, which lasted 1 hour and 53 minutes.

State

Resolved

Started

Lasted

1 h 53 min

Worst impact

Notice

Timeline

2 updates
22:5123:2023:4800:1600:45
NoticeUpdate postedTimes in UTC

Identified

1 h 53 min 100%

Updates

Times in UTC

As posted by Adyen

Resolved
Identified

We have been informed of issues with Pix starting at 22:50 CET. This may cause offers to remain open until cancelled. No payment errors are expected as the request is never sent to Adyen. We are in contact with Pix and we will provide an update as soon as it becomes available.

Affected components

1
Payment methods and issuers

Adyen in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

17

Days with an incident

7

Median duration

3 h 38 min

This incident

48% shorter than the median

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

3 days
median 3 h 38 min
90 days agoToday

Other Adyen incidents

All incidents

Adyen·JSC CB PRIVATBANK is experiencing higher refusal rates

Adyen reports higher refusal rates for JSC CB PRIVATBANK on the Payment methods and issuers component. Adyen identified the cause as planned maintenance on the bank's system. The incident is resolved, and it lasted about 4 hours.

Resolved

Adyen·PayU LATAM is experiencing higher error and decline rates

Adyen reports higher error and decline rates for the PayU LATAM payment method in the Payment methods and issuers component. Adyen identified the issue outside its platform and contacted PayU LATAM. The incident is resolved and lasted 13 hours.

Resolved

Adyen·MB WAY is experiencing higher error rates

MB WAY payments had higher error rates on Adyen's Payment methods and issuers component. Adyen reported the incident as resolved after 12 hours and 42 minutes. Adyen stated that the issue was outside its platform.

Resolved

Adyen·Multibanco is experiencing higher error rates

Adyen reports higher error rates for Multibanco payments in the Payment methods and issuers component. Adyen identified the issue outside its platform and contacted Multibanco. The incident is resolved. It lasted from 11:56 UTC to 23:27 UTC.

Resolved

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.

Resolved

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

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

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane