JSC CB PRIVATBANK is experiencing higher refusal rates
JSC CB PRIVATBANK payments have higher refusal rates. This affects the Payment methods and issuers component. Adyen reports the status as identified. The cause is planned maintenance on the bank system, scheduled for Nov 7, 2026 from 23:00 to 05:00 CET.
State
Identified
Started
Ongoing for
19 min
Worst impact
Notice
Timeline
2 updatesIdentified
19 min 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/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 32 min
This incident
91% shorter than the median
Other Adyen incidents
All incidentsAdyen·Pix is experiencing offer conversion issues
Adyen reports that Pix offer conversion does not work. This problem affects the Payment methods and issuers component. Adyen resolved the incident after 1 hour and 54 minutes.
Adyen·PayU LATAM is experiencing higher error and decline rates
PayU LATAM payments fail or decline at higher rates. This affects the Payment methods and issuers component. Adyen reports that PayU LATAM confirmed an issue, and PayU LATAM technical teams work to resolve it. Adyen continues to monitor the incident.
Adyen·MB WAY is experiencing higher error rates
Adyen reports higher error rates for MB WAY transactions on the Payment methods and issuers component. Adyen identified the issue outside its platform and contacted MB WAY. The incident is resolved. It lasted about 12 hours and 42 minutes.
Adyen·Multibanco is experiencing higher error rates
Multibanco payments had higher error rates. The problem affected the Payment methods and issuers component. Adyen reports that the outage is resolved. It lasted about 11 hours and 31 minutes.
Adyen·MoMo is experiencing higher error rates
MoMo transactions on Adyen have higher error rates. The problem affects Payment methods and issuers. Adyen reports that the incident is resolved after 2 hours and 30 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