Pleo Outage History
28 incidents recorded over the last 365 days, 28 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded Pleo Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Oct 27, 2026 | Timeout errors for windows usersThe issue was caused by an external provider connected to firewalls. | 18h 48m | Resolved |
| Oct 20, 2026 | TPP outage impacting Pleo Open Banking capabilities (PIS and VRP)The incident has been fully addressed. We apologise for any inconvenience caused. | -128 min | Resolved |
| Oct 18, 2026 | Scheduled Platform MaintenanceMaintenance has started | 6h 2m | Resolved |
| Sep 10, 2026 | Instant top-up option for SwedenWe have found the root cause and instant funding in Sweden should be back to normal. Thank you for your patience | 122h 14m | Resolved |
| Jul 15, 2026 | SCA Issues with 3rd PartySCA traffic has recovered as of 11:00 CEST and transactions are no longer impacted. | 2h 30m | Resolved |
| May 7, 2026 | Identified: SMS delivery issues affecting some usersIssues have been resolved | 166h 10m | Resolved |
| Apr 20, 2026 | Login issues on Pleo web appThe issue has been solved, access to the Pleo web app has been restored. | 17 min | Resolved |
| Mar 27, 2026 | Customers may experience issues viewing, updating, and seeing card details.The issue impacting card management has been resolved and customers should no longer see errors. We’ll continue to monitor closely. | 2h 40m | Resolved |
| Mar 6, 2026 | Issues viewing cards have been resolvedWe 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. | 1h 41m | Resolved |
| Feb 24, 2026 | Issues opening the mobile app on Android devicesA 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… | 1h 55m | Resolved |
| Feb 12, 2026 | Degraded performance of the mobile and web appsWe've confirmed that the service degradation is now resolved | 5h 22m | Resolved |
| Feb 5, 2026 | Investigating issues with Accounting System ExportsWe have solved this issue for our customers, please get in contact if you continue to see an issue. | 162h 29m | Resolved |
| Feb 5, 2026 | Mobile app is not loading user dataWe identified and resolved an issue affecting our mobile app where user data was not loading properly after login. | 39 min | Resolved |
| Jan 30, 2026 | Invoices page not loading for some customersThe issue has been resolved | 1h 56m | Resolved |
| Jan 28, 2026 | Reimbursement Processing Issue (Delays/Failures)Reimbursements and Expense Creation are back online | 16h 4m | Resolved |
| Jan 27, 2026 | Login and cards in web and mobile applications is functional againAfter monitoring we are seeing authentication flows working as normal again, closing this incident. | 2h 28m | Resolved |
| Jan 25, 2026 | Application Performance IssuesApplication is back to normal. | 7h 9m | Resolved |
| Jan 15, 2026 | Privacy Plugin blocking esential services on the web applicationWe're working on a long-term solution in the background | 282h 49m | Resolved |
| Dec 18, 2025 | PR created to listen to the correct serviceThis was intended for an internal audience - apologies. | 8 min | Resolved |
| Dec 16, 2025 | Card Payments IssuesPayment verification (3DS) is now fully available. | 1h 36m | Resolved |
| Dec 5, 2025 | Chat and phone calls not working due to upstream providerUpstream issues have been fixed and chat and calls should work as normal. | 18 min | Resolved |
| Dec 2, 2025 | Sporadic errors across the platform related to user managementWe have deployed the mitigations identified. | 2h 53m | Resolved |
| Dec 1, 2025 | Some users had trouble logging in, or experienced degraded performanceWe have no on-going reports of problems and our internal monitoring is all green | 44 min | Resolved |
| Nov 27, 2025 | Issues submitting out‑of‑pocket expensesWe believe our customers no longer see this issue and have successfully adopted the new app version | 95h 17m | Resolved |
| Nov 25, 2025 | Issues submissing out-of-pocket expensesWe have released a new version of the mobile app that fixes this problem, if you have an issue creating or tagging an expense, please update your app, as a first action. | 3h 34m | Resolved |
| Nov 20, 2025 | Delay in card spends appearing in appWe have seen no further issues | 1h 14m | Resolved |
| Nov 18, 2025 | Pleo experiencing login and other issuesThe issues on our upstream providers’ side have been fully resolved, and all Pleo services are running smoothly again. We are actively assessing additional measures to increase resilience against similar situations in… | 9h 47m | Resolved |
| Nov 6, 2025 | Degradation of experience in processing of invoicesThe **Invoice Processing** component is now fully **Operational**. We have successfully restored and rolled out the primary API, and all systems are functioning normally. All invoices have been processed, and… | 24h 43m | Resolved |
Hear about the next one while it is open
Everything above is a record written after the fact. We can email you when the next Pleo incident opens instead, at the point where knowing still changes what you do.
Free, no password, no card. Unsubscribe in one click.
How to Read This Pleo Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Pleo acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single Pleo outage in this window ran 11d 18h, against a mean recovery of 1d 10h. If you depend on Pleo in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.