Official incident history

  1. Performance degradation in DE

    Started: · Duration: 118 min
    Provider updates (3)
    1. Investigating “We are currently investigating this issue affecting the CDN performance in DE.”
    2. Monitoring “We've found and resolved the issue and are actively monitoring performance.”
    3. Resolved “This incident has been resolved, we're not observing performance issues anymore.”
    Resolved
  2. Storage operations in DE and Stream uploads performance degradation

    Started: · Duration: 790 min
    Provider updates (3)
    1. Investigating “We're currently investigating intermittent issues when listing/uploading to Storage zones in DE and failed uploads in Stream.”
    2. Monitoring “A fix has been implemented and we are monitoring the results.”
    3. Resolved “This issue has now been resolved.”
    Resolved
  3. Network issues in Frankfurt

    Started: · Duration: 631 min
    Provider updates (2)
    1. Monitoring “We are investigating a network issue that lasted approximately 10 minutes and affected the availability of the Frankfurt Storage, Magic Containers, Bunny Database and CDN regions”
    2. Resolved “Root Cause behind this incident was a core network outage on one of our major Frankfurt providers that made a large number of Bunny servers in Frankfurt unreachable between 02:36 and 02:44 UTC. We haven't observed any further issues since 02:44 UTC, nor expect any further issues due to this and will be resolving this incident at this time.”
    Resolved
  4. Database Performance Degradation

    Started: · Duration: 743 min
    Provider updates (3)
    1. Investigating “We are currently investigating Database performance degradation in some regions, our Engineering team are currently investigating root cause.”
    2. Monitoring “Our Engineering team has identified a process load issue which has now been resolved. The team are now monitoring the situation”
    3. Resolved “This incident has now been resolved.”
    Resolved
  5. CDN Log forwarding performance degradation

    Started: · Duration: 597 min
    Provider updates (3)
    1. Investigating “We're investigating performance degradation within our CDN Logging infrastructure, impacting our CDN Logging offering.”
    2. Monitoring “A suboptimal log query had put a lot of load to an infrastructure component affecting performance of the whole system. The query has been isolated. We're observing better throughput, but will be monitoring the situation for the next few hours.”
    3. Resolved “This incident has been resolved”
    Resolved
  6. Degraded Optimizer Response times

    Started: · Duration: 145 min
    Provider updates (2)
    1. Investigating “We are currently investigating degraded optimizer processing, causing increased latency in serving assets on CDN. This issue sits under image transformation and asset compression only.”
    2. Resolved “A subset of optimizer workers exhibited disk performance issues, impacting Optimizer software's throughput. A fix has been deployed to all servers sharing this same hardware model and performance is back at normal levels again.”
    Resolved
  7. Intermittent Login/API Timeouts in Poland

    Started: · Duration: 30 min
    Provider updates (2)
    1. Investigating “We are currently investigating intermittent timeouts with Bunny dashboard access (Login) and API responses within Poland”
    2. Resolved “Network performance issues caused by an upstream provider have been mitigated via traffic rerouting. All services and connection timeouts have returned to normal.”
    Resolved
  8. CDN Synchronization Delays

    Started: · Duration: 199 min
    Provider updates (3)
    1. Investigating “We are currently investigating an issue causing synchronization delays across our CDN. Our team is actively working to identify the cause and restore normal operations. We will provide further updates as more information becomes available. We apologize for any inconvenience this may cause.”
    2. Monitoring “The synchronization delays have been resolved, and normal operations have been restored. We will continue monitoring the service to ensure everything remains stable.”
    3. Resolved “This incident has been resolved.”
    Resolved
  9. Increased encoding processing time

    Started: · Duration: 5086 min
    Provider updates (3)
    1. Identified “We have been made aware of increased processing time in video encoding queues. We're working on alleviating the underlying issue.”
    2. Monitoring “We have noted improvement in transcoding process delays, and are monitoring the situation.”
    3. Resolved “Video encoding delays have now been fully resolved.”
    Resolved
  10. Payment Gateway Failures on Dashboard

    Started: · Duration: 157 min
    Provider updates (3)
    1. Identified “We are currently aware of an issue of failed payment attempts on our billing dashboard on user accounts. Our team are working to restore its functionality.”
    2. Monitoring “A fix has been deployed for the issue affecting payment attempts on the billing dashboard. The service has been restored, and we are currently monitoring the situation to ensure everything continues to operate as expected.”
    3. Resolved “The issue affecting payment attempts on the billing dashboard has been resolved. Our monitoring has confirmed that the service is operating normally.”
    Resolved
  11. Video Playback and Encoding Failures on Bunny Stream

    Started: · Duration: 111 min
    Provider updates (3)
    1. Investigating “Our Engineering team are currently investigating an issue on our Stream platform of playback failures on our embedded players, as well as upload failures to our platform.”
    2. Monitoring “We have identified a backend database issue which had caused a timeout across our video servers (to include our player and uploading process). The problem was rectified and we are now monitoring the situation.”
    3. Resolved “This issue is now fully resolved. Our Engineering team have identified additional guardrails to prevent this specific issue from happening in future.”
    Resolved
  12. Network issues in Los Angeles

    Started: · Duration: 258 min
    Provider updates (2)
    1. Identified “We are currently observing performance degradation with a Tier 1 transit provider in the Los Angeles area due to multiple fiber cuts on their network. This has impacted connectivity between the Bunny Optimizer LA cluster and a small number of US CDN PoPs. Traffic has been rerouted to minimize the impact.”
    2. Resolved “This incident has been resolved.”
    Resolved
  13. Network issues in Los Angeles

    Started: · Duration: 72 min
    Provider updates (2)
    1. Investigating “We're investigating reports of widespread network issues in Los Angeles that seem to be impacting our services as well. We are working with our providers in the area to understand the issue at hand and mitigate.”
    2. Resolved “A wider network incident in Los Angeles impacted Bunny Services hosted in the region. Affected network providers have mitigated the incident and all impacted services have remained stable since then.”
    Resolved
  14. Database Controller Outage

    Started: · Duration: 504 min
    Provider updates (3)
    1. Identified “We have identified an issue with our Database controller, that our Engineering team are working to restore. Databases already online are not affected and will continue operating normally, but idle Databases or Database management is currently unavailable.”
    2. Monitoring “The issue has been resolved and the affected services have been restored. Our Engineering team will continue monitoring the platform to ensure everything remains stable.”
    3. Resolved “After monitoring the affected services, we have confirmed that Database management and idle Database activation are operating normally.”
    Resolved
  15. Storage API degradation in London

    Started: · Duration: 121 min
    Provider updates (3)
    1. Investigating “We are currently investigating elevated error rates on the Storage API in our London, UK region. Some API operations may be affected as a result.”
    2. Monitoring “A fix has been implemented and we are monitoring the results.”
    3. Resolved “This incident has been resolved.”
    Resolved
  16. Video Delivery Failures on Basic DRM enabled Libraries

    Started: · Duration: 28 min
    Provider updates (2)
    1. Investigating “We are currently investigating intermittent playback failures on Stream libraries, specifically with Basic DRM enabled. This does not impact existing underlying storage, or other video library types (Enterprise DRM or non DRM).”
    2. Resolved “We have identified a process on a single server causing Basic DRM transformation failures, and was the cause of intermittent video freezes/500s. This has been rectified by the Engineering team.”
    Resolved
  17. Users are unable to login to dash.bunny.net

    Started: · Duration: 14 min
    Provider updates (2)
    1. Investigating “We are currently investigating an issue where users are unable to log in to the Bunny.net dashboard. Services themselves are not disrupted.”
    2. Resolved “The login issue has now been resolved following a fix deployed by our Frontend team.”
    Resolved
  18. Storage API Degradation in Germany

    Started: · Duration: 7 min
    Provider updates (2)
    1. Investigating “We are currently investigating a Storage API incident on our German nodes. API Upload/List/Deletions may be affected as a result.”
    2. Resolved “We identified an failing database process on the Storage layer, which has now been resolved by our Engineering team.”
    Resolved
  19. Investigating Dashboard and Service Availability Issues

    Started: · Duration: 74 min
    Provider updates (3)
    1. Investigating “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. Monitoring “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. Resolved “This incident has been resolved.”
    Resolved
  20. Investigating Issues with Magic Containers and Databases

    Started: · Duration: 36 min
    Provider updates (3)
    1. Investigating “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. Monitoring “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. Resolved “This incident has been resolved.”
    Resolved

What the provider published about this service, with the provider's own updates (wording quoted as published).

Evidence

Official
bunny.net Status ↗ · All Systems Operational · Oct 25, 01:41 AM UTC

Why this assessment

  • Provider reports no active incident.

Rule set assess-1. The same evidence always gives the same result.

Evidence and freshness

Each source separately: who says it, when it was last observed, and whether it is recent enough to be used.

SourceLast observedAgeUsed in assessment
Official0 min agoYes — recent

Technical details

Affected components (provider)

The provider lists no degraded components.

Official status page ↗