Histórico de interrupções do Bunny

1. 3 Gwengolo 2026 da 13:47 UTCinvestigating

   Nossa equipe de engenharia está atualmente investigando um problema em nossa plataforma Stream de falhas de reprodução em nossos jogadores embarcados, bem como falhas de upload em nossa plataforma.

2. 3 Gwengolo 2026 da 14:00 UTCmonitoring

   Nós identificamos um problema de banco de dados de backend que causou um tempo limite em nossos servidores de vídeo (para incluir nosso player e processo de upload). O problema foi corrigido e estamos agora a acompanhar a situação.

3. 3 Gwengolo 2026 da 14:01 UTCmonitoring

   Estamos a observar algumas questões isoladas na parte de trás da solução. Estamos trabalhando para restaurar totalmente o processo em nossa plataforma.

4. 3 Gwengolo 2026 da 14:25 UTCmonitoring

   Confirmámos que todos os serviços foram totalmente retomados. Nossa equipe de Engenharia está atualmente monitorando a situação. O playback agora está totalmente retomado sem problemas. Os novos envios durante a falha falharam e, assim, precisariam de recarga. Os vídeos de transcodificação existentes não foram perdidos, porém o status relatado em alguns desses vídeos pode ser impreciso como resultado.

5. 3 Gwengolo 2026 da 15:38 UTCresolved

   Esta questão está agora totalmente resolvida. Nossa equipe de engenharia identificou guardas adicionais para evitar que essa questão específica aconteça no futuro.

Traduzido automaticamente da atualização oficial do incidente.

1. 3 Gwengolo 2026 da 08:53 UTCidentified

   Atualmente estamos observando degradação de desempenho com um provedor de trânsito de nível 1 na área de Los Angeles devido a cortes múltiplos de fibras em sua rede. Isso afetou a conectividade entre o cluster Bunny Optimizer LA e um pequeno número de CDN PoPs americanos. O tráfego foi redirecionado para minimizar o impacto.

2. 3 Gwengolo 2026 da 13:11 UTCresolved

   Este incidente foi resolvido.

Traduzido automaticamente da atualização oficial do incidente.

1. 2 Gwengolo 2026 da 14:38 UTCinvestigating

   Estamos a investigar relatórios de problemas de rede em Los Angeles que parecem estar a afectar os nossos serviços também. Estamos trabalhando com nossos fornecedores na área para entender a questão em questão e mitigar.

2. 2 Gwengolo 2026 da 15:51 UTCresolved

   Um incidente de rede mais amplo em Los Angeles impactou os Serviços Bunny hospedados na região. Os fornecedores de rede afectados atenuaram o incidente e todos os serviços afectados permaneceram estáveis desde então.

Traduzido automaticamente da atualização oficial do incidente.

1. 25 Eost 2026 da 14:06 UTCidentified

   Nós identificamos um problema com o nosso controlador de banco de dados, que nossa equipe de engenharia está trabalhando para restaurar. Bancos de dados já on-line não são afetados e continuarão operando normalmente, mas bancos de dados ociosos ou gerenciamento de banco de dados está atualmente indisponível.

2. 25 Eost 2026 da 16:01 UTCidentified

   Nossa equipe de engenharia continua trabalhando no assunto. Além disso, estamos cientes de que alguns bancos de dados de trabalho falham durante esta falha. Isso está relacionado e nossa equipe também está trabalhando para lidar com isso.

3. 25 Eost 2026 da 16:06 UTCmonitoring

   A questão foi resolvida e os serviços afectados foram restaurados. Nossa equipe de Engenharia continuará monitorando a plataforma para garantir que tudo permaneça estável.

4. 25 Eost 2026 da 22:31 UTCresolved

   Após o monitoramento dos serviços afetados, confirmamos que o gerenciamento do banco de dados e a ativação do banco de dados ocioso estão funcionando normalmente.

Traduzido automaticamente da atualização oficial do incidente.

1. 18 Eost 2026 da 02:28 UTCinvestigating

   Atualmente estamos investigando taxas de erro elevadas na API de armazenamento em nossa região de Londres, Reino Unido. Algumas operações da API podem ser afetadas como resultado.

2. 18 Eost 2026 da 04:09 UTCmonitoring

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

3. 18 Eost 2026 da 04:29 UTCresolved

   Este incidente foi resolvido.

Traduzido automaticamente da atualização oficial do incidente.

1. 23 Gouere 2026 da 08:33 UTCinvestigating

   Atualmente estamos investigando falhas intermitentes de reprodução em bibliotecas Stream, especificamente com o DRM Básico ativado. Isso não afeta o armazenamento subjacente existente, ou outros tipos de bibliotecas de vídeo (Enterprise DRM ou não DRM).

2. 23 Gouere 2026 da 09:02 UTCresolved

   Nós identificamos um processo em um único servidor causando falhas básicas de transformação DRM, e foi a causa de congelamentos de vídeo intermitentes / 500s. Isto foi rectificado pela equipa de engenharia.

