Historial de interrupciones de Pleo

1. 15 de julio de 2026 a las 8:15 UTCinvestigating

   Los clientes pueden experimentar fallos de transacción intermitentes durante el período de impacto. Los equipos de Mastercard están investigando activamente esta cuestión y proporcionarán una actualización lo antes posible.

2. 15 de julio de 2026 a las 9:07 UTCinvestigating

   Estamos viendo que el tráfico para SCA parece haberse recuperado. Mastercard todavía no ha confirmado el incidente como resuelto, por lo que puede experimentar fallos de transacción intermitentes. Seguimos vigilando de cerca el incidente.

3. 15 de julio de 2026 a las 9:33 UTCmonitoring

   Estamos viendo que el tráfico para SCA se ha recuperado a partir de las 11:00 CEST. Seguimos vigilando para asegurar que se haya resuelto el incidente.

4. 15 de julio de 2026 a las 10:45 UTCresolved

   El tráfico SCA se ha recuperado a partir de las 11:00 CEST y las transacciones ya no están impactadas.

Traducido automáticamente desde la actualización oficial del incidente.

1. 7 de mayo de 2026 a las 8:38 UTCinvestigating

   We are currently investigating reports of SMS messages not being delivered to some users. This may affect actions that require SMS verification, including:  - Viewing cards  - Creating new cards  - Onboarding new users  Our team is actively investigating the root cause. We will provide an update as soon as we have more information.

2. 7 de mayo de 2026 a las 9:17 UTCinvestigating

   **Investigating: SMS Delivery Issues** We are currently investigating reports of SMS messages not being delivered to some users. This may affect actions that require SMS verification, including: - Viewing cards - Creating new cards - Onboarding new users Our team is actively investigating the root cause. We will provide an update as soon as we have more information.

