Störungsverlauf von Apaleo

1. 27. August 2026 um 13:30 UTCinvestigating

   Wir untersuchen derzeit ein Problem, das unsere Plattform betrifft.

2. 27. August 2026 um 13:56 UTCidentified

   Die Ursache wurde als eine API-Nutzung identifiziert, die das Datenbanksystem stark belastet. Die Systeme sehen normal aus. Wir werden weiter beobachten.

3. 27. August 2026 um 14:49 UTCmonitoring

   Ein Backend-Nachrichtensystem hatte die Verbindung verloren und stellt nun den Backlog wieder her. Dies betraf unter anderem Webhooks und die Zahlungsabwicklung.

4. 27. August 2026 um 14:59 UTCinvestigating

   Degradierte Leistung ist zurück, wir untersuchen.

5. 27. August 2026 um 16:36 UTCinvestigating

   Wir untersuchen noch immer.

6. 27. August 2026 um 17:06 UTCinvestigating

   Wir überwachen und untersuchen weiterhin, aber das System funktioniert normal.

7. 27. August 2026 um 17:11 UTCmonitoring

   Wir überwachen weiterhin

8. 27. August 2026 um 17:44 UTCresolved

   Die Systeme sind seit über 1 Stunde stabil und funktionieren korrekt. Wir beobachten weiter.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 11. August 2026 um 12:58 UTCresolved

   Between 11:10 and 11:35 UTC (13:10–13:35 CEST), some users may have experienced errors when signing in via SSO. The issue was intermittent and affected only SSO-based authentication. Sign-ins using other authentication methods were not impacted and continued to work normally. The problem has since been resolved, and SSO login is now operating as expected. Users who were affected should now be able to log in without issue. We apologize for any inconvenience.

1. 20. Juli 2026 um 11:21 UTCinvestigating

   Wir untersuchen derzeit ein Leistungsproblem, das dazu führen kann, dass der Preisgestaltungsbildschirm für einige Immobilien langsam oder nicht mehr reagiert. Wir werden ein Update teilen, sobald wir mehr wissen.

2. 20. Juli 2026 um 13:05 UTCinvestigating

   Wir werden dieses Problem weiter untersuchen.

3. 20. Juli 2026 um 13:09 UTCresolved

   Es wurde ein Update bereitgestellt, das die Leistung verbessert hat.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 30. Juni 2026 um 16:34 UTCinvestigating

   Unser Ingenieurteam untersucht das Problem aktiv und arbeitet daran, die Ursache zu identifizieren. Wir werden ein Update bereitstellen, sobald weitere Informationen verfügbar sind.

2. 30. Juni 2026 um 16:49 UTCmonitoring

   Ein Fix wurde implementiert und wir überwachen die Ergebnisse.

3. 30. Juni 2026 um 16:49 UTCmonitoring

   Wir werden weiterhin auf weitere Probleme achten.

4. 30. Juni 2026 um 17:59 UTCresolved

   Dieser Vorfall wurde behoben.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 5. Mai 2026 um 10:16 UTCinvestigating

   We are currently investigating an issue affecting our platform. Our engineering team is actively investigating the issue and working to identify the root cause. We will provide an update as soon as more information becomes available.

2. 5. Mai 2026 um 10:16 UTCinvestigating

   We are continuing to investigate this issue.

3. 5. Mai 2026 um 10:37 UTCidentified

   The issue has been identified and a fix is being implemented.

4. 5. Mai 2026 um 10:42 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

5. 5. Mai 2026 um 10:55 UTCresolved

   This incident has been resolved.

1. 10. März 2026 um 08:27 UTCinvestigating

   We are currently investigating an issue where the scheduled night audit process did not run for a subset of accounts. Our team is working to identify the root cause and trigger the missing audits where necessary. We will provide an update once more information is available and confirm when processing has been completed.

2. 10. März 2026 um 10:21 UTCidentified

   The issue has been identified and a fix is being implemented.

3. 10. März 2026 um 15:34 UTCmonitoring

   A fix was implemented, all affected night audits have been executed successfully. Monitoring

4. 10. März 2026 um 15:38 UTCresolved

   This incident has been resolved.

1. 9. März 2026 um 16:26 UTCinvestigating

   We are currently investigating an incident affecting invoice creation. At the moment, it appears that customers in Germany and the Netherlands are impacted. Our team is actively working on identifying the root cause and resolving the issue. We will provide further updates as soon as more information becomes available.

2. 9. März 2026 um 16:39 UTCidentified

   The issue has been identified and a fix is being implemented.

3. 9. März 2026 um 16:39 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

4. 9. März 2026 um 16:52 UTCresolved

   This incident has been resolved.

1. 6. März 2026 um 08:21 UTCinvestigating

   We are currently investigating an issue where the scheduled night audit process did not run for a subset of accounts. Our team is working to identify the root cause and trigger the missing audits where necessary. We will provide an update once more information is available and confirm when processing has been completed.

