← Back to Adyen's check readings
We started checking Adyen on August 20, 2026, which is 62 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.
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.
Elevated error rate for transactions processed through VisaAll systems operational
Oct 19, 2026, 12:09 PM UTC to Oct 19, 2026, 12:43 PM UTC (34 min)resolved
their latest update (Oct 19, 2026, 12:43 PM UTC): Processing over Visa is back to normal since 14:12 CEST. We will continue monitoring and provide a new update if required.
Swish is experiencing higher error ratesAll systems operational
Oct 14, 2026, 5:55 PM UTC to Oct 14, 2026, 6:32 PM UTC (38 min)resolved
their latest update (Oct 14, 2026, 6:32 PM UTC): Processing over Swish is back to normal since 20:00 CEST. We will continue monitoring and provide a new update if required.
Twint is experiencing higher error ratesAll systems operational
Oct 13, 2026, 11:21 PM UTC to Oct 14, 2026, 12:10 AM UTC (49 min)resolved
their latest update (Oct 14, 2026, 12:10 AM UTC): Processing over Twint is back to normal since 01:38 CEST. We will continue monitoring and provide a new update if required.
Payout delay for subset of USD transactionsMinor incident
Oct 13, 2026, 7:58 AM UTC to Oct 13, 2026, 9:08 PM UTC (13h 11m)resolved
their latest update (Oct 13, 2026, 9:08 PM UTC): We can confirm that as of 23:07 CEST on October 13, 2026, the issue resulting in a payout delay for a subset of USD transactions processed with regular priority (ACH) has been resolved. 97% of the impacted payouts will be received by the end of the day October 13, 2026. The remai…
Partial delay in processing modification requestsAll systems operational
Oct 12, 2026, 3:30 PM UTC to Oct 12, 2026, 4:14 PM UTC (44 min)resolved
their latest update (Oct 12, 2026, 4:14 PM UTC): We can confirm that as of 18:06 CEST on October 12, 2026 the issue resulting in delays in the processing of modification requests has been resolved. Modification requests, including refunds, captures, and cancellations, are now being processed within expected timeframes. We will …
Swish is experiencing higher error ratesAll systems operational
Oct 9, 2026, 4:48 PM UTC to Oct 9, 2026, 5:38 PM UTC (51 min)resolved
their latest update (Oct 9, 2026, 5:38 PM UTC): Processing over Swish is back to normal since 19:05 CEST. We will continue monitoring and provide a new update if required.
Partial delay in batch processing modification requestsAll systems operational
Oct 7, 2026, 5:25 PM UTC to Oct 7, 2026, 6:11 PM UTC (45 min)resolved
their latest update (Oct 7, 2026, 6:11 PM UTC): We can confirm that as of 19:30 CEST on October 7, 2026, the issue resulting in delays in the processing of batch modification requests has been resolved. Modification requests, including refunds, captures, and cancellations, are now being processed within expected timeframes. We…
Payout delay for a subset of BRL transactionsAll systems operational
Sep 30, 2026, 1:43 PM UTC to Oct 2, 2026, 7:26 PM UTC (2d 5h)resolved
their latest update (Oct 2, 2026, 7:26 PM UTC): We can confirm that as of 19:14 CEST on October 2, 2026, the issue resulting in a partial payout delay for a subset of customers in Brazil has been resolved. All impacted payouts scheduled for September 30, 2026 have now been successfully processed and credited to the respective …
MB WAY is experiencing higher refusal ratesAll systems operational
Sep 30, 2026, 8:09 AM UTC to Sep 30, 2026, 8:21 AM UTC (12 min)resolved
their latest update (Sep 30, 2026, 8:21 AM UTC): Processing over MB WAY is back to normal since 10:08 CEST. We will continue monitoring and provide a new update if required.
GCash Philippines is experiencing offer conversion issuesAll systems operational
Sep 30, 2026, 2:56 AM UTC to Sep 30, 2026, 3:34 AM UTC (38 min)resolved
their latest update (Sep 30, 2026, 3:34 AM UTC): Processing over GCash Philippines is back to normal since 04:55 CEST. We will continue monitoring and provide a new update if required.
Showing the 10 most recent of 34 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.