Histórico de interrupções do Sashido

1. 24 Here 2026 da 14:08 UTCinvestigating

   A nossa equipa está a investigar a causa principal do problema.

2. 24 Here 2026 da 17:10 UTCmonitoring

   Nosso sistema de monitoramento relata que todas as aplicações falhadas são saudáveis. Continuaremos a acompanhar proactivamente.

3. 24 Here 2026 da 17:40 UTCresolved

   Boas notícias! As coisas devem voltar ao normal de novo. Por favor, avise-nos se houver mais problemas. Muito obrigado pela vossa paciência enquanto trabalhávamos para resolver isto.

Traduzido automaticamente da atualização oficial do incidente.

1. 28 Gwengolo 2026 da 15:55 UTCinvestigating

   Atualmente estamos experimentando um problema que afeta e-mails transacionais de saída dos Servidores de Processamento na Região da UE. Nosso provedor de entrega de e-mail, Amazon SES, tem pausado temporariamente o envio de uma de nossas regiões de produção enquanto eles analisam atividade de envio incomum. Como resultado, alguns e-mails como notificações de conta, e-mails de verificação, resets de senha e outras mensagens transacionais podem ser atrasados ou não entregues. Nossos sistemas permanecem operacionais, e atualmente não há indicação de que os dados do cliente tenham sido afetados. Estamos investigando ativamente o problema com a AWS e revisando nossa infraestrutura de email. Restaurar a entrega normal de email é nossa maior prioridade. Forneceremos outra atualização assim que tivermos mais informações.

2. 4 Here 2026 da 08:32 UTCinvestigating

   Continuamos a trabalhar activamente na resolução da perturbação da entrega de correio electrónico transaccional que afecta os servidores de processamento na região da UE. Junto com a Amazon AWS, estamos investigando a fonte da atividade de envio incomum que fez com que a Amazon SES pausasse temporariamente a entrega de e-mail da região de produção afetada. Nosso foco atual não é apenas em restaurar o serviço normal, mas também em identificar a causa raiz e garantir que o problema não pode voltar. A investigação está demorando mais do que inicialmente esperávamos, e entendemos que a entrega de email transacional, incluindo verificação de conta, reset de senhas, notificações e outros e-mails de aplicativos, pode ser fundamental para alguns dos negócios de nossos clientes. Se este incidente está tendo um impacto significativo em sua aplicação de produção ou operações de negócios, entre em contato com nossa equipe de sucesso do cliente em [email protected] Trabalharemos diretamente com você para avaliar e, sempre que possível, fornecer uma solução alternativa de entrega de email enquanto a investigação com a AWS continua. Nossa infraestrutura e aplicativos do Parse Server permanecem operacionais, e atualmente não temos nenhuma indicação de que os dados do cliente tenham sido afetados. Pedimos desculpas pela interrupção prolongada e apreciamos sua paciência enquanto trabalhamos com a AWS para resolver totalmente o problema. Forneceremos outra atualização assim que tivermos progresso significativo para compartilhar.

3. 4 Here 2026 da 12:43 UTCidentified

   Identificamos a fonte da atividade de envio incomum que fez com que a Amazon SES pausasse o envio de e-mail da região de produção afetada. Nossa equipe já começou a implementar as correções necessárias e melhorias de segurança. Uma vez concluídas essas alterações, validaremos os sistemas afetados para garantir que o problema tenha sido totalmente abordado e que o envio normal possa retomar com segurança. Após esta validação, vamos coordenar com a Amazon AWS para concluir sua revisão e restaurar a entrega de email transacional de saída. O processo de investigação e remediação levou mais tempo do que inicialmente esperávamos, e entendemos que e-mails transacionais — incluindo verificação de conta, reset de senhas, notificações e outros e-mails de aplicativos, podem ser críticos para alguns clientes. Se este incidente está afetando significativamente sua aplicação de produção ou operações de negócios, entre em contato com nossa equipe de suporte. Trabalharemos diretamente com você para avaliar e, sempre que possível, fornecer uma solução alternativa de entrega de email enquanto a remediação final e revisão AWS estão sendo concluídas. Nossa infraestrutura e aplicativos do Parse Server permanecem operacionais, e atualmente não temos nenhuma indicação de que os dados do cliente tenham sido afetados. Agradecemos a sua paciência e forneceremos outra atualização assim que o processo de remediação e validação progredir ainda mais.

