Histórico de interrupções do Devolutions

1. 19 Eost 2026 da 15:52 UTCidentified

   A questão foi identificada e está a ser implementada uma solução.

2. 19 Eost 2026 da 16:59 UTCmonitoring

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

3. 19 Eost 2026 da 18:29 UTCresolved

   Este incidente foi resolvido.

Traduzido automaticamente da atualização oficial do incidente.

1. 22 Gouere 2026 da 12:29 UTCidentified

   A questão foi identificada e está a ser implementada uma solução.

2. 22 Gouere 2026 da 17:02 UTCmonitoring

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

3. 22 Gouere 2026 da 17:20 UTCresolved

   Este incidente foi resolvido.

Traduzido automaticamente da atualização oficial do incidente.

1. 14 Gouere 2026 da 07:55 UTCinvestigating

   Estamos actualmente a investigar esta questão.

2. 14 Gouere 2026 da 09:21 UTCidentified

   A questão foi identificada e está a ser implementada uma solução.

3. 14 Gouere 2026 da 13:16 UTCmonitoring

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

4. 14 Gouere 2026 da 15:06 UTCresolved

   O incidente foi resolvido. Se você estiver usando o serviço de criptografia, você pode precisar reiniciá-lo se você ainda encontrar erros.

Traduzido automaticamente da atualização oficial do incidente.

1. 29 Mezheven 2026 da 14:17 UTCidentified

   Identificamos um problema de entrega que afeta códigos MFA baseados em SMS para usuários na Eslovénia. Usuários em outras regiões não são afetados, e outros métodos de autenticação multifatorial permanecem disponíveis.

2. 30 Mezheven 2026 da 18:21 UTCresolved

   Este incidente foi resolvido.

Traduzido automaticamente da atualização oficial do incidente.

1. 28 Mezheven 2026 da 14:03 UTCidentified

   Identificamos o problema que afeta o MFA baseado em SMS e estamos trabalhando com o provedor de terceiros afetado para restaurar o serviço. Outros métodos de autenticação multifatorial permanecem disponíveis.

2. 28 Mezheven 2026 da 14:36 UTCmonitoring

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

3. 28 Mezheven 2026 da 14:58 UTCresolved

   Este incidente foi resolvido.

Traduzido automaticamente da atualização oficial do incidente.

1. 17 Ebrel 2026 da 17:14 UTCidentified

   The workaround is to restart the PAM Services, for example via a cron job.

2. 17 Ebrel 2026 da 18:16 UTCmonitoring

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

3. 17 Ebrel 2026 da 20:19 UTCresolved

   This incident has been resolved.

1. 31 Meurzh 2026 da 12:06 UTCinvestigating

   We are currently investigating this issue.

2. 31 Meurzh 2026 da 12:18 UTCmonitoring

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

3. 31 Meurzh 2026 da 15:16 UTCresolved

   This incident has been resolved.

1. 11 Meurzh 2026 da 14:44 UTCinvestigating

   We are currently investigating this issue.

2. 11 Meurzh 2026 da 14:56 UTCmonitoring

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

3. 11 Meurzh 2026 da 15:03 UTCresolved

   This incident has been resolved.

1. 1 Meurzh 2026 da 14:45 UTCinvestigating

   We are investigating the issue. In the meantime, you can refresh to try to login again.

2. 1 Meurzh 2026 da 14:57 UTCmonitoring

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

3. 1 Meurzh 2026 da 15:57 UTCresolved

   This incident has been resolved.

1. 4 Cʼhwevrer 2026 da 18:28 UTCidentified

   A third-party DNS provider issue is currently preventing the creation of new Hub Business.

2. 4 Cʼhwevrer 2026 da 18:41 UTCmonitoring

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

3. 4 Cʼhwevrer 2026 da 18:47 UTCresolved

   This incident has been resolved.

1. 3 Cʼhwevrer 2026 da 19:15 UTCinvestigating

   We are currently investigating this issue.

2. 3 Cʼhwevrer 2026 da 19:55 UTCmonitoring

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

3. 3 Cʼhwevrer 2026 da 20:24 UTCresolved

   This incident has been resolved.

1. 3 Cʼhwevrer 2026 da 15:30 UTCinvestigating

   We are currently investigating this issue.

2. 3 Cʼhwevrer 2026 da 15:54 UTCinvestigating

   We are continuing to investigate this issue.

3. 3 Cʼhwevrer 2026 da 16:07 UTCinvestigating

   The store is back online.

4. 3 Cʼhwevrer 2026 da 17:17 UTCresolved

   This incident has been resolved.

1. 7 Genver 2026 da 16:20 UTCinvestigating

   We are currently investigating this issue.

2. 7 Genver 2026 da 16:38 UTCmonitoring

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

3. 7 Genver 2026 da 16:51 UTCresolved

   This incident has been resolved.

1. 9 Kerzu 2025 da 20:03 UTCinvestigating

   We are currently investigating this issue.

2. 9 Kerzu 2025 da 20:35 UTCmonitoring

   The issue is no longer occurring. We will continue to monitor the situation.

3. 9 Kerzu 2025 da 21:20 UTCresolved

   This incident has been resolved.

1. 18 Du 2025 da 19:32 UTCinvestigating

   We are currently investigating this issue.

2. 18 Du 2025 da 20:13 UTCmonitoring

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

3. 18 Du 2025 da 20:32 UTCresolved

   This incident has been resolved.

1. 18 Du 2025 da 12:47 UTCidentified

   Cloudflare is experiencing a global network incident (started 11:48 UTC, Nov 18) that may cause intermittent 500 errors when accessing our services. Our team is actively monitoring the situation and Cloudflare's resolution progress. Track updates: https://www.cloudflarestatus.com/ We apologize for any disruption and will update you as soon as the issue is resolved. Thank you for your patience.

2. 18 Du 2025 da 13:59 UTCidentified

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

3. 18 Du 2025 da 14:30 UTCidentified

   We are implementing a mitigation and services are beginning to come back online. We will continue to monitor the situation and provide updates.

4. 18 Du 2025 da 14:49 UTCmonitoring

   Cloudflare has implemented a fix and all services are now available. We are actively monitoring to ensure everything remains stable.

5. 18 Du 2025 da 17:00 UTCresolved

   This incident has been resolved.

1. 29 Here 2025 da 12:27 UTCinvestigating

   We are currently investigating this issue.

2. 29 Here 2025 da 12:56 UTCresolved

   This incident has been resolved.

1. 8 Here 2025 da 16:08 UTCinvestigating

   We are currently investigating this issue.

2. 8 Here 2025 da 16:27 UTCmonitoring

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

3. 8 Here 2025 da 16:31 UTCresolved

   This incident has been resolved.

1. 7 Here 2025 da 13:54 UTCinvestigating

   We are currently investigating this issue.

2. 7 Here 2025 da 14:17 UTCinvestigating

   We are continuing to investigate this issue.

3. 7 Here 2025 da 15:11 UTCidentified

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

4. 7 Here 2025 da 15:50 UTCmonitoring

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

5. 7 Here 2025 da 17:44 UTCresolved

   This incident has been resolved.

1. 5 Here 2025 da 03:03 UTCinvestigating

   We are currently investigating this issue.

2. 5 Here 2025 da 03:31 UTCmonitoring

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

3. 5 Here 2025 da 03:43 UTCresolved

   This incident has been resolved.