Histórico de interrupções do Apaleo

1. 29 Gwengolo 2026 da 13:55 UTCinvestigating

   Atualmente estamos investigando um problema que afeta nossa plataforma.

2. 29 Gwengolo 2026 da 14:19 UTCidentified

   A questão foi identificada, a solução está a ser lançada. Vamos monitorizar a recuperação.

3. 29 Gwengolo 2026 da 14:28 UTCmonitoring

   Sistema parece funcionar normalmente novamente, estamos monitorando

4. 29 Gwengolo 2026 da 15:31 UTCresolved

   Todos os sistemas estão estáveis

Traduzido automaticamente da atualização oficial do incidente.

1. 27 Eost 2026 da 13:30 UTCinvestigating

   Atualmente estamos investigando um problema que afeta nossa plataforma.

2. 27 Eost 2026 da 13:56 UTCidentified

   A causa foi identificada como algum uso da API causando carga pesada no sistema de banco de dados. Os sistemas parecem normais. Continuaremos a monitorizar.

3. 27 Eost 2026 da 14:49 UTCmonitoring

   Um sistema de mensagens de backend perdeu a conexão, e agora está recuperando o backlog. Isso afetou webhooks e processamento de pagamento, entre outros.

4. 27 Eost 2026 da 14:59 UTCinvestigating

   O desempenho degradado voltou, estamos a investigar.

5. 27 Eost 2026 da 16:36 UTCinvestigating

   Ainda estamos a investigar.

6. 27 Eost 2026 da 17:06 UTCinvestigating

   Nós continuamos a monitorar e investigar, mas o sistema está funcionando normalmente.

7. 27 Eost 2026 da 17:11 UTCmonitoring

   Continuamos a acompanhar

8. 27 Eost 2026 da 17:44 UTCresolved

   Os sistemas estão estáveis e funcionam corretamente há mais de 1 hora. Continuamos a monitorizar.

Traduzido automaticamente da atualização oficial do incidente.

1. 11 Eost 2026 da 12:58 UTCresolved

   Entre 11:10 e 11:35 UTC (13:10-13:35 CEST), alguns usuários podem ter experimentado erros ao iniciar sessão via SSO. O problema foi intermitente e afetou apenas a autenticação baseada em SSO. Sinais utilizando outros métodos de autenticação não foram afetados e continuaram a funcionar normalmente. O problema já foi resolvido, e o login do SSO agora está funcionando como esperado. Usuários que foram afetados devem agora ser capazes de entrar sem problemas. Pedimos desculpa por qualquer inconveniente.

Traduzido automaticamente da atualização oficial do incidente.

1. 20 Gouere 2026 da 11:21 UTCinvestigating

   Atualmente estamos investigando um problema de desempenho que pode fazer com que a tela de preços do plano de taxa se torne lenta ou sem resposta para algumas propriedades. Iremos partilhar uma actualização assim que soubermos mais.

2. 20 Gouere 2026 da 13:05 UTCinvestigating

   Continuamos a investigar esta questão.

3. 20 Gouere 2026 da 13:09 UTCresolved

   Foi implantada uma atualização que melhorou o desempenho.

Traduzido automaticamente da atualização oficial do incidente.

1. 30 Mezheven 2026 da 16:34 UTCinvestigating

   Nossa equipe de engenharia está ativamente investigando o problema e trabalhando para identificar a causa raiz. Forneceremos uma atualização assim que mais informações estiverem disponíveis.

2. 30 Mezheven 2026 da 16:49 UTCmonitoring

   Foi implementada uma correção e estamos monitorando os resultados.

3. 30 Mezheven 2026 da 16:49 UTCmonitoring

   Continuamos monitorando quaisquer outros problemas.

4. 30 Mezheven 2026 da 17:59 UTCresolved

   Este incidente foi resolvido.

Traduzido automaticamente da atualização oficial do incidente.

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

   We are continuing to investigate this issue.

3. 5 Mae 2026 da 10:37 UTCidentified

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

4. 5 Mae 2026 da 10:42 UTCmonitoring

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

5. 5 Mae 2026 da 10:55 UTCresolved

   This incident has been resolved.

1. 10 Meurzh 2026 da 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 Meurzh 2026 da 10:21 UTCidentified

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

3. 10 Meurzh 2026 da 15:34 UTCmonitoring

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

4. 10 Meurzh 2026 da 15:38 UTCresolved

   This incident has been resolved.

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

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

3. 9 Meurzh 2026 da 16:39 UTCmonitoring

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

4. 9 Meurzh 2026 da 16:52 UTCresolved

   This incident has been resolved.

1. 6 Meurzh 2026 da 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 Meurzh 2026 da 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 Meurzh 2026 da 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 Cʼhwevrer 2026 da 00:36 UTCinvestigating

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

2. 21 Cʼhwevrer 2026 da 00:53 UTCresolved

   This incident has been resolved.

1. 20 Cʼhwevrer 2026 da 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 Cʼhwevrer 2026 da 21:39 UTCinvestigating

   We are currently investigating this issue.

2. 17 Cʼhwevrer 2026 da 21:49 UTCinvestigating

   We are continuing to investigate this issue.

3. 17 Cʼhwevrer 2026 da 21:49 UTCidentified

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

4. 17 Cʼhwevrer 2026 da 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 Cʼhwevrer 2026 da 22:14 UTCresolved

   All systems are working nominally, any webhook delays cleared.

1. 11 Cʼhwevrer 2026 da 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 Genver 2026 da 13:21 UTCresolved

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

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

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

3. 18 Du 2025 da 17:53 UTCresolved

   This incident has been resolved.

1. 5 Du 2025 da 08:44 UTCresolved

   For approx. 20 minutes

1. 23 Here 2025 da 14:02 UTCinvestigating

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

2. 23 Here 2025 da 14:04 UTCinvestigating

   We are continuing to investigate this issue.

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

   We continue to monitor

1. 1 Here 2025 da 09:03 UTCinvestigating

   We are currently investigating this issue.

2. 1 Here 2025 da 09:04 UTCinvestigating

   We are continuing to investigate this issue.

3. 1 Here 2025 da 09:08 UTCidentified

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

4. 1 Here 2025 da 10:40 UTCidentified

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

5. 1 Here 2025 da 11:14 UTCidentified

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

6. 1 Here 2025 da 11:14 UTCmonitoring

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

7. 1 Here 2025 da 12:12 UTCmonitoring

   Performance will be

8. 1 Here 2025 da 12:12 UTCresolved

   This incident has been resolved.

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

   We are currently investigating this issue.

2. 7 Eost 2025 da 11:37 UTCidentified

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

3. 7 Eost 2025 da 11:38 UTCidentified

   Problem identified, fix is prepared for deployment

4. 7 Eost 2025 da 11:57 UTCmonitoring

   Fix has been deployed.

5. 7 Eost 2025 da 12:06 UTCresolved

   This incident has been resolved.