4. 5 Here 2026 da 07:15 UTCmonitoring

   A Verificamos que os e-mails estão sendo enviados com sucesso e continuarão a monitorar de perto a infraestrutura e a atividade de envio para garantir que o serviço permaneça estável. Neste ponto, consideramos a interrupção imediata do serviço resolvida, enquanto o monitoramento continuará como uma precaução adicional. Obrigado pela vossa paciência e compreensão durante todo este incidente.

5. 6 Here 2026 da 08:47 UTCmonitoring

   A entrega de email transacional continua operacional, e continuamos a monitorar de perto a infraestrutura após o recente trabalho de remediação. Como parte das medidas de segurança adicionais que introduzimos, estamos actualmente a ver um pequeno número de falsos positivos que afectam alguma actividade de aplicação legítima do cliente. Estamos revisando esses casos continuamente e implementando ajustes o mais rápido possível para minimizar qualquer impacto e garantir que as aplicações do cliente continuem funcionando normalmente. Gostaríamos de agradecer a todos os clientes que relataram comportamento inesperado, seus relatórios são extremamente úteis em nos permitir identificar e resolver esses casos rapidamente. Nós também apreciamos sua paciência e compreensão enquanto continuamos a fortalecer a proteção de nossa infraestrutura. Em algumas situações, nossas salvaguardas podem ser temporariamente mais restritivas do que o necessário, mas nossa prioridade é proteger a plataforma e, em última análise, as aplicações e negócios de nossos clientes que estão em operação nela. Continuaremos a acompanhar de perto a situação e, sempre que necessário, proceder a ajustamentos.

6. 15 Here 2026 da 14:30 UTCresolved

   Este incidente foi resolvido.

Traduzido automaticamente da atualização oficial do incidente.

1. 22 Mae 2026 da 09:11 UTCinvestigating

   We're experiencing an increased rate of unhealthy applications. Currently we are looking into the issue.

2. 22 Mae 2026 da 10:01 UTCidentified

   We are currently experiencing connectivity issues affecting part of our infrastructure hosted in the FR-PAR datacenter region. Our datacenter provider, Scaleway, has confirmed an ongoing network incident in the same region. According to their latest update, the issue is related to a power problem inside the datacenter, and most services have already recovered while their teams continue working on the remaining affected systems. Some users may experience intermittent connectivity issues, increased latency, or temporary service interruptions. Our team is actively monitoring the situation and will continue to follow Scaleway’s recovery progress closely. We will provide another update as soon as we have more information or once the situation is fully stabilized. Provider incident: https://status.scaleway.com/incidents/qkj49g6g3ykp

3. 22 Mae 2026 da 10:53 UTCmonitoring

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

4. 22 Mae 2026 da 11:25 UTCresolved

   Good news! Things should be back to normal again across the board. Please let us know if there is any further trouble. Thank you so much for your patience while we worked to sort this out.

1. 12 Mae 2026 da 13:18 UTCinvestigating

   We're experiencing an increased rate of applications health errors currently looking into the issue.

2. 12 Mae 2026 da 14:29 UTCmonitoring

   Our monitoring system report all of the failing applications are healthy. We we will continue monitoring proactively.

3. 12 Mae 2026 da 14:59 UTCresolved

   The incident is resolved. Apologies for this connection blip. Thank you as always for sticking with us, we really appreciate it.

1. 23 Ebrel 2026 da 16:47 UTCinvestigating

   Our team is currently investigating the root cause of the issue.

2. 23 Ebrel 2026 da 16:55 UTCidentified

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

3. 23 Ebrel 2026 da 17:48 UTCmonitoring

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

4. 23 Ebrel 2026 da 18:18 UTCresolved

   Issue is resolved and for more than 1 hour there are no reports for unhealthy applications.

1. 13 Ebrel 2026 da 17:48 UTCinvestigating

   We're experiencing an increased rate of applications health errors currently looking into the issue.

2. 13 Ebrel 2026 da 17:59 UTCidentified

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

3. 13 Ebrel 2026 da 18:52 UTCmonitoring

   Our monitoring system report all of the failing applications are healthy. We we will continue monitoring proactively.

4. 13 Ebrel 2026 da 19:22 UTCresolved

   Issue is resolved and for more than 1 hour there are no reports for unhealthy applications.

1. 25 Meurzh 2026 da 12:54 UTCinvestigating

   We are currently experiencing an issue where builds and deployments are completing successfully at the infrastructure level, but are not being correctly reflected in the Dashboard for some applications. This appears to be a synchronization issue affecting the Dashboard visibility layer only. There is no impact on the actual build or deployment processes. Our team is actively investigating the root cause.

