Bunny driftsforstyrrelser

1. 3. september 2026 kl. 13.47 UTCinvestigating

   Vores Engineering team er i øjeblikket at undersøge et problem på vores Stream platform af afspilningsfejl på vores indlejrede spillere, samt uploade fejl til vores platform.

2. 3. september 2026 kl. 14.00 UTCmonitoring

   Vi har identificeret en backend database problem, som havde forårsaget en timeout på tværs af vores video servere (at inkludere vores spiller og upload proces). Problemet blev løst, og vi overvåger nu situationen.

3. 3. september 2026 kl. 14.01 UTCmonitoring

   Vi observerer nogle isolerede problemer på bagsiden af fixet. Vi arbejder på fuldt ud at genoprette processen på vores platform.

4. 3. september 2026 kl. 14.25 UTCmonitoring

   Vi har bekræftet, at alle tjenester er fuldt ud genoptaget. Vores ingeniørhold overvåger situationen. Playback er nu helt genoptaget uden problemer. Nye uploads under udslippet har slået fejl og vil derfor kræve genupload. Eksisterende transkodning videoer blev ikke tabt, men status rapporteret på nogle af disse videoer kan være unøjagtige som et resultat.

5. 3. september 2026 kl. 15.38 UTCresolved

   Dette spørgsmål er nu helt løst. Vores ingeniørhold har identificeret ekstra vagter for at forhindre dette specifikke problem i at ske i fremtiden.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 3. september 2026 kl. 08.53 UTCidentified

   Vi observerer i øjeblikket forringelse af ydeevnen med en Tier 1 transitudbyder i Los Angeles området på grund af flere fiber nedskæringer på deres netværk. Dette har påvirket forbindelsen mellem Bunny Optimizer LA klyngen og et lille antal amerikanske CDN POPs. Trafikken er blevet omdirigeret for at minimere virkningen.

2. 3. september 2026 kl. 13.11 UTCresolved

   Denne hændelse er blevet løst.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 2. september 2026 kl. 14.38 UTCinvestigating

   Vi efterforsker rapporter om udbredte netværksproblemer i Los Angeles, som også påvirker vores tjenester. Vi arbejder sammen med vores udbydere på området for at forstå og afbøde problemet.

2. 2. september 2026 kl. 15.51 UTCresolved

   Et bredere netværk hændelse i Los Angeles påvirket Bunny Services hosted i regionen. Berørte netværksudbydere har afhjulpet hændelsen, og alle berørte tjenester har været stabile siden da.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 25. august 2026 kl. 14.06 UTCidentified

   Vi har identificeret et problem med vores Database controller, at vores Engineering team arbejder på at genoprette. Databaser allerede online er ikke påvirket og vil fortsætte med at fungere normalt, men tomgang Databaser eller Database management er i øjeblikket ikke tilgængelig.

2. 25. august 2026 kl. 16.01 UTCidentified

   Vores ingeniørhold arbejder videre med sagen. Derudover er vi klar over, at nogle arbejdsdatabaser svigter under denne afbrydelse. Dette er relateret, og vores team arbejder også på at løse dette.

3. 25. august 2026 kl. 16.06 UTCmonitoring

   Spørgsmålet er blevet løst, og de berørte tjenester er blevet genoprettet. Vores ingeniørhold vil fortsætte med at overvåge platformen for at sikre, at alt forbliver stabilt.

4. 25. august 2026 kl. 22.31 UTCresolved

   Efter overvågning af de berørte tjenester, har vi bekræftet, at Database management og tomgang Database aktivering fungerer normalt.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 18. august 2026 kl. 02.28 UTCinvestigating

   Vi er i øjeblikket undersøge forhøjede fejlrater på Storage API i vores London, UK region. Nogle API-operationer kan blive påvirket som et resultat.

2. 18. august 2026 kl. 04.09 UTCmonitoring

   Et fix er blevet gennemført, og vi overvåger resultaterne.

3. 18. august 2026 kl. 04.29 UTCresolved

   Denne hændelse er blevet løst.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 23. juli 2026 kl. 08.33 UTCinvestigating

   Vi er i øjeblikket ved at undersøge intermitterende afspilningsfejl på Stream biblioteker, specielt med Basic DRM aktiveret. Dette påvirker ikke eksisterende underliggende lagring eller andre former for videobibliotek (Enterprise DRM eller ikke DRM).

2. 23. juli 2026 kl. 09.02 UTCresolved

   Vi har identificeret en proces på en enkelt server forårsager grundlæggende DRM transformation fejl, og var årsag til intermitterende video fryser / 500s. Dette er blevet rettet af ingeniørholdet.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 17. juli 2026 kl. 10.57 UTCinvestigating

   Vi undersøger i øjeblikket et problem, hvor brugerne ikke kan logge ind på Bunny.net instrumentbrættet. Tjenester i sig selv forstyrres ikke.

2. 17. juli 2026 kl. 11.11 UTCresolved

   Login problemet er nu blevet løst efter et fix indsat af vores Frontend team.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 1. juli 2026 kl. 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. juli 2026 kl. 09.53 UTCresolved

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

1. 27. juni 2026 kl. 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. juni 2026 kl. 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. juni 2026 kl. 20.11 UTCresolved

   This incident has been resolved.

1. 26. juni 2026 kl. 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. juni 2026 kl. 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. juni 2026 kl. 14.57 UTCresolved

   This incident has been resolved.

1. 23. juni 2026 kl. 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. juni 2026 kl. 03.11 UTCresolved

   This incident has been resolved.

1. 18. juni 2026 kl. 20.57 UTCinvestigating

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

2. 18. juni 2026 kl. 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. juni 2026 kl. 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. juni 2026 kl. 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. juni 2026 kl. 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. juni 2026 kl. 21.24 UTCresolved

   All pending configuration changes have propagated across the CDN.

1. 3. juni 2026 kl. 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. juni 2026 kl. 12.38 UTCresolved

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

1. 1. juni 2026 kl. 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. juni 2026 kl. 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. juni 2026 kl. 20.17 UTCresolved

   This incident has been resolved.

1. 1. juni 2026 kl. 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. juni 2026 kl. 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. juni 2026 kl. 20.18 UTCresolved

   This incident has been resolved.

4. 3. juni 2026 kl. 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. juni 2026 kl. 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. juni 2026 kl. 10.38 UTCresolved

   This incident has been resolved.

1. 26. maj 2026 kl. 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. maj 2026 kl. 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. maj 2026 kl. 11.15 UTCresolved

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

1. 22. maj 2026 kl. 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. maj 2026 kl. 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. maj 2026 kl. 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. maj 2026 kl. 13.52 UTCresolved

   This incident has been resolved.

1. 21. maj 2026 kl. 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. maj 2026 kl. 16.51 UTCmonitoring

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

3. 21. maj 2026 kl. 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].