Störungsverlauf von Bunny

1. 3. September 2026 um 13:47 UTCinvestigating

   Unser Engineering-Team untersucht derzeit ein Problem auf unserer Stream-Plattform mit Wiedergabefehlern bei unseren Embedded-Playern sowie Upload-Ausfällen auf unserer Plattform.

2. 3. September 2026 um 14:00 UTCmonitoring

   Wir haben ein Backend-Datenbankproblem identifiziert, das zu einem Timeout auf unseren Videoservern geführt hat (um unseren Player und den Upload-Prozess einzubeziehen). Das Problem wurde behoben, und wir beobachten jetzt die Situation.

3. 3. September 2026 um 14:01 UTCmonitoring

   Wir beobachten einige isolierte Probleme auf der Rückseite des Fixes. Wir arbeiten daran, den Prozess auf unserer Plattform vollständig wiederherzustellen.

4. 3. September 2026 um 14:25 UTCmonitoring

   Wir haben bestätigt, dass alle Dienste vollständig wieder aufgenommen wurden. Unser Engineering-Team überwacht derzeit die Situation. Die Wiedergabe wurde nun vollständig ohne Probleme fortgesetzt. Neue Uploads während des Ausfalls sind fehlgeschlagen und müssten daher erneut hochgeladen werden. Bestehende Transcoding-Videos gingen nicht verloren, der Status, der auf einigen dieser Videos gemeldet wurde, kann jedoch ungenau sein.

5. 3. September 2026 um 15:38 UTCresolved

   Dieses Problem ist nun vollständig gelöst. Unser Engineering-Team hat zusätzliche Leitplanken identifiziert, um dieses spezielle Problem in Zukunft zu verhindern.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 3. September 2026 um 08:53 UTCidentified

   Wir beobachten derzeit Leistungseinbußen bei einem Tier-1-Transitanbieter in der Region Los Angeles aufgrund mehrerer Faserschnitte in ihrem Netzwerk. Dies hat die Konnektivität zwischen dem Bunny Optimizer LA Cluster und einer kleinen Anzahl von US CDN PoPs beeinflusst. Der Verkehr wurde umgeleitet, um die Auswirkungen zu minimieren.

2. 3. September 2026 um 13:11 UTCresolved

   Dieser Vorfall wurde behoben.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 2. September 2026 um 14:38 UTCinvestigating

   Wir untersuchen Berichte über weit verbreitete Netzwerkprobleme in Los Angeles, die sich auch auf unsere Dienste auswirken. Wir arbeiten mit unseren Anbietern in der Region zusammen, um das Problem zu verstehen und zu mildern.

2. 2. September 2026 um 15:51 UTCresolved

   Ein größerer Netzwerkvorfall in Los Angeles hat Bunny Services in der Region betroffen. Betroffene Netzwerkanbieter haben den Vorfall abgeschwächt und alle betroffenen Dienste sind seitdem stabil geblieben.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 25. August 2026 um 14:06 UTCidentified

   Wir haben ein Problem mit unserem Datenbankcontroller identifiziert, an dessen Wiederherstellung unser Engineering-Team arbeitet. Datenbanken, die bereits online sind, sind nicht betroffen und werden weiterhin normal funktionieren, aber im Leerlauf befindliche Datenbanken oder Datenbankverwaltung sind derzeit nicht verfügbar.

2. 25. August 2026 um 16:01 UTCidentified

   Unser Engineering-Team arbeitet weiter an dem Thema. Darüber hinaus sind wir uns bewusst, dass einige funktionierende Datenbanken während dieses Ausfalls ausfallen. Dies hängt damit zusammen und unser Team arbeitet auch daran, dies anzugehen.

3. 25. August 2026 um 16:06 UTCmonitoring

   Das Problem wurde behoben und die betroffenen Dienste wurden wiederhergestellt. Unser Engineering-Team wird die Plattform weiterhin überwachen, um sicherzustellen, dass alles stabil bleibt.

4. 25. August 2026 um 22:31 UTCresolved

   Nach der Überwachung der betroffenen Dienste haben wir bestätigt, dass die Datenbankverwaltung und die untätige Datenbankaktivierung normal funktionieren.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 18. August 2026 um 02:28 UTCinvestigating

   Wir untersuchen derzeit erhöhte Fehlerquoten bei der Storage API in unserer Region London, Großbritannien. Einige API-Operationen können dadurch betroffen sein.

2. 18. August 2026 um 04:09 UTCmonitoring

   Ein Fix wurde implementiert und wir überwachen die Ergebnisse.

3. 18. August 2026 um 04:29 UTCresolved

   Dieser Vorfall wurde behoben.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 23. Juli 2026 um 08:33 UTCinvestigating

   Wir untersuchen derzeit intermittierende Wiedergabefehler in Stream-Bibliotheken, insbesondere mit aktiviertem Basic DRM. Dies hat keine Auswirkungen auf bestehende zugrunde liegende Speicher oder andere Videobibliothekstypen (Enterprise DRM oder Nicht-DRM).

2. 23. Juli 2026 um 09:02 UTCresolved

   Wir haben einen Prozess auf einem einzelnen Server identifiziert, der grundlegende DRM-Transformationsfehler verursacht und die Ursache für intermittierende Video-Einfrierungen / 500s war. Dies wurde vom Engineering-Team behoben.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 17. Juli 2026 um 10:57 UTCinvestigating

   Wir untersuchen derzeit ein Problem, bei dem sich Benutzer nicht im Bunny.net-Dashboard anmelden können. Die Dienste selbst werden nicht gestört.

2. 17. Juli 2026 um 11:11 UTCresolved

   Das Login-Problem wurde nun nach einem von unserem Frontend-Team bereitgestellten Fix behoben.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 1. Juli 2026 um 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 um 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 um 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 um 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 um 20:11 UTCresolved

   This incident has been resolved.

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

   This incident has been resolved.

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

   This incident has been resolved.

1. 18. Juni 2026 um 20:57 UTCinvestigating

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

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

   All pending configuration changes have propagated across the CDN.

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

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

1. 1. Juni 2026 um 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 um 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 um 20:17 UTCresolved

   This incident has been resolved.

1. 1. Juni 2026 um 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 um 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 um 20:18 UTCresolved

   This incident has been resolved.

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

   This incident has been resolved.

1. 26. Mai 2026 um 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 um 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 um 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 um 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 um 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 um 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 um 13:52 UTCresolved

   This incident has been resolved.

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

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

3. 21. Mai 2026 um 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].