2. 25 Meurzh 2026 da 23:16 UTCmonitoring

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

3. 30 Meurzh 2026 da 11:49 UTCresolved

   This incident has been resolved.

1. 22 Meurzh 2026 da 08:17 UTCinvestigating

   Our team is currently investigating the root cause of the issue

2. 22 Meurzh 2026 da 10:06 UTCmonitoring

   We have identified and mitigated the immediate issue affecting multiple hypervisors. The platform is currently stable. We are continuing to investigate the underlying cause of the unusual hardware behavior to ensure long-term reliability. At this stage, there is no active impact, but we are monitoring closely and will share further updates as we learn more.

3. 22 Meurzh 2026 da 16:27 UTCmonitoring

   We continue to monitor the situation closely following the mitigation of the issue affecting multiple hypervisors. The platform remains stable following the applied mitigation. We are continuing to monitor the situation closely and investigate the root cause of the unusual hardware behavior. If you notice anything unexpected or experience any issues, please contact our support team immediately. Our team is actively investigating the underlying cause to ensure long-term reliability.

4. 22 Meurzh 2026 da 16:34 UTCmonitoring

   We continue to monitor the situation closely and investigate the underlying cause. As shared previously, we will provide the next update on this status page as soon as we have any significant new information.

5. 1 Ebrel 2026 da 14:34 UTCresolved

   After 10 days with no further anomalies observed, we are closing this incident. Over the course of the remediation, we fully replaced 100% of our database hardware infrastructure in Europe. This included a significant number of migrations, reconfigurations, and coordinated infrastructure changes performed across the platform. The work required a major effort from our engineering team and was executed with a strong focus on maintaining platform stability and minimizing customer-facing impact. Since completion, the platform has remained stable, and the affected services are now running on new and improved hardware. We will continue to monitor the environment closely, but at this stage the incident is considered resolved.

1. 2 Meurzh 2026 da 16:16 UTCinvestigating

   We're experiencing an increased rate of applications health errors currently looking into the issue.

2. 2 Meurzh 2026 da 17:20 UTCmonitoring

   We have implemented a fix for this issue and are currently monitoring the results. We will update once we have confirmed it is resolved.

3. 2 Meurzh 2026 da 17:50 UTCresolved

   Good news! Things should be back to normal again across the board. Please let us know if there is any further trouble. Thank you so much for your patience while we worked to sort this out.

1. 10 Cʼhwevrer 2026 da 21:31 UTCinvestigating

   We're experiencing an increased rate of applications health errors currently looking into the issue.

2. 10 Cʼhwevrer 2026 da 22:33 UTCmonitoring

   All applications have returned to healthy state. We will continue to monitor the situation.

3. 10 Cʼhwevrer 2026 da 23:03 UTCresolved

   Good news! Things should be back to normal again across the board. Please let us know if there is any further trouble. Thank you so much for your patience while we worked to sort this out.

1. 20 Genver 2026 da 12:48 UTCinvestigating

   Our team is currently investigating the root cause of the issue.

2. 20 Genver 2026 da 14:03 UTCmonitoring

   All applications have returned to healthy state. We will continue to monitor the situation.

3. 20 Genver 2026 da 14:34 UTCresolved

   We have some good news to share! Everything is now looking clear from our side and all users should be able to work with their applications without any interruptions. Please let us know at [email protected] if you are still experiencing problems. We apologize for disrupting your day and thank you for your patience.

1. 29 Kerzu 2025 da 00:02 UTCinvestigating

   We're experiencing an increased rate of applications health errors currently looking into the issue.

2. 29 Kerzu 2025 da 01:12 UTCmonitoring

   We have implemented a fix for this issue and are currently monitoring the results. We will update once we have confirmed it is resolved.

3. 29 Kerzu 2025 da 01:42 UTCresolved

   Good news! Things should be back to normal again across the board. Please let us know if there is any further trouble. Thank you so much for your patience while we worked to sort this out.

1. 19 Kerzu 2025 da 18:16 UTCinvestigating

   Our team is currently investigating the root cause of the issue.

2. 19 Kerzu 2025 da 19:19 UTCmonitoring

   We have implemented a fix for this issue and are currently monitoring the results. We will update once we have confirmed it is resolved.

3. 19 Kerzu 2025 da 19:49 UTCresolved

   Good news! Things should be back to normal again across the board. Please let us know if there is any further trouble. Thank you so much for your patience while we worked to sort this out.

1. 2 Kerzu 2025 da 14:12 UTCinvestigating

   We're experiencing an increased rate of applications health errors currently looking into the issue.

