We started checking Adyen on August 20, 2026, which is 79 days ago. Everything below covers that period, not the full 90 days a longer-tracked service would show.
Email me when Adyen reports an incident on its status page, and again when it reports it resolved.
01
The last 24 hours
What happened most recently, on one time axis: our own probe readings by surface, how many people reported a problem, and what Adyen's own status page declared. Below it, any public chatter we saw about Adyen and the extra probe it triggered.
The last 24 hours on one axis: what our probes read for each surface we check, how many people reported a problem, and what Adyen's own status page declared. Three records side by side; none of them changes another.
Our probes, web
Unverified user reportsNo reports about Adyen in the last 24 hours, which is not evidence that nothing is wrong.
Adyen's status pageNo incident declared in the last 24 hours.
24h ago18h ago12h ago6h agonow
Each check cell is the worst reading across every region in that quarter hour: one region that did not answer colours the cell, never an average. An amber cell is a reading that answered, but at three times or more its 7-day median for three checks running: slow is not down, and we say which. A filtered reading stays neutral, because a refused check is not a failed check. Report bars count reports as submitted; we do not check who sent them, and they never change our reading. The status-page lane is Adyen's own declaration, shown as they made it.
Third-party chatter, labeled
Public posts from the last hour that mention Adyen next to an outage word (“down”, “outage”, “not working”). This is what other people said in public, collected by keyword: not something we measured, and not the user reports above. It never affects the verdict.
No matching public posts in the last hour from the sources we watch.
02
Checks passing by region
Checks passing is the checks that passed, divided by every check we attempted, per region. Not interpolated, not smoothed, and never computed for a region with zero recorded samples.
Region
Checks passing
Probes recorded
US-East
99.96%
10999
US-West
99.94%
10892
Europe
99.94%
10782
Asia-Pacific
99.76%
10416
US-Central
100.00%
4604
Canada
99.93%
4605
UK
99.96%
4601
Southeast Asia
99.98%
4571
Australia
99.82%
4564
South America
99.41%
4592
Their declared record
Adyen's own incident history, taken from their public status feed. This is their account of what happened, not our check reading.
Payout delay affecting multiple currenciesAll systems operational
Nov 5, 2026, 11:24 AM UTC to Nov 5, 2026, 11:24 AM UTC (0 min)resolved
their latest update (Nov 5, 2026, 11:24 AM UTC): We have identified and resolved an internal technical issue which started at 08:15 CET on November 5, 2026, resulting in a payout delay for a subset of DKK, SEK, CAD, USD, HUF and PLN transactions. As a result of this issue, a subset of customers may experience a delay in receivi…
MoMo is experiencing higher error ratesAll systems operational
Nov 5, 2026, 2:15 AM UTC to Nov 5, 2026, 4:43 AM UTC (2h 29m)resolved
their latest update (Nov 5, 2026, 4:43 AM UTC): Processing over MoMo is back to normal since 05:22 CET. We will continue monitoring and provide a new update if required.
Intersolve is experiencing higher error ratesAll systems operational
Nov 4, 2026, 5:38 PM UTC to Nov 4, 2026, 7:55 PM UTC (2h 17m)resolved
their latest update (Nov 4, 2026, 7:55 PM UTC): Processing over Intersolve is back to normal since 20:05 CET. We will continue monitoring and provide a new update if required.
Missing or changed payout descriptors for a subset of payoutsOngoing, all systems operational
Nov 4, 2026, 5:34 PM UTC, open for 21h 34m so faridentified
their latest update (Nov 4, 2026, 5:34 PM UTC): We have identified an external issue starting on November 2, 2026, resulting in missing or changed descriptors for a subset of payouts. As a result, a subset of customers may see a payout descriptor that is missing or different from the one configured on their account. Our engine…
Givex is experiencing higher error rates on TESTOngoing, all systems operational
Nov 3, 2026, 4:37 PM UTC, open for 1d 22h so faridentified
their latest update (Nov 3, 2026, 4:37 PM UTC): We have identified an issue outside of our platform resulting in higher error rates for transactions processed through TEST GIVEX starting Nov 1st, 14:00 CET. The transaction processing on LIVE with GIVEX is unaffected. We have contacted GIVEX and we will provide an update as soo…
Swish is experiencing higher refusal ratesAll systems operational
Nov 3, 2026, 1:52 AM UTC to Nov 3, 2026, 4:01 AM UTC (2h 8m)resolved
their latest update (Nov 3, 2026, 4:01 AM UTC): Processing over Swish is back to normal since 03:50 CET. We will continue monitoring and provide a new update if required.
Swish is experiencing higher error ratesAll systems operational
Nov 2, 2026, 11:27 PM UTC to Nov 3, 2026, 12:15 AM UTC (48 min)resolved
their latest update (Nov 3, 2026, 12:15 AM UTC): Processing over Swish is back to normal since 01:00 CET. We will continue monitoring and provide a new update if required.
Partial payout delay for USD payoutsAll systems operational
Nov 2, 2026, 5:03 PM UTC to Nov 2, 2026, 8:36 PM UTC (3h 33m)resolved
their latest update (Nov 2, 2026, 8:36 PM UTC): We can confirm that as of 20:45 CET on November 2, 2026, the issue resulting in a partial payout delay for a subset of USD and EUR transactions, and for a subset of payouts processed through cross-border transfer instruments, has been resolved. EUR instant transfers that failed d…
Partial degradation of Tap to Pay on iPhone on a subset of devices running iOS 27Minor incident
Nov 2, 2026, 4:01 PM UTCidentified
their latest update (Nov 2, 2026, 4:01 PM UTC): We have identified an issue which started on October 2, 2026, affecting Tap to Pay on iPhone on a subset of devices running iOS 27. This issue is resulting in an internal error when the app starts. As a result, affected devices may be unable to process Tap to Pay transactions. Ba…
Capture failures and payout delay for Mastercard transactions in AustraliaAll systems operational
Nov 2, 2026, 3:56 PM UTCidentified
their latest update (Nov 2, 2026, 3:56 PM UTC): We have identified an internal issue starting at 20:00 CET on November 1, 2026, resulting in capture failures for a subset of Mastercard transactions processed in Australia. As a result, customers may see an increase in Capture Failures in reporting and the Customer Area, and som…
Showing the 10 most recent of 63 incidents Adyen has declared in the history we hold.
These entries are Adyen's own declarations, taken from their public status feed, shown separately from our own check readings. Their page publishes what they choose to publish: an incident missing here means they did not declare one, not that nothing happened, and an incident here is their account, not our measurement. Neither record ever changes the other.
Adyen's own status feed works, so its declared incidents are the record and our probe events are not listed or counted. Our check results by region are above, as a reading beside the statement.
Full detail on what a probe does and does not prove is in the methodology page.