All Systems Operational

About This Site

bunny.net operates a global content delivery network. This page contains the system status service of our network, API, storage and other related systems. If no issues are reported and you are experiencing problems, please email us at support@bunny.net

Uptime over the past 90 days. View historical uptime.
Website Operational
Dashboard Operational
API Operational
CDN Operational
90 days ago
100.0 % uptime
Today
DNS Operational
90 days ago
99.99 % uptime
Today
Edge Storage Operational
90 days ago
99.99 % uptime
Today
Stream Operational
90 days ago
100.0 % uptime
Today
Stream Service Operational
90 days ago
100.0 % uptime
Today
Stream - Transcoding Service Operational
Optimizer Operational
90 days ago
99.84 % uptime
Today
Origin Shield Operational
90 days ago
100.0 % uptime
Today
Bunny Fonts Operational
90 days ago
99.99 % uptime
Today
Edge Scripting Operational
90 days ago
99.99 % uptime
Today
Magic Containers Operational
90 days ago
99.98 % uptime
Today
Bunny Shield Operational
90 days ago
99.99 % uptime
Today
Bunny Database Operational
90 days ago
99.97 % uptime
Today
CDN Logging Operational
90 days ago
100.0 % uptime
Today
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.

No incidents or maintenance related to this downtime.

Jun 5, 2026

No incidents reported today.

Jun 4, 2026

No incidents reported.

Jun 3, 2026
Lets Encrypt SSL API Errors
Resolved - We no longer see delays stemming from Lets Encrypt and the issue is considered resolved.
Jun 3, 12:38 UTC
Identified - 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.
Jun 3, 09:02 UTC
Jun 2, 2026

No incidents reported.

Jun 1, 2026
Investigating Issues with Magic Containers and Databases
Postmortem - Read details
Jun 3, 09:17 UTC
Resolved - This incident has been resolved.
Jun 1, 20:18 UTC
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.
Jun 1, 17:24 UTC
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.
Jun 1, 16:02 UTC
Stream Service Degradation
Resolved - This incident has been resolved.
Jun 1, 20:17 UTC
Monitoring - 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.
Jun 1, 17:18 UTC
Investigating - 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.
Jun 1, 16:19 UTC
Increased Optimizer Errors
Resolved - This incident has been resolved.
Jun 1, 10:38 UTC
Investigating - 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.
Jun 1, 07:24 UTC
May 31, 2026

No incidents reported.

May 30, 2026

No incidents reported.

May 29, 2026

No incidents reported.

May 28, 2026

No incidents reported.

May 27, 2026
CDN configuration sync delays
Resolved - The fix has been deployed to all nodes. We will be readding the missing nodes to the pool today.
May 27, 11:15 UTC
Monitoring - 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.
May 26, 16:00 UTC
Identified - 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.
May 26, 06:47 UTC
May 26, 2026
Isolated 502s for Magic Containers
Resolved - We identified and resolved an issue that could cause endpoint updates to experience delayed propagation after CDN services had been running for an extended period of time. The issue was related to endpoint synchronization between Magic Containers and the CDN routing component, where slower processing connected to sticky session invalidation could result in stale endpoint data remaining in use longer than expected.
May 26, 08:23 UTC
Monitoring - We are monitoring improvements related to the resilience of routing configuration failover on edge servers during temporary control plane connectivity interruptions.
May 6, 14:29 UTC
Update - Our Engineering team are still investigating the root cause for isolated 502s in the NA region.
May 1, 10:48 UTC
Update - We have made some routing adjustments to mitigate the timeouts on Database and is fully operational again. Our Engineering team is continuing to investigate the Magic Containers issue.
Apr 30, 12:16 UTC
Update - We are continuing to investigate this issue.
Apr 30, 10:14 UTC
Investigating - We are currently looking into isolated 502s within the NA region for CDN endpoints utilizing Magic Containers and Databases. This is primarily affecting specific regions in North America.

Our Engineering team are investigating the issue currently.
Apr 30, 10:12 UTC
May 25, 2026

No incidents reported.

May 24, 2026

No incidents reported.

May 23, 2026
CDN Acceleration 502s on DNS Records
Resolved - This incident has been resolved.
May 23, 13:52 UTC
Monitoring - 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.
May 22, 19:03 UTC
Identified - 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.
May 22, 14:22 UTC
Investigating - 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.
May 22, 11:19 UTC
May 22, 2026
← Incident History Powered by Atlassian Statuspage