2. 2 Kerzu 2025 da 14:38 UTCidentified

   We’ve identified the cause of the increased application errors. The issue originates from our data center provider, who is currently experiencing an outage impacting network and compute stability. Our platform remains operational, but some requests may continue to fail intermittently until the provider resolves the incident. You can follow their official updates here: https://bare-metal-servers.status-ovhcloud.com/incidents/9y4sd9ly0lqb We’ll continue to monitor and update as the situation evolves.

3. 2 Kerzu 2025 da 15:25 UTCmonitoring

   Our monitoring system report all of the failing applications are healthy. We we will continue monitoring proactively.

4. 2 Kerzu 2025 da 15:56 UTCresolved

   Good news! Things should be back to normal again across the board. Please let us know if there is any further trouble. Thank you so much for your patience while we worked to sort this out.

1. 13 Du 2025 da 14:28 UTCinvestigating

   We're experiencing an increased rate of applications health errors currently looking into the issue.

2. 13 Du 2025 da 15:34 UTCmonitoring

   We have implemented a fix for this issue and are currently monitoring the results. We will update once we have confirmed it is resolved.

3. 13 Du 2025 da 16:04 UTCresolved

   We have some good news to share! Everything is now looking clear from our side and all users should be able to work with their applications without any interruptions. Please let us know at [email protected] if you are still experiencing problems. We apologize for disrupting your day and thank you for your patience.

1. 5 Du 2025 da 20:16 UTCinvestigating

   Our team is currently investigating the root cause of the issue.

2. 5 Du 2025 da 21:18 UTCmonitoring

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

3. 5 Du 2025 da 21:48 UTCresolved

   Issue is resolved and for more than 1 hour there are no reports for unhealthy applications.

1. 28 Here 2025 da 08:58 UTCinvestigating

   We are currently investigating this issue.

2. 28 Here 2025 da 09:04 UTCinvestigating

   We’ve identified that the ongoing connectivity issues

3. 28 Here 2025 da 09:05 UTCidentified

   We’ve identified that the ongoing connectivity issues affecting some services in our North America datacenter are due to scheduled maintenance on the vRack network infrastructure by OVHcloud. - Maintenance window: Oct 28, 2025, 08:00–10:00 UTC - Impact: Intermittent or total loss of vRack connectivity during the maintenance period. - Current state: Maintenance is still in progress on OVH’s side. - Reference: https://network.status-ovhcloud.com/incidents/pc33ftfc2xxq We are actively monitoring the situation and will update once connectivity is fully restored. Thank you for your patience and understanding.

4. 28 Here 2025 da 10:35 UTCmonitoring

   Our monitoring system report all of the failing applications are healthy. We we will continue monitoring proactively.

5. 28 Here 2025 da 11:05 UTCresolved

   Good news! Things should be back to normal again across the board. Please let us know if there is any further trouble. Thank you so much for your patience while we worked to sort this out.

1. 26 Here 2025 da 01:39 UTCinvestigating

   Our team is currently investigating the root cause of the issue.

2. 26 Here 2025 da 03:58 UTCmonitoring

   All applications have returned to healthy state. We will continue to monitor the situation.

3. 26 Here 2025 da 04:28 UTCresolved

   Good news! Things should be back to normal again across the board. Please let us know if there is any further trouble. Thank you so much for your patience while we worked to sort this out.

1. 2 Here 2025 da 23:18 UTCinvestigating

   We're experiencing an increased rate of applications health errors currently looking into the issue.

2. 3 Here 2025 da 00:21 UTCmonitoring

   Our monitoring system report all of the failing applications are healthy. We we will continue monitoring proactively.

3. 3 Here 2025 da 00:52 UTCresolved

   Issue is resolved and for more than 1 hour there are no reports for unhealthy applications.

1. 16 Gwengolo 2025 da 14:36 UTCinvestigating

   We're experiencing an increased rate of unhealthy applications. Currently we are looking into the issue.

2. 16 Gwengolo 2025 da 15:41 UTCmonitoring

   All applications have returned to healthy state. We will continue to monitor the situation.

3. 16 Gwengolo 2025 da 16:59 UTCmonitoring

   We have implemented a fix for this issue and are currently monitoring the results. We will update once we have confirmed it is resolved.

4. 16 Gwengolo 2025 da 17:29 UTCresolved

   Good news! Things should be back to normal again across the board. Please let us know if there is any further trouble. Thank you so much for your patience while we worked to sort this out.