2. 6. März 2026 um 09:08 UTCmonitoring

   The missing night audits are currently being processed. Our team is monitoring the progress to ensure all affected accounts are completed successfully. We will provide another update once processing has fully finished.

3. 6. März 2026 um 10:39 UTCresolved

   All pending night audits have now been successfully processed, and systems are operating normally. Our team will continue to monitor to ensure stability.

1. 21. Februar 2026 um 00:36 UTCinvestigating

   An SSL certificate has expired, we are working on renewing the certificate.

2. 21. Februar 2026 um 00:53 UTCresolved

   This incident has been resolved.

1. 20. Februar 2026 um 19:17 UTCresolved

   We experienced an infrastructure failover on a backend system, the issue has been resolved and delayed processing has been caught up.

1. 17. Februar 2026 um 21:39 UTCinvestigating

   We are currently investigating this issue.

2. 17. Februar 2026 um 21:49 UTCinvestigating

   We are continuing to investigate this issue.

3. 17. Februar 2026 um 21:49 UTCidentified

   The issue has been identified and a fix is being implemented.

4. 17. Februar 2026 um 21:51 UTCmonitoring

   Our messaging infrastructure has resumed normal processing, and is expected to catch up soon. Payments are working although could experience some slowness during the recovery. We continue to monitor.

5. 17. Februar 2026 um 22:14 UTCresolved

   All systems are working nominally, any webhook delays cleared.

1. 11. Februar 2026 um 15:14 UTCresolved

   A transient issue affecting both the UI and API layers resulted in incorrect permission-related messages being returned. The issue was resolved.

1. 29. Januar 2026 um 13:21 UTCresolved

   We experienced a technical issue with GET /finance/v1/folios endpoint that has now been resolved.

1. 18. November 2025 um 13:23 UTCidentified

   There is currently an issue with Cloudflare Turnstile which might prevent some users to login or to submit payments. We are currently implementing a fix.

2. 18. November 2025 um 15:16 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. 18. November 2025 um 17:53 UTCresolved

   This incident has been resolved.

1. 5. November 2025 um 08:44 UTCresolved

   For approx. 20 minutes

1. 23. Oktober 2025 um 14:02 UTCinvestigating

   Folio payments are facing delays in processing due to an internal service degradation. We are investigating on the issue.

2. 23. Oktober 2025 um 14:04 UTCinvestigating

   We are continuing to investigate this issue.

3. 23. Oktober 2025 um 14:38 UTCmonitoring

   An intermittent load spike caused delays and some elevated errors. The system is now operating normally. We will monitor the situation.

4. 23. Oktober 2025 um 14:41 UTCresolved

   We continue to monitor

1. 1. Oktober 2025 um 09:03 UTCinvestigating

   We are currently investigating this issue.

2. 1. Oktober 2025 um 09:04 UTCinvestigating

   We are continuing to investigate this issue.

3. 1. Oktober 2025 um 09:08 UTCidentified

   The issue has been identified and a fix is being implemented.

4. 1. Oktober 2025 um 10:40 UTCidentified

   We have identified the problem and working on a fix still.

5. 1. Oktober 2025 um 11:14 UTCidentified

   We are continuing to work on a fix for this issue.

6. 1. Oktober 2025 um 11:14 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

7. 1. Oktober 2025 um 12:12 UTCmonitoring

   Performance will be

8. 1. Oktober 2025 um 12:12 UTCresolved

   This incident has been resolved.

1. 20. August 2025 um 09:12 UTCinvestigating

   We are currently investigating an issue causing intermittent delays in webhook delivery. Some customers may experience slower-than-normal processing times or degraded performance when receiving webhook events.

2. 21. August 2025 um 09:55 UTCmonitoring

   Our team has implemented mitigations and webhook delivery latency has decreased significantly. Most events are now processing close to normal speed, though we are continuing to monitor performance closely to ensure full stability

3. 22. August 2025 um 08:51 UTCresolved

   Webhook delivery performance has returned to normal, and the vast majority of events are now processing on time. We consider this incident resolved, but our team will continue to monitor the system to ensure sustained stability.

1. 7. August 2025 um 11:24 UTCinvestigating

   We are currently investigating this issue.

2. 7. August 2025 um 11:37 UTCidentified

   The issue has been identified and a fix is being implemented.

3. 7. August 2025 um 11:38 UTCidentified

   Problem identified, fix is prepared for deployment

4. 7. August 2025 um 11:57 UTCmonitoring

   Fix has been deployed.

5. 7. August 2025 um 12:06 UTCresolved

   This incident has been resolved.

1. 2. Juli 2025 um 12:54 UTCinvestigating

   We are currently investigating this issue.

2. 2. Juli 2025 um 12:55 UTCinvestigating

   We are continuing to investigate this issue.

3. 2. Juli 2025 um 13:00 UTCidentified

   The issue has been identified and a fix is being implemented.

4. 2. Juli 2025 um 13:14 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

5. 2. Juli 2025 um 14:09 UTCresolved

   This incident has been resolved.