3. 8 de mayo de 2026 a las 8:06 UTCidentified

   We have confirmed that our SMS provider is experiencing degraded service which prevents some users from getting SMS codes and they are actively trying to resolve this. We are monitoring the situation closely. As a workaround for affected users we suggest they follow this guide ([https://help.pleo.io/en/support/solutions/articles/103000284452-reset-authentication-method](https://help.pleo.io/en/support/solutions/articles/103000284452-reset-authentication-method "https://help.pleo.io/en/support/solutions/articles/103000284452-reset-authentication-method")) to change their authentication method to an authenticator app.

4. 11 de mayo de 2026 a las 11:25 UTCidentified

   We are experiencing an issue with our SMS provider, which prevents customers in Sweden, Denmark and Norway from receiving SMS messages. This is being worked on with the highest priority. In the meantime for affected customers the recommendation is to switch to TOTP with an authenticator app as outlined by this article ([https://help.pleo.io/en/support/solutions/articles/103000284452-reset-authentication-method](https://help.pleo.io/en/support/solutions/articles/103000284452-reset-authentication-method "https://help.pleo.io/en/support/solutions/articles/103000284452-reset-authentication-method"))

5. 12 de mayo de 2026 a las 11:28 UTCidentified

   SMS verification is unavailable in Sweden, Norway and Italy. Switch to TOTP via an authenticator app. Mobile users: update and restart the app. [Learn how](https://help.pleo.io/en/support/solutions/articles/103000284452-reset-authentication-method "Learn how") (link to article)

6. 14 de mayo de 2026 a las 6:48 UTCresolved

   Issues have been resolved

1. 20 de abril de 2026 a las 13:33 UTCinvestigating

   We are currently experiencing an issue preventing users from logging in to the Pleo web app. Our team is working with the highest priority to resolve this.

2. 20 de abril de 2026 a las 13:36 UTCinvestigating

   We are currently experiencing an issue preventing users from logging in to the Pleo web app. Our team is working with the highest priority to resolve this. Customers should still be able to access the mobile app.

3. 20 de abril de 2026 a las 13:47 UTCresolved

   The issue has been solved, access to the Pleo web app has been restored.

1. 27 de marzo de 2026 a las 9:04 UTCinvestigating

   We are seeing degraded performance related to card management and are investigating the issue.

2. 27 de marzo de 2026 a las 9:38 UTCinvestigating

   We’re analysing the degraded performance in card management and are investigating with high priority. We’ll share updates as soon as we have more information.

3. 27 de marzo de 2026 a las 10:00 UTCmonitoring

   We’ve stabilised our core systems, and we’re continuing to monitor closely.

4. 27 de marzo de 2026 a las 11:44 UTCresolved

   The issue impacting card management has been resolved and customers should no longer see errors. We’ll continue to monitor closely.

1. 6 de marzo de 2026 a las 8:01 UTCidentified

   An issue is preventing some users from seeing their cards details and activating cards in the Pleo web app. Users can access card functionality in the mobile app. Our team is actively investigating and working on a fix.

2. 6 de marzo de 2026 a las 9:43 UTCresolved

   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.

1. 24 de febrero de 2026 a las 10:07 UTCinvestigating

   We have identified a small issue whereby some Android device users on the latest version of the mobile app may have difficulties opening it.

2. 24 de febrero de 2026 a las 12:03 UTCresolved

   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.

1. 12 de febrero de 2026 a las 9:32 UTCinvestigating

   We're currently investigating degraded performance in the mobile and web apps.

2. 12 de febrero de 2026 a las 10:51 UTCinvestigating

   Some online card transaction verifications may fail (3D-Secure). We are looking into this as a priority.

3. 12 de febrero de 2026 a las 11:18 UTCmonitoring

   We’ve applied changes to address the issue, and performance has improved. We remain attentive to the situation.

4. 12 de febrero de 2026 a las 11:30 UTCmonitoring

   We continue to monitor.

5. 12 de febrero de 2026 a las 14:31 UTCresolved

   We've confirmed that the service degradation is now resolved

1. 5 de febrero de 2026 a las 15:10 UTCinvestigating

   We are currently investigating an issue affecting expense exports to external accounting systems. Users may encounter errors when attempting to sync transactions.

2. 6 de febrero de 2026 a las 8:05 UTCmonitoring

   We have rolled out a fix the errors users encountered when exporting to external systems. We will continue to closely monitor the area.

3. 12 de febrero de 2026 a las 9:39 UTCresolved

   We have solved this issue for our customers, please get in contact if you continue to see an issue.

1. 5 de febrero de 2026 a las 12:26 UTCinvestigating

   We are currently investigating an issue affecting our mobile app where user data is not loading properly after login. Users may experience empty or partially loaded screens, with limited access to features such as card details, expenses, and profile information.

2. 5 de febrero de 2026 a las 12:45 UTCmonitoring

   We identified and resolved an issue affecting our mobile app where user data was not loading properly after login. We are now monitoring the situation to confirm the fix is working for all users.

3. 5 de febrero de 2026 a las 13:05 UTCresolved

   We identified and resolved an issue affecting our mobile app where user data was not loading properly after login.

1. 30 de enero de 2026 a las 10:42 UTCidentified

   Some customers are unable to access the Invoices page. We have identified the issue and are working on a fix.

2. 30 de enero de 2026 a las 11:21 UTCmonitoring

   We believe the issue is resolved, but are continuing to monitor the situation.

3. 30 de enero de 2026 a las 12:38 UTCresolved

   The issue has been resolved

1. 28 de enero de 2026 a las 15:15 UTCinvestigating

   We’re currently experiencing an issue affecting reimbursements. Some requests may be delayed or not processed as expected

2. 29 de enero de 2026 a las 7:20 UTCresolved

   Reimbursements and Expense Creation are back online

1. 27 de enero de 2026 a las 7:43 UTCidentified

   We are currently experiencing issues with sending SMS. During resolution users may experience problems logging in, or viewing card and payment details. Please bear with us while we resolve them

2. 27 de enero de 2026 a las 7:58 UTCidentified

   We are currently experiencing issues with sending SMS. During resolution users may experience problems logging in or viewing card and payment details for both the web and mobile app. Please bear with us while we resolve them.

3. 27 de enero de 2026 a las 8:07 UTCidentified

   We're fixing a technical issue affecting the Web and Mobile apps. No data or funds are at risk.

4. 27 de enero de 2026 a las 9:23 UTCmonitoring

   We resolved an issue that impacted login and using cards that should now be functional again

5. 27 de enero de 2026 a las 10:11 UTCresolved

   After monitoring we are seeing authentication flows working as normal again, closing this incident.

1. 25 de enero de 2026 a las 4:29 UTCinvestigating

   We're experiencing slower than normal performance on both our web and mobile applications following scheduled database maintenance. Users may notice delays when loading pages, accessing expense details, or using various app features. Our engineering team is actively working to restore normal performance

2. 25 de enero de 2026 a las 5:04 UTCmonitoring

   We have identified and fixed the issue. The application is back to normal now

3. 25 de enero de 2026 a las 11:38 UTCresolved

   Application is back to normal.

1. 15 de enero de 2026 a las 14:36 UTCidentified

   We have identified that privacy plugins, specifically Privacy Badger, block some of the services we rely on since their last release. We're working on a more long-term solution, but there is a temporary workaround customers can use by whitelisting our pleo domain `[pleo.io](http://pleo.io/)` in this (or similar) privacy plugin.

2. 15 de enero de 2026 a las 14:46 UTCmonitoring

   We're looking at implementing a more long-term solution. This seems to only affect a small subset of customer using these privacy plugins. With whitelisting pleo.io in the privacy plugin, the app should be functional until the long-term solution is in place.

3. 27 de enero de 2026 a las 9:26 UTCresolved

   We're working on a long-term solution in the background

1. 18 de diciembre de 2025 a las 13:03 UTCidentified

   Identified that the executor service was not listening to the Kafka Topic

2. 18 de diciembre de 2025 a las 13:11 UTCresolved

   This was intended for an internal audience - apologies.

1. 16 de diciembre de 2025 a las 16:02 UTCinvestigating

   Payment verification (3DS) is temporarily unavailable, which may cause some card payments to fail. We’re investigating.

2. 16 de diciembre de 2025 a las 17:39 UTCresolved

   Payment verification (3DS) is now fully available.

1. 5 de diciembre de 2025 a las 9:23 UTCinvestigating

   An upstream provider is having issues this morning and you may not be able to reach us on chat. A fix is in progress and you should be able to chat to us shortly.

2. 5 de diciembre de 2025 a las 9:32 UTCmonitoring

   An upstream provider is having issues this morning and you may not be able to reach us by chat or phone. A fix is in progress and you should be able to reach us shortly.

3. 5 de diciembre de 2025 a las 9:41 UTCresolved

   Upstream issues have been fixed and chat and calls should work as normal.

1. 2 de diciembre de 2025 a las 11:24 UTCinvestigating

   We have identified sporadic error spikes cross the platform related to user management. This has a cascading effect for various areas and could cause problems to validate incoming card-transactions.

2. 2 de diciembre de 2025 a las 13:17 UTCidentified

   We have identified the source of the problem and working on fixes to mitigate.

3. 2 de diciembre de 2025 a las 14:18 UTCresolved

   We have deployed the mitigations identified.

1. 1 de diciembre de 2025 a las 10:39 UTCinvestigating

   We’re investigating an issue causing slower performance in the Pleo web and mobile apps. If you’re affected, please try again in 15 minutes. We’ll post updates on [status.pleo.io](http://status.pleo.io "status.pleo.io").

2. 1 de diciembre de 2025 a las 10:58 UTCmonitoring

   We have identified the issue and have rolled out a fix

3. 1 de diciembre de 2025 a las 11:23 UTCresolved

   We fixed a backend service issue that caused some users to have trouble logging in, or experience degraded performance.

4. 1 de diciembre de 2025 a las 13:09 UTCmonitoring

   We’re recovering from an app performance issue and you may see intermittent performance degradation. If something fails or appears slow, please retry. We’re monitoring closely and will post updates here.

5. 1 de diciembre de 2025 a las 13:35 UTCmonitoring

   We have no on-going reports of problems

6. 1 de diciembre de 2025 a las 13:39 UTCresolved

   We have no on-going reports of problems and our internal monitoring is all green

1. 27 de noviembre de 2025 a las 11:42 UTCmonitoring

   Some customers on mobile are having trouble creating out‑of‑pocket expenses. We’ve released a fix. Please restart the Pleo app or update to the latest version from your app store.

2. 1 de diciembre de 2025 a las 11:00 UTCresolved

   We believe our customers no longer see this issue and have successfully adopted the new app version