Bunny kesinti geçmişi

1. 3 Eylül 2026 13:47 UTCinvestigating

   Mühendislik ekibimiz şu anda gömülü oyuncularımızdaki oyun geri dönüşüm başarısızlıkları konusunda bir sorun araştırıyor ve platformumuza başarısızlıklar yükleniyor.

2. 3 Eylül 2026 14:00 UTCmonitoring

   Video sunucularımız arasında bir süre boyunca yol açan bir arka uç veritabanı sorunu tespit ettik ( oyuncumuzu dahil etmek ve süreç yüklemek). Sorun düzeltildi ve şimdi durumu takip ediyoruz.

3. 3 Eylül 2026 14:01 UTCmonitoring

   Bazı izole sorunları düzeltmenin arkasında gözlemliyoruz. Platformumuzdaki süreci tamamen restore etmeye çalışıyoruz.

4. 3 Eylül 2026 14:25 UTCmonitoring

   Tüm hizmetlerin tamamen yeniden başladığını doğruladık. Mühendislik ekibimiz şu anda durumu izliyor. Playback şimdi tamamen sorun olmadan yeniden başladı. Outage sırasında yeni yüklemeler başarısız oldu ve bu nedenle yeniden yapılacaktı. Mevcut transkript videoları kaybolmadı, ancak bu videoların bazılarında bildirilen durum bir sonuç olarak yanlış olabilir.

5. 3 Eylül 2026 15:38 UTCresolved

   Bu konu şimdi tamamen çözülmüştür. Mühendislik ekibimiz, bu özel meselenin gelecekte gerçekleşmesini önlemek için ek bekçileri tespit etti.

Resmî olay güncellemesinden otomatik olarak çevrilmiştir.

1. 3 Eylül 2026 08:53 UTCidentified

   Şu anda Los Angeles bölgesinde bir Tier 1 transit sağlayıcı ile performans bozulmasını, ağlarında birden fazla fiber kesinti nedeniyle gözlemliyoruz. Bu, Bunny Optimizer LA grubu ve az sayıda ABD CDN PoPs arasındaki bağlantıyı etkiledi. Trafik etkisini en aza indirmek için geri getirildi.

2. 3 Eylül 2026 13:11 UTCresolved

   Bu olay çözüldü.

Resmî olay güncellemesinden otomatik olarak çevrilmiştir.

1. 2 Eylül 2026 14:38 UTCinvestigating

   Los Angeles'taki yaygın ağ sorunlarının raporlarını araştırıyoruz, hizmetlerimizi de etkiliyor gibi görünüyor. Sorunu el ve hafifletebilmek için bölgedeki sağlayıcılarımızla çalışıyoruz.

2. 2 Eylül 2026 15:51 UTCresolved

   Los Angeles'ta daha geniş bir ağ olayı, bölgede barındırılan Bunny Hizmetleri etkiledi. Etkilenen ağ sağlayıcıları olayı hafifletti ve tüm etkilenen hizmetler o zamandan beri stabil kaldı.

Resmî olay güncellemesinden otomatik olarak çevrilmiştir.

1. 25 Ağustos 2026 14:06 UTCidentified

   Veritabanı kontrolörümüzle ilgili bir sorunu tespit ettik, Mühendislik ekibimizin geri yüklemek için çalıştığını. Veritabanı zaten online etkilenmez ve normalde çalışmaya devam edecektir, ancak idle Databases veya Veritabanı yönetimi şu anda mevcut değildir.

2. 25 Ağustos 2026 16:01 UTCidentified

   Mühendislik ekibimiz konu üzerinde çalışmaya devam ediyor. Ayrıca, bu kesinti sırasında bazı çalışma veritabanlarının başarısız olduğunu biliyoruz. Bu ilgili ve ekibimiz de bunu ele almak için çalışıyor.

3. 25 Ağustos 2026 16:06 UTCmonitoring

   Sorun çözüldü ve etkilenen hizmetler restore edildi. Mühendislik ekibimiz her şeyin istikrarlı kalmasını sağlamak için platformu izlemeye devam edecektir.

4. 25 Ağustos 2026 22:31 UTCresolved

   Etkilenen hizmetleri izledikten sonra, Veritabanı yönetiminin ve idle Database aktivasyonunun normalde çalıştığını doğruladık.

Resmî olay güncellemesinden otomatik olarak çevrilmiştir.

1. 18 Ağustos 2026 02:28 UTCinvestigating

   Şu anda Londra, İngiltere bölgemizde Storage API'sinde yüksek hata oranları araştırıyoruz. Bazı API operasyonları bir sonuç olarak etkilenebilir.

2. 18 Ağustos 2026 04:09 UTCmonitoring

   Bir düzeltme uygulandı ve sonuçları takip ediyoruz.

3. 18 Ağustos 2026 04:29 UTCresolved

   Bu olay çözüldü.

Resmî olay güncellemesinden otomatik olarak çevrilmiştir.

1. 23 Temmuz 2026 08:33 UTCinvestigating

   Şu anda Stream kütüphanelerinde geçici oyun başarısızlıklarını araştırıyoruz, özellikle Temel DRM etkinleştirildi. Bu mevcut alt depolamayı veya diğer video kütüphane türlerini etkilemez (Enterprise DRM veya DRM olmayan).

2. 23 Temmuz 2026 09:02 UTCresolved

   Temel DRM dönüşüm başarısızlıklarına neden olan tek bir sunucuda bir süreç tespit ettik ve intermittent video dons/500s nedeniydik. Bu, Mühendislik ekibi tarafından düzeltilmiştir.

Resmî olay güncellemesinden otomatik olarak çevrilmiştir.

1. 17 Temmuz 2026 10:57 UTCinvestigating

   Şu anda kullanıcıların Bunny.net paniğe giremeyeceği bir sorunu araştırıyoruz. Hizmetler kendilerini bozmaz.

2. 17 Temmuz 2026 11:11 UTCresolved

   Giriş sorunu şimdi Frontend ekibimiz tarafından dağıtılan bir düzeltme sonrasında çözüldü.

Resmî olay güncellemesinden otomatik olarak çevrilmiştir.

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

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

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

   This incident has been resolved.

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

   This incident has been resolved.

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

   This incident has been resolved.

1. 18 Haziran 2026 20:57 UTCinvestigating

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

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

   All pending configuration changes have propagated across the CDN.

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

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

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

   This incident has been resolved.

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

   This incident has been resolved.

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

   This incident has been resolved.

1. 26 Mayıs 2026 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 Mayıs 2026 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 Mayıs 2026 11:15 UTCresolved

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

1. 22 Mayıs 2026 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 Mayıs 2026 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 Mayıs 2026 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 Mayıs 2026 13:52 UTCresolved

   This incident has been resolved.

1. 21 Mayıs 2026 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 Mayıs 2026 16:51 UTCmonitoring

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

3. 21 Mayıs 2026 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].