Istoricul incidentelor Apaleo

1. 27 august 2026 la 13:30 UTCinvestigating

   Investigăm în prezent o problemă care afectează platforma noastră.

2. 27 august 2026 la 13:56 UTCidentified

   Cauza a fost identificată ca fiind o utilizare a API care cauzează sarcini grele în sistemul de baze de date. Sistemele arată normal. Vom continua să monitorizăm.

3. 27 august 2026 la 14:49 UTCmonitoring

   Un sistem de mesaje backend a pierdut conexiunea, și este acum recuperarea backlog. Acest lucru a afectat webhooks și procesarea plăților, printre altele.

4. 27 august 2026 la 14:59 UTCinvestigating

   A revenit performanţa degradată, investigăm.

5. 27 august 2026 la 16:36 UTCinvestigating

   Încă investigăm.

6. 27 august 2026 la 17:06 UTCinvestigating

   Continuăm să monitorizăm şi să investigăm, dar sistemul funcţionează normal.

7. 27 august 2026 la 17:11 UTCmonitoring

   Continuăm monitorizarea

8. 27 august 2026 la 17:44 UTCresolved

   Sistemele sunt stabile şi funcţionează corect de peste 1 oră. Continuăm monitorizarea.

Traducere automată din actualizarea oficială a incidentului.

1. 11 august 2026 la 12:58 UTCresolved

   Intre 11:10 si 11:35 UTC (13:10 Problema a fost intermitentă și a afectat doar autentificarea bazată pe SSO. Signele care utilizează alte metode de autentificare nu au fost afectate și au continuat să funcționeze normal. Problema a fost rezolvată de atunci, iar logarea SSO funcţionează acum conform aşteptărilor. Utilizatorii care au fost afectaţi ar trebui să se poată conecta fără probleme. Ne cerem scuze pentru neplăceri.

Traducere automată din actualizarea oficială a incidentului.

1. 20 iulie 2026 la 11:21 UTCinvestigating

   Investigăm în prezent o problemă de performanță care ar putea determina ca ecranul de tarifare al planului de rate să devină lent sau să nu răspundă la unele proprietăți. Vom împărtăși o actualizare de îndată ce vom ști mai multe.

2. 20 iulie 2026 la 13:05 UTCinvestigating

   Continuăm să investigăm această problemă.

3. 20 iulie 2026 la 13:09 UTCresolved

   A fost implementată o actualizare care a îmbunătățit performanța.

Traducere automată din actualizarea oficială a incidentului.

1. 30 iunie 2026 la 16:34 UTCinvestigating

   Echipa noastră de ingineri investighează în mod activ problema și lucrează pentru a identifica cauza principală. Vom oferi o actualizare de îndată ce mai multe informații devin disponibile.

2. 30 iunie 2026 la 16:49 UTCmonitoring

   A fost implementată o soluţie şi monitorizăm rezultatele.

3. 30 iunie 2026 la 16:49 UTCmonitoring

   Continuăm să monitorizăm orice alte probleme.

4. 30 iunie 2026 la 17:59 UTCresolved

   Acest incident a fost rezolvat.

Traducere automată din actualizarea oficială a incidentului.

1. 5 mai 2026 la 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 la 10:16 UTCinvestigating

   We are continuing to investigate this issue.

3. 5 mai 2026 la 10:37 UTCidentified

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

4. 5 mai 2026 la 10:42 UTCmonitoring

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

5. 5 mai 2026 la 10:55 UTCresolved

   This incident has been resolved.

1. 10 martie 2026 la 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 martie 2026 la 10:21 UTCidentified

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

3. 10 martie 2026 la 15:34 UTCmonitoring

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

4. 10 martie 2026 la 15:38 UTCresolved

   This incident has been resolved.

1. 9 martie 2026 la 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 martie 2026 la 16:39 UTCidentified

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

3. 9 martie 2026 la 16:39 UTCmonitoring

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

4. 9 martie 2026 la 16:52 UTCresolved

   This incident has been resolved.

1. 6 martie 2026 la 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 martie 2026 la 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 martie 2026 la 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 februarie 2026 la 00:36 UTCinvestigating

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

2. 21 februarie 2026 la 00:53 UTCresolved

   This incident has been resolved.

1. 20 februarie 2026 la 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 februarie 2026 la 21:39 UTCinvestigating

   We are currently investigating this issue.

2. 17 februarie 2026 la 21:49 UTCinvestigating

   We are continuing to investigate this issue.

3. 17 februarie 2026 la 21:49 UTCidentified

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

4. 17 februarie 2026 la 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 februarie 2026 la 22:14 UTCresolved

   All systems are working nominally, any webhook delays cleared.

1. 11 februarie 2026 la 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 ianuarie 2026 la 13:21 UTCresolved

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

1. 18 noiembrie 2025 la 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 noiembrie 2025 la 15:16 UTCmonitoring

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

3. 18 noiembrie 2025 la 17:53 UTCresolved

   This incident has been resolved.

1. 5 noiembrie 2025 la 08:44 UTCresolved

   For approx. 20 minutes

1. 23 octombrie 2025 la 14:02 UTCinvestigating

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

2. 23 octombrie 2025 la 14:04 UTCinvestigating

   We are continuing to investigate this issue.

3. 23 octombrie 2025 la 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 octombrie 2025 la 14:41 UTCresolved

   We continue to monitor

1. 1 octombrie 2025 la 09:03 UTCinvestigating

   We are currently investigating this issue.

2. 1 octombrie 2025 la 09:04 UTCinvestigating

   We are continuing to investigate this issue.

3. 1 octombrie 2025 la 09:08 UTCidentified

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

4. 1 octombrie 2025 la 10:40 UTCidentified

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

5. 1 octombrie 2025 la 11:14 UTCidentified

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

6. 1 octombrie 2025 la 11:14 UTCmonitoring

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

7. 1 octombrie 2025 la 12:12 UTCmonitoring

   Performance will be

8. 1 octombrie 2025 la 12:12 UTCresolved

   This incident has been resolved.

1. 20 august 2025 la 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 la 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 la 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 la 11:24 UTCinvestigating

   We are currently investigating this issue.

2. 7 august 2025 la 11:37 UTCidentified

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

3. 7 august 2025 la 11:38 UTCidentified

   Problem identified, fix is prepared for deployment

4. 7 august 2025 la 11:57 UTCmonitoring

   Fix has been deployed.

5. 7 august 2025 la 12:06 UTCresolved

   This incident has been resolved.

1. 2 iulie 2025 la 12:54 UTCinvestigating

   We are currently investigating this issue.

2. 2 iulie 2025 la 12:55 UTCinvestigating

   We are continuing to investigate this issue.

3. 2 iulie 2025 la 13:00 UTCidentified

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

4. 2 iulie 2025 la 13:14 UTCmonitoring

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

5. 2 iulie 2025 la 14:09 UTCresolved

   This incident has been resolved.