Traduzido automaticamente da atualização oficial do incidente.

1. 17 Gouere 2026 da 10:57 UTCinvestigating

   Atualmente estamos investigando um problema onde os usuários não são capazes de fazer login no painel Bunny.net. Os serviços em si não são interrompidos.

2. 17 Gouere 2026 da 11:11 UTCresolved

   O problema de login agora foi resolvido após uma correção implantada pela nossa equipe Frontend.

Traduzido automaticamente da atualização oficial do incidente.

1. 1 Gouere 2026 da 09:45 UTCinvestigating

   We are currently investigating a Storage API incident on our German nodes. API Upload/List/Deletions may be affected as a result.

2. 1 Gouere 2026 da 09:53 UTCresolved

   We identified an failing database process on the Storage layer, which has now been resolved by our Engineering team.

1. 27 Mezheven 2026 da 18:57 UTCinvestigating

   We are currently investigating reports of issues affecting the dashboard and certain services. Our engineering team is actively investigating the situation. We will share more information as soon as it becomes available.

2. 27 Mezheven 2026 da 19:17 UTCmonitoring

   Between 18:34 and 18:57 UTC, a transient connectivity incident affecting one of our upstream providers impacted Storage services and the Core API in Europe. The issue has been resolved. No data loss occurred, as the incident was limited to network connectivity. We are actively monitoring the situation and are working with our upstream provider to gather additional details about the incident.

3. 27 Mezheven 2026 da 20:11 UTCresolved

   This incident has been resolved.

1. 26 Mezheven 2026 da 14:21 UTCinvestigating

   We are currently investigating an issue affecting Magic Containers and Databases. Our engineering team is actively working to identify the cause and restore normal service. Further updates will be provided as they become available.

2. 26 Mezheven 2026 da 14:29 UTCmonitoring

   Service has been restored and affected systems are operating normally. We are continuing to monitor the platform closely to confirm stability and ensure there are no remaining impacts.

3. 26 Mezheven 2026 da 14:57 UTCresolved

   This incident has been resolved.

1. 23 Mezheven 2026 da 13:22 UTCmonitoring

   We identified intermittent issues affecting the Shield API that may have caused occasional errors for some users. A fix has been implemented, and the service has returned to normal operation. We are currently monitoring to ensure continued stability.

2. 24 Mezheven 2026 da 03:11 UTCresolved

   This incident has been resolved.

1. 18 Mezheven 2026 da 20:57 UTCinvestigating

   We have identified an issue with free certificate issuance and renewals for custom CDN domains.

2. 18 Mezheven 2026 da 20:58 UTCidentified

   We identified that this is due to an issue currently experienced by the Let's Encrypt service. Existing certificates on custom domains will continue to function as normal - however new and cert renewals via our free certificate option may experience errors to the certificate issuance. You can follow https://letsencrypt.status.io/ for more details.

3. 19 Mezheven 2026 da 09:37 UTCresolved

   As per Lets Encrypt status page, this has been resolved - we similarly have observed no degradation/failures on certificate renewals since their update went out.

1. 15 Mezheven 2026 da 20:25 UTCinvestigating

   We are currently investigating reports of delays affecting synchronization and the propagation of configuration changes. Our team is actively investigating the issue and working to determine its scope and impact. We will provide additional updates as soon as more information becomes available.

2. 15 Mezheven 2026 da 20:45 UTCmonitoring

   Our team has identified the underlying cause of the issue and has implemented a fix. The affected processes are now recovering, and pending changes are continuing to propagate. As a result, some synchronization and configuration propagation delays may still be observed while the platform returns to normal operation. We are actively monitoring the recovery and will provide another update once processing has normalized.

3. 15 Mezheven 2026 da 21:24 UTCresolved

   All pending configuration changes have propagated across the CDN.

1. 3 Mezheven 2026 da 09:02 UTCidentified

   We have identified an issue on free cert issuance and renewals for custom CDN domains. We have observed a delay from Lets Encrypt API endpoint causing these delays. Existing certificates on custom domains will continue to function as normal - however new and cert renewals via our free certificate option may experience a delay to the certificate issuance.

2. 3 Mezheven 2026 da 12:38 UTCresolved

   We no longer see delays stemming from Lets Encrypt and the issue is considered resolved.

1. 1 Mezheven 2026 da 16:19 UTCinvestigating

   We are currently investigating a service degradation affecting Stream. Users may experience delays with video uploads, video fetching operations, and transcoding jobs. Playback, delivery, and management of existing videos are not affected and continue to operate normally. Our engineering team is actively working to identify the cause and restore full service. Further updates will be provided as they become available.

