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.
State
Resolved
Started
Lasted
4 h
Worst impact
Notice
Timeline
4 updatesIdentified
4 h 100%
Updates
Times in UTCAs posted by Adyen
We have identified an issue outside of our platform resulting in higher refusal rates due to a planned maintenance on their system. Their maintenance work is scheduled for Nov 7th, 2026 from 23:00 to 05:00 CET Their official announcement can be found on their press blog https://privatbank.ua/en and widely in UA media.
We have identified an issue outside of our platform resulting in higher refusal rates due to a planned maintenance on their system. Their maintenance work is scheduled for Nov 7th, 2026 from 23:00 to 05:00 CET Their official announcement can be found on their press blog https://privatbank.ua/and widely in UA media.
We have identified an issue outside of our platform resulting in higher refusal rates due to a planned maintenance on their system. Their maintenance work is scheduled for Nov 7th, 2026 from 23:00 to 05:00 CET Their official announcement can be found on their press blog https://privatbank.ua/en/news and widely in UA media.
Affected components
1Adyen in the last 90 days
Full historyIncidents in 90 days
17
Days with an incident
7
Median duration
3 h 38 min
This incident
About the median
Other Adyen incidents
All incidentsAdyen·Pix is experiencing offer conversion issues
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.
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.
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.
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.
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.
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