Historial de interrupciones de Apaleo

1. August 27, 2026 at 1:30 PM UTCinvestigating

   Actualmente estamos investigando un problema que afecta a nuestra plataforma.

2. August 27, 2026 at 1:56 PM UTCidentified

   La causa se ha identificado como algún uso de API que causa una carga pesada en el sistema de bases de datos. Los sistemas se ven normales. Seguiremos monitoreando.

3. August 27, 2026 at 2:49 PM UTCmonitoring

   Un sistema de mensajes de backend había perdido la conexión, y ahora está recuperando el atraso. Este webhooks afectado y procesamiento de pagos entre otros.

4. August 27, 2026 at 2:59 PM UTCinvestigating

   El rendimiento degradado ha vuelto, estamos investigando.

5. August 27, 2026 at 4:36 PM UTCinvestigating

   Todavía estamos investigando.

6. August 27, 2026 at 5:06 PM UTCinvestigating

   Seguimos monitoreando e investigando, pero el sistema funciona normalmente.

7. August 27, 2026 at 5:11 PM UTCmonitoring

   Continuamos monitoreando

8. August 27, 2026 at 5:44 PM UTCresolved

   Los sistemas han sido estables y funcionan correctamente durante más de 1 hora. Continuamos monitoreando.

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

1. August 11, 2026 at 12:58 PM 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. July 20, 2026 at 11:21 AM UTCinvestigating

   Actualmente estamos investigando un problema de rendimiento que puede causar que la pantalla de precios del plan de tarifas se vuelva lenta o no responde para algunas propiedades. Compartiremos una actualización tan pronto como sepamos más.

2. July 20, 2026 at 1:05 PM UTCinvestigating

   Seguimos investigando esta cuestión.

3. July 20, 2026 at 1:09 PM UTCresolved

   Se ha desplegado una actualización que ha mejorado el rendimiento.

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

1. June 30, 2026 at 4:34 PM UTCinvestigating

   Nuestro equipo de ingeniería está investigando activamente la cuestión y trabajando para identificar la causa raíz. Proporcionaremos una actualización tan pronto como se disponga de más información.

2. June 30, 2026 at 4:49 PM UTCmonitoring

   Se ha aplicado una solución y estamos monitoreando los resultados.

3. June 30, 2026 at 4:49 PM UTCmonitoring

   Continuamos monitoreando cualquier otro problema.

4. June 30, 2026 at 5:59 PM UTCresolved

   Este incidente ha sido resuelto.

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

1. May 5, 2026 at 10:16 AM 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. May 5, 2026 at 10:16 AM UTCinvestigating

   We are continuing to investigate this issue.

3. May 5, 2026 at 10:37 AM UTCidentified

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

4. May 5, 2026 at 10:42 AM UTCmonitoring

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

5. May 5, 2026 at 10:55 AM UTCresolved

   This incident has been resolved.

1. March 10, 2026 at 8:27 AM 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. March 10, 2026 at 10:21 AM UTCidentified

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

3. March 10, 2026 at 3:34 PM UTCmonitoring

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

4. March 10, 2026 at 3:38 PM UTCresolved

   This incident has been resolved.

1. March 9, 2026 at 4:26 PM 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. March 9, 2026 at 4:39 PM UTCidentified

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

3. March 9, 2026 at 4:39 PM UTCmonitoring

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

4. March 9, 2026 at 4:52 PM UTCresolved

   This incident has been resolved.

1. March 6, 2026 at 8:21 AM 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. March 6, 2026 at 9:08 AM 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. March 6, 2026 at 10:39 AM 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. February 21, 2026 at 12:36 AM UTCinvestigating

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

2. February 21, 2026 at 12:53 AM UTCresolved

   This incident has been resolved.

1. February 20, 2026 at 7:17 PM UTCresolved

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

1. February 17, 2026 at 9:39 PM UTCinvestigating

   We are currently investigating this issue.

2. February 17, 2026 at 9:49 PM UTCinvestigating

   We are continuing to investigate this issue.

3. February 17, 2026 at 9:49 PM UTCidentified

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

4. February 17, 2026 at 9:51 PM 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. February 17, 2026 at 10:14 PM UTCresolved

   All systems are working nominally, any webhook delays cleared.

1. February 11, 2026 at 3:14 PM UTCresolved

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

1. January 29, 2026 at 1:21 PM UTCresolved

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

1. November 18, 2025 at 1:23 PM 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. November 18, 2025 at 3:16 PM UTCmonitoring

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

3. November 18, 2025 at 5:53 PM UTCresolved

   This incident has been resolved.

1. November 5, 2025 at 8:44 AM UTCresolved

   For approx. 20 minutes

1. October 23, 2025 at 2:02 PM UTCinvestigating

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

2. October 23, 2025 at 2:04 PM UTCinvestigating

   We are continuing to investigate this issue.

3. October 23, 2025 at 2:38 PM UTCmonitoring

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

4. October 23, 2025 at 2:41 PM UTCresolved

   We continue to monitor

1. October 1, 2025 at 9:03 AM UTCinvestigating

   We are currently investigating this issue.

2. October 1, 2025 at 9:04 AM UTCinvestigating

   We are continuing to investigate this issue.

3. October 1, 2025 at 9:08 AM UTCidentified

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

4. October 1, 2025 at 10:40 AM UTCidentified

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

5. October 1, 2025 at 11:14 AM UTCidentified

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

6. October 1, 2025 at 11:14 AM UTCmonitoring

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

7. October 1, 2025 at 12:12 PM UTCmonitoring

   Performance will be

8. October 1, 2025 at 12:12 PM UTCresolved

   This incident has been resolved.

1. August 20, 2025 at 9:12 AM 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. August 21, 2025 at 9:55 AM 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. August 22, 2025 at 8:51 AM 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. August 7, 2025 at 11:24 AM UTCinvestigating

   We are currently investigating this issue.

2. August 7, 2025 at 11:37 AM UTCidentified

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

3. August 7, 2025 at 11:38 AM UTCidentified

   Problem identified, fix is prepared for deployment

4. August 7, 2025 at 11:57 AM UTCmonitoring

   Fix has been deployed.

5. August 7, 2025 at 12:06 PM UTCresolved

   This incident has been resolved.

1. July 2, 2025 at 12:54 PM UTCinvestigating

   We are currently investigating this issue.

2. July 2, 2025 at 12:55 PM UTCinvestigating

   We are continuing to investigate this issue.

3. July 2, 2025 at 1:00 PM UTCidentified

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

4. July 2, 2025 at 1:14 PM UTCmonitoring

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

5. July 2, 2025 at 2:09 PM UTCresolved

   This incident has been resolved.