- Detected by Pingoru
- Aug 25, 2026, 02:06 PM UTC
- Resolved
- Aug 25, 2026, 10:31 PM UTC
- Duration
- 8h 24m
Affected: Bunny Database
Timeline · 4 updates
-
identified Aug 25, 2026, 02:06 PM UTC
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.
-
identified Aug 25, 2026, 04:01 PM UTC
Our Engineering team are continuing to work on the issue. Additionally, we are aware of some working Databases failing during this outage. This is related and our team are also working to address this.
-
monitoring Aug 25, 2026, 04:06 PM UTC
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.
-
resolved Aug 25, 2026, 10:31 PM UTC
After monitoring the affected services, we have confirmed that Database management and idle Database activation are operating normally.
Read the full incident report →
- Detected by Pingoru
- Aug 18, 2026, 02:28 AM UTC
- Resolved
- Aug 18, 2026, 04:29 AM UTC
- Duration
- 2h
Affected: Edge Storage
Timeline · 3 updates
-
investigating Aug 18, 2026, 02:28 AM UTC
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.
-
monitoring Aug 18, 2026, 04:09 AM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Aug 18, 2026, 04:29 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jul 23, 2026, 08:33 AM UTC
- Resolved
- Jul 23, 2026, 09:02 AM UTC
- Duration
- 28m
Affected: Stream Service
Timeline · 2 updates
-
investigating Jul 23, 2026, 08:33 AM UTC
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).
-
resolved Jul 23, 2026, 09:02 AM UTC
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.
Read the full incident report →
- Detected by Pingoru
- Jul 17, 2026, 10:57 AM UTC
- Resolved
- Jul 17, 2026, 11:11 AM UTC
- Duration
- 14m
Affected: Dashboard
Timeline · 2 updates
-
investigating Jul 17, 2026, 10:57 AM UTC
We are currently investigating an issue where users are unable to log in to the Bunny.net dashboard. Services themselves are not disrupted.
-
resolved Jul 17, 2026, 11:11 AM UTC
The login issue has now been resolved following a fix deployed by our Frontend team.
Read the full incident report →
- Detected by Pingoru
- Jul 01, 2026, 09:45 AM UTC
- Resolved
- Jul 01, 2026, 09:53 AM UTC
- Duration
- 7m
Affected: Edge Storage
Timeline · 2 updates
-
investigating Jul 01, 2026, 09:45 AM UTC
We are currently investigating a Storage API incident on our German nodes. API Upload/List/Deletions may be affected as a result.
-
resolved Jul 01, 2026, 09:53 AM UTC
We identified an failing database process on the Storage layer, which has now been resolved by our Engineering team.
Read the full incident report →
- Detected by Pingoru
- Jun 27, 2026, 06:57 PM UTC
- Resolved
- Jun 27, 2026, 08:11 PM UTC
- Duration
- 1h 14m
Affected: Stream ServiceDashboardEdge Storage
Timeline · 3 updates
-
investigating Jun 27, 2026, 06:57 PM UTC
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.
-
monitoring Jun 27, 2026, 07:17 PM UTC
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.
-
resolved Jun 27, 2026, 08:11 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jun 26, 2026, 02:21 PM UTC
- Resolved
- Jun 26, 2026, 02:57 PM UTC
- Duration
- 35m
Affected: Magic Containers
Timeline · 3 updates
-
investigating Jun 26, 2026, 02:21 PM UTC
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.
-
monitoring Jun 26, 2026, 02:29 PM UTC
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.
-
resolved Jun 26, 2026, 02:57 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jun 23, 2026, 01:22 PM UTC
- Resolved
- Jun 24, 2026, 03:11 AM UTC
- Duration
- 13h 49m
Affected: Bunny Shield
Timeline · 2 updates
-
monitoring Jun 23, 2026, 01:22 PM UTC
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.
-
resolved Jun 24, 2026, 03:11 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jun 18, 2026, 08:57 PM UTC
- Resolved
- Jun 19, 2026, 09:37 AM UTC
- Duration
- 12h 39m
Affected: APICDN
Timeline · 3 updates
-
investigating Jun 18, 2026, 08:57 PM UTC
We have identified an issue with free certificate issuance and renewals for custom CDN domains.
-
identified Jun 18, 2026, 08:58 PM UTC
We have identified an issue with free certificate issuance and renewals for custom CDN domains. 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.
-
resolved Jun 19, 2026, 09:37 AM UTC
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.
Read the full incident report →
- Detected by Pingoru
- Jun 15, 2026, 08:25 PM UTC
- Resolved
- Jun 15, 2026, 09:24 PM UTC
- Duration
- 59m
Affected: CDNDNS
Timeline · 3 updates
-
investigating Jun 15, 2026, 08:25 PM UTC
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.
-
monitoring Jun 15, 2026, 08:45 PM UTC
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.
-
resolved Jun 15, 2026, 09:24 PM UTC
All pending configuration changes have propagated across the CDN.
Read the full incident report →
- Detected by Pingoru
- Jun 03, 2026, 09:02 AM UTC
- Resolved
- Jun 03, 2026, 12:38 PM UTC
- Duration
- 3h 35m
Affected: CDN
Timeline · 2 updates
-
identified Jun 03, 2026, 09:02 AM UTC
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.
-
resolved Jun 03, 2026, 12:38 PM UTC
We no longer see delays stemming from Lets Encrypt and the issue is considered resolved.
Read the full incident report →
- Detected by Pingoru
- Jun 01, 2026, 04:19 PM UTC
- Resolved
- Jun 01, 2026, 08:17 PM UTC
- Duration
- 3h 58m
Affected: Stream - Transcoding Service
Timeline · 3 updates
-
investigating Jun 01, 2026, 04:19 PM UTC
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.
-
monitoring Jun 01, 2026, 05:18 PM UTC
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.
-
resolved Jun 01, 2026, 08:17 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jun 01, 2026, 07:24 AM UTC
- Resolved
- Jun 01, 2026, 10:38 AM UTC
- Duration
- 3h 14m
Affected: Optimizer
Timeline · 2 updates
-
investigating Jun 01, 2026, 07:24 AM UTC
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.
-
resolved Jun 01, 2026, 10:38 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- May 26, 2026, 06:47 AM UTC
- Resolved
- May 27, 2026, 11:15 AM UTC
- Duration
- 1d 4h
Affected: CDN
Timeline · 3 updates
-
identified May 26, 2026, 06:47 AM UTC
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.
-
monitoring May 26, 2026, 04:00 PM UTC
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.
-
resolved May 27, 2026, 11:15 AM UTC
The fix has been deployed to all nodes. We will be readding the missing nodes to the pool today.
Read the full incident report →
- Detected by Pingoru
- May 22, 2026, 11:19 AM UTC
- Resolved
- May 23, 2026, 01:52 PM UTC
- Duration
- 1d 2h
Affected: CDNDNS
Timeline · 4 updates
-
investigating May 22, 2026, 11:19 AM UTC
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.
-
identified May 22, 2026, 02:22 PM UTC
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.
-
monitoring May 22, 2026, 07:03 PM UTC
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.
-
resolved May 23, 2026, 01:52 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- May 21, 2026, 04:39 PM UTC
- Resolved
- May 21, 2026, 06:21 PM UTC
- Duration
- 1h 41m
Affected: WebsiteStream ServiceDashboardStream - Transcoding ServiceAPICDNDNSEdge StorageOptimizerOrigin ShieldBunny FontsEdge ScriptingMagic ContainersBunny ShieldBunny DatabaseCDN Logging
Timeline · 3 updates
Read the full incident report →
- Detected by Pingoru
- May 14, 2026, 02:23 PM UTC
- Resolved
- May 14, 2026, 03:41 PM UTC
- Duration
- 1h 17m
Affected: CDNEdge StorageEdge ScriptingMagic ContainersBunny Database
Timeline · 5 updates
-
investigating May 14, 2026, 02:23 PM UTC
We are currently experiencing a network issue in our Singapore region, and as a result there may be degraded performance on CDN, Storage, Magic Containers and Database from the region. Our Engineering team are investigating the problem.
-
investigating May 14, 2026, 02:23 PM UTC
We are continuing to investigate this issue.
-
investigating May 14, 2026, 02:33 PM UTC
We are continuing to investigate this issue.
-
monitoring May 14, 2026, 02:42 PM UTC
We identified an outage in relation to an upstream network provider that resulted in partial degradation in Singapore, this is now resolved. We are currently monitoring the situation.
-
resolved May 14, 2026, 03:41 PM UTC
This incident has now been cleared.
Read the full incident report →
- Detected by Pingoru
- May 01, 2026, 03:51 AM UTC
- Resolved
- May 01, 2026, 11:12 AM UTC
- Duration
- 7h 20m
Affected: CDN
Timeline · 3 updates
-
investigating May 01, 2026, 03:51 AM UTC
We are currently investigating issues related to delayed configuration of Pull Zones.
-
identified May 01, 2026, 08:43 AM UTC
We have identified the core issue at hand and our Engineering team are currently reviewing the situation. Configuration delays/syncs are slowly recovering.
-
resolved May 01, 2026, 11:12 AM UTC
The configuration delay has now been resolved. At around 00:15, we observed a large scale domain sync that caused configuration delays. This was resolved at 06:00 UTC, before the backlog of configuration changes were cleared by 09:30 UTC. Our Engineering team have identified the core issue and will take action to prevent future recurrence of the problem.
Read the full incident report →
- Detected by Pingoru
- Apr 30, 2026, 10:12 AM UTC
- Resolved
- May 26, 2026, 08:23 AM UTC
- Duration
- 25d 22h
Affected: Magic ContainersBunny Database
Timeline · 6 updates
-
investigating Apr 30, 2026, 10:12 AM UTC
We are currently looking into isolated 502s within the NA region for CDN endpoints utilizing Magic Containers and Edge Scripting. This is primarily affecting specific regions in North America. Our Engineering team are investigating the issue currently.
-
investigating Apr 30, 2026, 10:14 AM UTC
We are continuing to investigate this issue.
-
investigating Apr 30, 2026, 12:16 PM UTC
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.
-
investigating May 01, 2026, 10:48 AM UTC
Our Engineering team are still investigating the root cause for isolated 502s in the NA region.
-
monitoring May 06, 2026, 02:29 PM UTC
We are monitoring improvements related to the resilience of routing configuration failover on edge servers during temporary control plane connectivity interruptions.
-
resolved May 26, 2026, 08:23 AM UTC
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.
Read the full incident report →
- Detected by Pingoru
- Mar 30, 2026, 09:05 AM UTC
- Resolved
- Mar 30, 2026, 09:51 PM UTC
- Duration
- 12h 46m
Affected: DashboardAPI
Timeline · 3 updates
-
identified Mar 30, 2026, 09:05 AM UTC
We are working on an issue with our Statistics API endpoint. There are increased response times probing CDN and DNS statistics, resulting in some delayed reports, or timeouts. This affects both dashboard and direct API requests for statistics.
-
identified Mar 30, 2026, 03:29 PM UTC
Our Engineering team has identified the issue of the statistics response delays, and are preparing a fix
-
resolved Mar 30, 2026, 09:51 PM UTC
Our Engineering team identified an overloaded process with on our statistics endpoint. This was rectified and monitored, and the issue has now been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 23, 2026, 07:50 PM UTC
- Resolved
- Mar 27, 2026, 09:00 AM UTC
- Duration
- 3d 13h
Affected: Stream - Transcoding Service
Timeline · 2 updates
-
investigating Mar 23, 2026, 07:50 PM UTC
We are currently experiencing high demand for our free encoding services. Video processing times may be longer than usual. Premium encoding, existing videos, and delivery are not affected. Our team is actively monitoring the situation, thank you for your patience.
-
resolved Mar 27, 2026, 09:00 AM UTC
We have expanded our transcoding capacity, transcoding delays have now cleared, and processing has normalized.
Read the full incident report →
- Detected by Pingoru
- Mar 19, 2026, 11:41 AM UTC
- Resolved
- Mar 19, 2026, 03:05 PM UTC
- Duration
- 3h 24m
Affected: Magic Containers
Timeline · 2 updates
-
investigating Mar 19, 2026, 11:41 AM UTC
Our Magic Containers team are currently investigating an issue with application updates. There may be deployment delays or failures on the platform as a result.
-
resolved Mar 19, 2026, 03:05 PM UTC
Our Containers team found that a recent deployment had resulted in an unintended CPU throttling on new pod or app deployments. This has now been resolved, and the team has made mitigating changes to ensure this does not resurface.
Read the full incident report →
- Detected by Pingoru
- Mar 05, 2026, 03:29 PM UTC
- Resolved
- Mar 06, 2026, 04:43 AM UTC
- Duration
- 13h 13m
Affected: CDN Logging
Timeline · 3 updates
-
investigating Mar 05, 2026, 03:29 PM UTC
Our Engineering team are aware of and currently working to address Log Forwarding failures. Any zones configured with Log Forwarding is affected. Standard logging is not affected.
-
monitoring Mar 05, 2026, 11:45 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Mar 06, 2026, 04:43 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 03, 2026, 10:12 AM UTC
- Resolved
- Mar 04, 2026, 02:32 PM UTC
- Duration
- 1d 4h
Affected: CDN Logging
Timeline · 2 updates
-
identified Mar 03, 2026, 10:12 AM UTC
Over the past few weeks, we've grown beyond the scale our previous CDN log delivery platform was originally designed to handle. As a result, customers are experiencing delays in log delivery. We've been working on a more robust, better-scaling ingest system, and that work is now complete. We expect the transition to be fully rolled out by Friday evening (UTC), March 6th.
-
resolved Mar 04, 2026, 02:32 PM UTC
Migration to our new Logging Platform is now complete, and near real-time logs should be visible again. Unfortunately, we had to accelerate the migration timeline as our legacy platform began struggling much sooner than expected. Because of this, we made the difficult decision to complete the migration before fully backfilling the expected 3 days of retained logging history. At the moment, approximately 1.5 days of logs are available on the new platform. This will gradually increase and return to the full 3-day retention by Friday. The raw, unprocessed logs remain stored on the legacy logging platform. If you require access to these logs and have a valid justification, please submit a support ticket, and we will do our best to recover them on a case-by-case basis.
Read the full incident report →
- Detected by Pingoru
- Mar 02, 2026, 09:18 AM UTC
- Resolved
- Mar 02, 2026, 11:21 AM UTC
- Duration
- 2h 3m
Affected: Stream ServiceAPICDN
Timeline · 3 updates
-
investigating Mar 02, 2026, 09:18 AM UTC
We are currently looking into pull zone configuration delays. Existing configurations and platform traffic are not affected.
-
monitoring Mar 02, 2026, 10:15 AM UTC
Our Engineering team has applied a fix, and a delayed pull zone backlog of configurations are now processing. We will monitor the situation.
-
resolved Mar 02, 2026, 11:21 AM UTC
This issue is now resolved.
Read the full incident report →
