Istoricul incidentelor Bunny

1. 3 septembrie 2026 la 13:47 UTCinvestigating

   Echipa noastră de Inginerie investighează în prezent o problemă pe platforma noastră Stream de eșecuri de redare pe jucătorii noștri integrați, precum și eșecuri de încărcare pe platforma noastră.

2. 3 septembrie 2026 la 14:00 UTCmonitoring

   Am identificat o problemă de bază de date care a cauzat un timeout pe serverele noastre video (pentru a include jucătorul nostru și procesul de încărcare). Problema a fost remediată şi acum monitorizăm situaţia.

3. 3 septembrie 2026 la 14:01 UTCmonitoring

   Observăm nişte probleme izolate în spate. Lucrăm pentru a restabili pe deplin procesul de pe platforma noastră.

4. 3 septembrie 2026 la 14:25 UTCmonitoring

   Am confirmat că toate serviciile au fost reluate complet. Echipa noastră de ingineri monitorizează situaţia. Redarea a fost reluată fără probleme. Noi upload-uri în timpul întreruperii au eșuat și, prin urmare, ar trebui reîncărcată. Videoclipurile transcoding existente nu au fost pierdute, însă statutul raportat pe unele dintre aceste videoclipuri poate fi inexact ca rezultat.

5. 3 septembrie 2026 la 15:38 UTCresolved

   Această problemă este acum pe deplin rezolvată. Echipa noastră de Inginerie a identificat balustrade suplimentare pentru a preveni această problemă specifică să se întâmple în viitor.

Traducere automată din actualizarea oficială a incidentului.

1. 3 septembrie 2026 la 08:53 UTCidentified

   În prezent observăm degradarea performanței cu un furnizor de tranzit de nivel 1 în zona Los Angeles din cauza tăierilor multiple de fibre pe rețeaua lor. Acest lucru a afectat conectivitatea dintre grupul Bunny Optimizer LA și un număr mic de US CDN PoP. Traficul a fost redirecţionat pentru a minimiza impactul.

2. 3 septembrie 2026 la 13:11 UTCresolved

   Acest incident a fost rezolvat.

Traducere automată din actualizarea oficială a incidentului.

1. 2 septembrie 2026 la 14:38 UTCinvestigating

   Investigăm rapoarte de probleme de rețea pe scară largă în Los Angeles care par a fi impactul serviciilor noastre, de asemenea. Lucrăm cu furnizorii noștri din zonă pentru a înțelege problema în cauză și a atenua problema.

2. 2 septembrie 2026 la 15:51 UTCresolved

   Un incident de rețea mai larg în Los Angeles a afectat Bunny Services găzduit în regiune. Furnizorii de rețele afectați au atenuat incidentul și toate serviciile afectate au rămas stabile de atunci.

Traducere automată din actualizarea oficială a incidentului.

1. 25 august 2026 la 14:06 UTCidentified

   Am identificat o problemă cu controlorul bazei noastre de date, pe care echipa noastră de inginerie lucrează pentru a o restabili. Baza de date deja online nu este afectată și va continua să funcționeze normal, dar bazele de date inactive sau gestionarea bazelor de date nu sunt disponibile în prezent.

2. 25 august 2026 la 16:01 UTCidentified

   Echipa noastră de ingineri continuă să lucreze la această problemă. În plus, suntem conștienți de unele baze de date de lucru care nu funcționează în timpul acestei întreruperi. Acest lucru este legat și echipa noastră sunt, de asemenea, de lucru pentru a aborda acest lucru.

3. 25 august 2026 la 16:06 UTCmonitoring

   Problema a fost rezolvată, iar serviciile afectate au fost restaurate. Echipa noastră de Inginerie va continua monitorizarea platformei pentru a se asigura că totul rămâne stabil.

4. 25 august 2026 la 22:31 UTCresolved

   După monitorizarea serviciilor afectate, am confirmat că gestionarea bazei de date și activarea bazei de date inactive funcționează în mod normal.

Traducere automată din actualizarea oficială a incidentului.

1. 18 august 2026 la 02:28 UTCinvestigating

   Investigăm în prezent rate ridicate de eroare în ceea ce priveşte API-ul de stocare din regiunea noastră Londra, Marea Britanie. Unele operațiuni API pot fi afectate ca urmare.

2. 18 august 2026 la 04:09 UTCmonitoring

   A fost implementată o soluţie şi monitorizăm rezultatele.

3. 18 august 2026 la 04:29 UTCresolved

   Acest incident a fost rezolvat.

Traducere automată din actualizarea oficială a incidentului.

1. 23 iulie 2026 la 08:33 UTCinvestigating

   Investigăm în prezent eșecuri intermitente de redare pe biblioteci Stream, în special cu DRM de bază activat. Acest lucru nu are impact asupra stocării existente sau asupra altor tipuri de biblioteci video (Enterprise DRM sau non DRM).

2. 23 iulie 2026 la 09:02 UTCresolved

   Am identificat un proces pe un singur server care cauzează eșecuri de transformare Bază DRM, și a fost cauza înghețări video intermitente / 500s. Acest lucru a fost rectificat de echipa de inginerie.

Traducere automată din actualizarea oficială a incidentului.

1. 17 iulie 2026 la 10:57 UTCinvestigating

   Investigăm o problemă în care utilizatorii nu se pot conecta la tabloul de bord Bunny.net. Serviciile nu sunt perturbate.

2. 17 iulie 2026 la 11:11 UTCresolved

   Problema autentificării a fost rezolvată în urma unei fixări desfăşurate de echipa noastră de la Frontend.

Traducere automată din actualizarea oficială a incidentului.

1. 1 iulie 2026 la 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 iulie 2026 la 09:53 UTCresolved

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

1. 27 iunie 2026 la 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 iunie 2026 la 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 iunie 2026 la 20:11 UTCresolved

   This incident has been resolved.

1. 26 iunie 2026 la 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 iunie 2026 la 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 iunie 2026 la 14:57 UTCresolved

   This incident has been resolved.

1. 23 iunie 2026 la 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 iunie 2026 la 03:11 UTCresolved

   This incident has been resolved.

1. 18 iunie 2026 la 20:57 UTCinvestigating

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

2. 18 iunie 2026 la 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 iunie 2026 la 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 iunie 2026 la 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 iunie 2026 la 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 iunie 2026 la 21:24 UTCresolved

   All pending configuration changes have propagated across the CDN.

1. 3 iunie 2026 la 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 iunie 2026 la 12:38 UTCresolved

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

1. 1 iunie 2026 la 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 iunie 2026 la 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 iunie 2026 la 20:17 UTCresolved

   This incident has been resolved.

1. 1 iunie 2026 la 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 iunie 2026 la 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 iunie 2026 la 20:18 UTCresolved

   This incident has been resolved.

4. 3 iunie 2026 la 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 iunie 2026 la 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 iunie 2026 la 10:38 UTCresolved

   This incident has been resolved.

1. 26 mai 2026 la 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 mai 2026 la 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 mai 2026 la 11:15 UTCresolved

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

1. 22 mai 2026 la 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 mai 2026 la 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 mai 2026 la 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 mai 2026 la 13:52 UTCresolved

   This incident has been resolved.

1. 21 mai 2026 la 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 mai 2026 la 16:51 UTCmonitoring

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

3. 21 mai 2026 la 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].