Historial de interrupciones de Apaleo

1. 29 de septiembre de 2026 a las 13:55 UTCinvestigating

   Actualmente estamos investigando un problema que afecta a nuestra plataforma.

2. 29 de septiembre de 2026 a las 14:19 UTCidentified

   Se ha identificado el problema, se está poniendo en marcha la solución. Supervisaremos la recuperación.

3. 29 de septiembre de 2026 a las 14:28 UTCmonitoring

   El sistema parece funcionar normalmente de nuevo, estamos monitoreando

4. 29 de septiembre de 2026 a las 15:31 UTCresolved

   Todos los sistemas están estables

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

1. 27 de agosto de 2026 a las 13:30 UTCinvestigating

   Actualmente estamos investigando un problema que afecta a nuestra plataforma.

2. 27 de agosto de 2026 a las 13:56 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. 27 de agosto de 2026 a las 14:49 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. 27 de agosto de 2026 a las 14:59 UTCinvestigating

   El rendimiento degradado ha vuelto, estamos investigando.

5. 27 de agosto de 2026 a las 16:36 UTCinvestigating

   Todavía estamos investigando.

6. 27 de agosto de 2026 a las 17:06 UTCinvestigating

   Seguimos monitoreando e investigando, pero el sistema funciona normalmente.

7. 27 de agosto de 2026 a las 17:11 UTCmonitoring

   Continuamos monitoreando

8. 27 de agosto de 2026 a las 17:44 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. 11 de agosto de 2026 a las 12:58 UTCresolved

   Entre las 11:10 y las 11:35 UTC (13:10–13:35 CEST), algunos usuarios pueden haber experimentado errores al iniciar sesión a través de SSO. The issue was intermittent and affected only SSO-based autation. Los registros utilizando otros métodos de autenticación no fueron impactados y continuaron trabajando normalmente. El problema se ha resuelto desde entonces, y SSO login está operando como se espera. Los usuarios afectados deben ahora poder iniciar sesión sin problemas. Nos disculpamos por cualquier inconveniente.

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

1. 20 de julio de 2026 a las 11:21 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. 20 de julio de 2026 a las 13:05 UTCinvestigating

   Seguimos investigando esta cuestión.

3. 20 de julio de 2026 a las 13:09 UTCresolved

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

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

1. 30 de junio de 2026 a las 16:34 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. 30 de junio de 2026 a las 16:49 UTCmonitoring

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

3. 30 de junio de 2026 a las 16:49 UTCmonitoring

   Continuamos monitoreando cualquier otro problema.

4. 30 de junio de 2026 a las 17:59 UTCresolved

   Este incidente ha sido resuelto.

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

1. 5 de mayo de 2026 a las 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 de mayo de 2026 a las 10:16 UTCinvestigating

   We are continuing to investigate this issue.

3. 5 de mayo de 2026 a las 10:37 UTCidentified

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

4. 5 de mayo de 2026 a las 10:42 UTCmonitoring

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

5. 5 de mayo de 2026 a las 10:55 UTCresolved

   This incident has been resolved.

1. 10 de marzo de 2026 a las 8: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 de marzo de 2026 a las 10:21 UTCidentified

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

3. 10 de marzo de 2026 a las 15:34 UTCmonitoring

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

4. 10 de marzo de 2026 a las 15:38 UTCresolved

   This incident has been resolved.

1. 9 de marzo de 2026 a las 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 de marzo de 2026 a las 16:39 UTCidentified

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

3. 9 de marzo de 2026 a las 16:39 UTCmonitoring

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

4. 9 de marzo de 2026 a las 16:52 UTCresolved

   This incident has been resolved.

1. 6 de marzo de 2026 a las 8: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 de marzo de 2026 a las 9: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 de marzo de 2026 a las 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 de febrero de 2026 a las 0:36 UTCinvestigating

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

2. 21 de febrero de 2026 a las 0:53 UTCresolved

   This incident has been resolved.

1. 20 de febrero de 2026 a las 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 de febrero de 2026 a las 21:39 UTCinvestigating

   We are currently investigating this issue.

2. 17 de febrero de 2026 a las 21:49 UTCinvestigating

   We are continuing to investigate this issue.

3. 17 de febrero de 2026 a las 21:49 UTCidentified

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

4. 17 de febrero de 2026 a las 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 de febrero de 2026 a las 22:14 UTCresolved

   All systems are working nominally, any webhook delays cleared.

1. 11 de febrero de 2026 a las 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 de enero de 2026 a las 13:21 UTCresolved

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

1. 18 de noviembre de 2025 a las 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 de noviembre de 2025 a las 15:16 UTCmonitoring

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

3. 18 de noviembre de 2025 a las 17:53 UTCresolved

   This incident has been resolved.

1. 5 de noviembre de 2025 a las 8:44 UTCresolved

   For approx. 20 minutes

1. 23 de octubre de 2025 a las 14:02 UTCinvestigating

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

2. 23 de octubre de 2025 a las 14:04 UTCinvestigating

   We are continuing to investigate this issue.

3. 23 de octubre de 2025 a las 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 de octubre de 2025 a las 14:41 UTCresolved

   We continue to monitor

1. 1 de octubre de 2025 a las 9:03 UTCinvestigating

   We are currently investigating this issue.

2. 1 de octubre de 2025 a las 9:04 UTCinvestigating

   We are continuing to investigate this issue.

3. 1 de octubre de 2025 a las 9:08 UTCidentified

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

4. 1 de octubre de 2025 a las 10:40 UTCidentified

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

5. 1 de octubre de 2025 a las 11:14 UTCidentified

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

6. 1 de octubre de 2025 a las 11:14 UTCmonitoring

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

7. 1 de octubre de 2025 a las 12:12 UTCmonitoring

   Performance will be

8. 1 de octubre de 2025 a las 12:12 UTCresolved

   This incident has been resolved.

1. 20 de agosto de 2025 a las 9: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 de agosto de 2025 a las 9: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 de agosto de 2025 a las 8: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 de agosto de 2025 a las 11:24 UTCinvestigating

   We are currently investigating this issue.

2. 7 de agosto de 2025 a las 11:37 UTCidentified

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

3. 7 de agosto de 2025 a las 11:38 UTCidentified

   Problem identified, fix is prepared for deployment

4. 7 de agosto de 2025 a las 11:57 UTCmonitoring

   Fix has been deployed.

5. 7 de agosto de 2025 a las 12:06 UTCresolved

   This incident has been resolved.