Störungsverlauf von Pleo

1. 27. Oktober 2026 um 13:44 UTCinvestigating

   Einige Windows-Benutzer haben derzeit Anmeldeprobleme, die zu endlosen Loadern führen. Wir untersuchen das Problem

2. 27. Oktober 2026 um 14:27 UTCinvestigating

   Wir sehen einen erhöhten Timeout-Fehler für einige unserer Windows-Benutzer, der endloses Laden verursacht, was möglicherweise durch externe Firewalls von Anbietern in Verbindung mit Cloudflare verursacht wird. Wir untersuchen das Problem

3. 27. Oktober 2026 um 14:54 UTCmonitoring

   Wir sehen, dass die Timeout-Fehler sinken und die Anwendung sollte für die Benutzer wieder normal funktionieren. Das Problem wurde durch einen externen Anbieter verursacht, der die Blockierung bestimmter Firewalls verursachte.

4. 28. Oktober 2026 um 08:32 UTCresolved

   Das Problem wurde durch einen externen Anbieter verursacht, der mit Firewalls verbunden ist.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 20. Oktober 2026 um 14:53 UTCidentified

   TPP-Ausfälle, die Pleo-Fähigkeiten auf die Zahlungsauslösung durch Open Banking Rails auswirken

2. 20. Oktober 2026 um 14:53 UTCinvestigating

   Aktives Engagement mit TPP

3. 20. Oktober 2026 um 14:53 UTCmonitoring

   Einsatz von TPP-Fixen

4. 20. Oktober 2026 um 14:53 UTCresolved

   Der Vorfall wurde vollständig angegangen. Wir entschuldigen uns für jegliche Unannehmlichkeiten.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 10. September 2026 um 12:54 UTCinvestigating

   Wir untersuchen derzeit ein Problem mit sofortiger Finanzierung in Schweden. Bitte verwenden Sie **Standard-Überweisung**, um Ihr Konto ohne Verzögerung aufzuladen. Wir schätzen Ihre Geduld, während wir an einem Fix arbeiten.

2. 15. September 2026 um 11:56 UTCinvestigating

   Wir haben Probleme mit AutoGiro-Kollektionen und automatisierten Aufladeregeln in Schweden. Um Finanzierungsverzögerungen zu vermeiden, füllen Sie bitte mit **standardmäßiger manueller Banküberweisung** auf. Wir arbeiten aktiv daran, dies zu lösen.

3. 15. September 2026 um 15:09 UTCresolved

   Wir haben die Ursache gefunden und sofortige Finanzierung in Schweden sollte wieder normal sein. Vielen Dank für Ihre Geduld

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 15. Juli 2026 um 08:15 UTCinvestigating

   Kunden können während des Wirkungszeitraums intermittierende Transaktionsfehler auftreten. Mastercard-Teams untersuchen dieses Problem aktiv und werden so schnell wie möglich ein Update bereitstellen.

2. 15. Juli 2026 um 09:07 UTCinvestigating

   Wir sehen, dass sich der Traffic für SCA anscheinend erholt hat. Mastercard hat den Vorfall noch nicht als behoben bestätigt, so dass es immer noch zu intermittierenden Transaktionsfehlern kommen kann. Wir verfolgen den Vorfall weiterhin aufmerksam.

3. 15. Juli 2026 um 09:33 UTCmonitoring

   Wir sehen, dass sich der Verkehr für SCA ab 11:00 Uhr erholt hat. Wir beobachten weiterhin, um sicherzustellen, dass der Vorfall behoben wurde.

4. 15. Juli 2026 um 10:45 UTCresolved

   Der SCA-Verkehr hat sich ab 11:00 Uhr erholt und Transaktionen sind nicht mehr betroffen.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 7. Mai 2026 um 08: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. Mai 2026 um 09: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. Mai 2026 um 08: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. Mai 2026 um 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. Mai 2026 um 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. Mai 2026 um 06:48 UTCresolved

   Issues have been resolved

1. 20. April 2026 um 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. April 2026 um 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. April 2026 um 13:47 UTCresolved

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

1. 27. März 2026 um 09:04 UTCinvestigating

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

2. 27. März 2026 um 09: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. März 2026 um 10:00 UTCmonitoring

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

4. 27. März 2026 um 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. März 2026 um 08: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. März 2026 um 09: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. Februar 2026 um 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. Februar 2026 um 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. Februar 2026 um 09:32 UTCinvestigating

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

2. 12. Februar 2026 um 10:51 UTCinvestigating

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

3. 12. Februar 2026 um 11:18 UTCmonitoring

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

4. 12. Februar 2026 um 11:30 UTCmonitoring

   We continue to monitor.

5. 12. Februar 2026 um 14:31 UTCresolved

   We've confirmed that the service degradation is now resolved

1. 5. Februar 2026 um 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. Februar 2026 um 08: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. Februar 2026 um 09:39 UTCresolved

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

1. 5. Februar 2026 um 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. Februar 2026 um 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. Februar 2026 um 13:05 UTCresolved

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

1. 30. Januar 2026 um 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. Januar 2026 um 11:21 UTCmonitoring

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

3. 30. Januar 2026 um 12:38 UTCresolved

   The issue has been resolved

1. 28. Januar 2026 um 15:15 UTCinvestigating

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

2. 29. Januar 2026 um 07:20 UTCresolved

   Reimbursements and Expense Creation are back online

1. 27. Januar 2026 um 07: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. Januar 2026 um 07: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. Januar 2026 um 08:07 UTCidentified

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

4. 27. Januar 2026 um 09:23 UTCmonitoring

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

5. 27. Januar 2026 um 10:11 UTCresolved

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

1. 25. Januar 2026 um 04: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. Januar 2026 um 05:04 UTCmonitoring

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

3. 25. Januar 2026 um 11:38 UTCresolved

   Application is back to normal.

1. 15. Januar 2026 um 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. Januar 2026 um 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. Januar 2026 um 09:26 UTCresolved

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

1. 18. Dezember 2025 um 13:03 UTCidentified

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

2. 18. Dezember 2025 um 13:11 UTCresolved

   This was intended for an internal audience - apologies.

1. 16. Dezember 2025 um 16:02 UTCinvestigating

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

2. 16. Dezember 2025 um 17:39 UTCresolved

   Payment verification (3DS) is now fully available.

1. 5. Dezember 2025 um 09: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. Dezember 2025 um 09: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. Dezember 2025 um 09:41 UTCresolved

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