Historial de interrupciones de Bunny

1. 3 de septiembre de 2026 a las 13:47 UTCinvestigating

   Nuestro equipo de Ingeniería está actualmente investigando un problema en nuestra plataforma Stream de fallas de reproducción en nuestros jugadores integrados, así como subiendo fallas en nuestra plataforma.

2. 3 de septiembre de 2026 a las 14:00 UTCmonitoring

   Hemos identificado un problema de base de datos de backend que había causado un timeout en nuestros servidores de vídeo (para incluir a nuestro reproductor y el proceso de carga). El problema fue rectificado y ahora estamos monitoreando la situación.

3. 3 de septiembre de 2026 a las 14:01 UTCmonitoring

   Estamos observando algunos problemas aislados en la parte posterior de la solución. Estamos trabajando para restaurar completamente el proceso en nuestra plataforma.

4. 3 de septiembre de 2026 a las 14:25 UTCmonitoring

   Hemos confirmado que todos los servicios se han reanudado totalmente. Nuestro equipo de Ingeniería está monitoreando la situación. Playback se ha reanudado completamente sin problemas. Las nuevas cargas durante la salida han fracasado y por lo tanto necesitarían recargarse. No se perdieron videos de transcodificación existentes, sin embargo el estado reportado en algunos de estos videos puede ser inexacto como resultado.

5. 3 de septiembre de 2026 a las 15:38 UTCresolved

   Esta cuestión ya está plenamente resuelta. Nuestro equipo de Ingeniería ha identificado custodios adicionales para evitar que este problema específico suceda en el futuro.

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

1. 3 de septiembre de 2026 a las 8:53 UTCidentified

   Actualmente observamos la degradación del rendimiento con un proveedor de tránsito Tier 1 en el área de Los Ángeles debido a múltiples cortes de fibra en su red. Esto ha impactado la conectividad entre el clúster LA de Bunny Optimizer y un pequeño número de PoPs CDN estadounidenses. El tráfico ha sido redirigido para minimizar el impacto.

2. 3 de septiembre de 2026 a las 13:11 UTCresolved

   Este incidente ha sido resuelto.

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

1. 2 de septiembre de 2026 a las 14:38 UTCinvestigating

   Estamos investigando informes de problemas de red en Los Ángeles que parecen estar impactando nuestros servicios también. Trabajamos con nuestros proveedores en la zona para comprender el tema que nos ocupa y mitigar.

2. 2 de septiembre de 2026 a las 15:51 UTCresolved

   Un incidente de red más amplio en Los Ángeles impactó a Bunny Services hospedado en la región. Los proveedores de redes afectados han mitigado el incidente y todos los servicios afectados han permanecido estables desde entonces.

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

1. 25 de agosto de 2026 a las 14:06 UTCidentified

   Hemos identificado un problema con nuestro controlador de base de datos, que nuestro equipo de ingeniería está trabajando para restaurar. Las bases de datos ya en línea no están afectadas y continuarán operando normalmente, pero las bases de datos o la gestión de bases de datos ociosos no están disponibles.

2. 25 de agosto de 2026 a las 16:01 UTCidentified

   Nuestro equipo de ingeniería sigue trabajando en el tema. Además, somos conscientes de que algunas bases de datos de trabajo fallan durante este outage. Esto está relacionado y nuestro equipo también está trabajando para abordar esto.

3. 25 de agosto de 2026 a las 16:06 UTCmonitoring

   Se ha resuelto la cuestión y se han restablecido los servicios afectados. Nuestro equipo de ingeniería seguirá monitoreando la plataforma para asegurar que todo siga siendo estable.

4. 25 de agosto de 2026 a las 22:31 UTCresolved

   Después de supervisar los servicios afectados, hemos confirmado que la gestión de bases de datos y la activación de idle Database funcionan normalmente.

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

1. 18 de agosto de 2026 a las 2:28 UTCinvestigating

   Actualmente estamos investigando tasas de error elevadas en la API de almacenamiento en nuestra región de Londres, Reino Unido. Algunas operaciones de API pueden verse afectadas como resultado.

2. 18 de agosto de 2026 a las 4:09 UTCmonitoring

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

3. 18 de agosto de 2026 a las 4:29 UTCresolved

   Este incidente ha sido resuelto.

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

1. 23 de julio de 2026 a las 8:33 UTCinvestigating

   Actualmente estamos investigando fallos de reproducción intermitentes en las bibliotecas Stream, específicamente con Básico DRM habilitado. Esto no afecta el almacenamiento subyacente existente, u otros tipos de videoteca (Enterprise DRM o no DRM).

2. 23 de julio de 2026 a las 9:02 UTCresolved

   Hemos identificado un proceso en un solo servidor causando fallas de transformación Básica de DRM, y fue la causa de congelaciones de vídeo intermitentes/500s. Esto ha sido rectificado por el equipo de Ingeniería.

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

1. 17 de julio de 2026 a las 10:57 UTCinvestigating

   Actualmente estamos investigando un problema donde los usuarios son incapaces de iniciar sesión en el dashboard de Bunny.net. Los propios servicios no se interrumpen.

2. 17 de julio de 2026 a las 11:11 UTCresolved

   El número de inicio de sesión se ha resuelto después de una solución implementada por nuestro equipo Frontend.

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

1. 1 de julio de 2026 a las 9: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 de julio de 2026 a las 9:53 UTCresolved

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

1. 27 de junio de 2026 a las 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 de junio de 2026 a las 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 de junio de 2026 a las 20:11 UTCresolved

   This incident has been resolved.

1. 26 de junio de 2026 a las 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 de junio de 2026 a las 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 de junio de 2026 a las 14:57 UTCresolved

   This incident has been resolved.

1. 23 de junio de 2026 a las 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 de junio de 2026 a las 3:11 UTCresolved

   This incident has been resolved.

1. 18 de junio de 2026 a las 20:57 UTCinvestigating

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

2. 18 de junio de 2026 a las 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 de junio de 2026 a las 9: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 de junio de 2026 a las 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 de junio de 2026 a las 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 de junio de 2026 a las 21:24 UTCresolved

   All pending configuration changes have propagated across the CDN.

1. 3 de junio de 2026 a las 9: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 de junio de 2026 a las 12:38 UTCresolved

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

1. 1 de junio de 2026 a las 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 de junio de 2026 a las 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 de junio de 2026 a las 20:17 UTCresolved

   This incident has been resolved.

1. 1 de junio de 2026 a las 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 de junio de 2026 a las 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 de junio de 2026 a las 20:18 UTCresolved

   This incident has been resolved.

4. 3 de junio de 2026 a las 9: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 de junio de 2026 a las 7: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 de junio de 2026 a las 10:38 UTCresolved

   This incident has been resolved.

1. 26 de mayo de 2026 a las 6: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 de mayo de 2026 a las 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 de mayo de 2026 a las 11:15 UTCresolved

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

1. 22 de mayo de 2026 a las 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 de mayo de 2026 a las 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 de mayo de 2026 a las 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 de mayo de 2026 a las 13:52 UTCresolved

   This incident has been resolved.

1. 21 de mayo de 2026 a las 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 de mayo de 2026 a las 16:51 UTCmonitoring

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

3. 21 de mayo de 2026 a las 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].