We started checking Pleo on November 2, 2026, which is 5 days ago. Everything below covers that period, not the full 90 days a longer-tracked service would show.
Email me when Pleo 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 Pleo's own status page declared. Below it, any public chatter we saw about Pleo 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 Pleo's own status page declared. Three records side by side; none of them changes another.
Our probes, web
Unverified user reportsNo reports about Pleo in the last 24 hours, which is not evidence that nothing is wrong.
Pleo'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 Pleo's own declaration, shown as they made it.
Third-party chatter, labeled
Public posts from the last hour that mention Pleo 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
100.00%
144
US-West
100.00%
115
Europe
100.00%
104
Asia-Pacific
100.00%
63
Their declared record
Pleo's own incident history, taken from their public status feed. This is their account of what happened, not our check reading.
Timeout errors for windows usersMinor incident
Oct 27, 2026, 1:44 PM UTC to Oct 28, 2026, 8:32 AM UTC (18h 48m)resolved
their latest update (Oct 28, 2026, 8:32 AM UTC): The issue was caused by an external provider connected to firewalls.
TPP outage impacting Pleo Open Banking capabilities (PIS and VRP)Partial outage
Oct 20, 2026, 6:10 AM UTC to Oct 20, 2026, 12:45 PM UTC (6h 35m)resolved
their latest update (Oct 20, 2026, 12:45 PM UTC): The incident has been fully addressed. We apologise for any inconvenience caused.
Instant top-up option for SwedenMinor incident
Sep 10, 2026, 12:54 PM UTC to Sep 15, 2026, 3:09 PM UTC (5d 2h)resolved
their latest update (Sep 15, 2026, 3:09 PM UTC): We have found the root cause and instant funding in Sweden should be back to normal. Thank you for your patience
SCA Issues with 3rd PartyMinor incident
Jul 15, 2026, 8:15 AM UTC to Jul 15, 2026, 10:45 AM UTC (2h 30m)resolved
their latest update (Jul 15, 2026, 10:45 AM UTC): SCA traffic has recovered as of 11:00 CEST and transactions are no longer impacted.
Identified: SMS delivery issues affecting some usersMinor incident
May 7, 2026, 8:38 AM UTC to May 14, 2026, 6:48 AM UTC (6d 22h)resolved
their latest update (May 14, 2026, 6:48 AM UTC): Issues have been resolved
Login issues on Pleo web appMajor outage
Apr 20, 2026, 1:30 PM UTC to Apr 20, 2026, 1:47 PM UTC (17 min)resolved
their latest update (Apr 20, 2026, 1:47 PM UTC): The issue has been solved, access to the Pleo web app has been restored.
Customers may experience issues viewing, updating, and seeing card details.Minor incident
Mar 27, 2026, 9:04 AM UTC to Mar 27, 2026, 11:44 AM UTC (2h 41m)resolved
their latest update (Mar 27, 2026, 11:44 AM UTC): The issue impacting card management has been resolved and customers should no longer see errors. We’ll continue to monitor closely.
Issues viewing cards have been resolvedPartial outage
Mar 6, 2026, 8:01 AM UTC to Mar 6, 2026, 9:43 AM UTC (1h 42m)resolved
their latest update (Mar 6, 2026, 9:43 AM UTC): We have resolved the issue that was preventing users from viewing their active cards in the web page. Cards are now displaying correctly for all users. We apologize for the inconvenience caused.
Issues opening the mobile app on Android devicesMinor incident
Feb 24, 2026, 10:07 AM UTC to Feb 24, 2026, 12:03 PM UTC (1h 56m)resolved
their latest update (Feb 24, 2026, 12:03 PM UTC): A fix (v26.9.0) has been released to the Google Play store. We will continue to monitor rollout to ensure affected users are no longer experiencing these issues. We are grateful for your patience during this time and apologise for any inconvenience this may have caused.
Degraded performance of the mobile and web appsMinor incident
Feb 12, 2026, 9:08 AM UTC to Feb 12, 2026, 2:31 PM UTC (5h 23m)resolved
their latest update (Feb 12, 2026, 2:31 PM UTC): We've confirmed that the service degradation is now resolved
Showing the 10 most recent of 25 incidents Pleo has declared in the history we hold.
These entries are Pleo'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.
Pleo'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.