2. 1 Mezheven 2026 da 17:18 UTCmonitoring

   We are seeing normal processing resume for newly submitted video uploads and transcoding jobs. Some videos that entered processing during the incident may remain delayed. Our team is actively reviewing and working through the remaining affected jobs while continuing to monitor the service. Further updates will be provided as they become available.

3. 1 Mezheven 2026 da 20:17 UTCresolved

   This incident has been resolved.

1. 1 Mezheven 2026 da 16:02 UTCinvestigating

   We are currently investigating an issue affecting Magic Containers and Databases. Our engineering team is actively working to identify the cause and restore normal service. Further updates will be provided as they become available.

2. 1 Mezheven 2026 da 17:24 UTCmonitoring

   Service has been restored and affected systems are operating normally. We are continuing to monitor the platform closely to confirm stability and ensure there are no remaining impacts.

3. 1 Mezheven 2026 da 20:18 UTCresolved

   This incident has been resolved.

4. 3 Mezheven 2026 da 09:15 UTCpostmortem

   Processing Delays and Intermittent Timeouts for Magic Containers On June 1, Magic Containers experienced degraded service for approximately one hour due to a network connectivity issue in our hosting provider's environment. Customers running workloads may have seen increased processing delays, intermittent timeouts, temporary disruption, or reduced availability as some workloads were automatically rescheduled. The issue was resolved after the underlying network conditions stabilized, allowing scheduling activity to resume normally. We are improving the resilience of Magic Containers so degraded connectivity can be detected and handled more effectively, not only complete outages. We are also adding safeguards to reduce unnecessary or duplicate workload rescheduling during degraded conditions, helping limit customer impact if similar infrastructure issues occur again.

1. 1 Mezheven 2026 da 07:24 UTCinvestigating

   We're currently investigating an issue causing the Optimizer to serve a number of 5XX errors. We're investigating this as a matter of priority and we will provide updates here as soon as we can.

2. 1 Mezheven 2026 da 10:38 UTCresolved

   This incident has been resolved.

1. 26 Mae 2026 da 06:47 UTCidentified

   We've been observing 25 to 30 nodes in various PoPs around the world exhibiting constant delays with syncing their configuration since yesterday evening. We've depooled all impacted nodes as a temporary workaround and working on a permanent fix.

2. 26 Mae 2026 da 16:00 UTCmonitoring

   A fix is being staged on a subset of affected nodes. Impacted nodes are since identifying the issue isolated from CDN traffic and only receiving test traffic. Further updates will be provided after testing concludes and deployment to all affected nodes is complete.

3. 27 Mae 2026 da 11:15 UTCresolved

   The fix has been deployed to all nodes. We will be readding the missing nodes to the pool today.

1. 22 Mae 2026 da 11:19 UTCinvestigating

   As a continuation of our DNS issues last night, we are currently investigating an issue when newly CDN accelerating a DNS record results in CDN 502s for the domain in question. Existing pull zones and pull zones not created via CDN Acceleration are not affected. Existing CDN Accelerated zones are also not affected.

2. 22 Mae 2026 da 14:22 UTCidentified

   We have identified a discrepancy in our backend process that has caused zone id mismatch on new CDN Accelerated zones. The team are currently working to deploy a hotfix to address the problem.

3. 22 Mae 2026 da 19:03 UTCmonitoring

   A fix has been applied and we're now working through the backlog to process all pending updates. We expect processing to be back to real-time in the next 6 hours.

4. 23 Mae 2026 da 13:52 UTCresolved

   This incident has been resolved.

1. 21 Mae 2026 da 16:39 UTCidentified

   We've identified an issue with the configuration of one of our primary domains, bunny.net, impacting most of our services. We're working to fix it.

2. 21 Mae 2026 da 16:51 UTCmonitoring

   A fix has been implemented and all impacted services have recovered. We're monitoring.

3. 21 Mae 2026 da 18:21 UTCresolved

   An internal process failure related to the management of our bunny.net domain with one of our domain registrars led to the temporary suspension of the domain, causing multiple services under bunny.net to become unavailable. After identifying and confirming the issue, we worked with the registrar to restore the domain and all affected services are now recovering as DNS changes propagate globally. We have identified the root cause internally and are implementing additional safeguards and escalation procedures to ensure this cannot happen again. During the outage, products and services under bunny.net experienced varying levels of disruption depending on DNS propagation and their dependency on bunny.net infrastructure and Bunny DNS. Services including the Website, Dashboard, API, DNS, and related tools experienced widespread availability issues. Other products such as Stream and Magic Containers saw limited disruption and remained largely operational for most users, though some functionality was impacted depending on DNS resolution and service dependencies. Core services such as CDN delivery and Storage remained operational throughout the incident. We will publish a full public RCA once the incident is fully resolved, including additional details around the timeline, service impact, root cause, and the preventative measures being implemented. We're deeply sorry for the disruption and inconvenience caused. We expect the situation to fully resolve over the next few hours as DNS propagation completes worldwide. If you have any questions, please contact [email protected].