Bunny.net Status
Last incident: 8/8/2025
Recent Incidents
THIS IS A SCHEDULED EVENT Aug 8, 22:00 UTC - Aug 9, 06:00 UTC
Jul 27, 16:36 UTC
Scheduled - We will be performing scheduled maintenance that will temporarily affect access to files stored in non-replicated storage zones located in Germany.
Expected Impact
During the maintenance window, requests for files in non-replicated storage zones may result in temporary 5xx errors. Replicated files will remain fully accessible.
Maintenance Window
Date: August 9th, 2025
Time: 00:00 - 08:00 AM local time (UTC+2)
Expected Impact Duration: Up to 3 hours
Aug 1, 14:42 UTC
Resolved - We have upgraded the backend for the statistics response time problem. In line with our long-term strategy, we are planning a migration to ensure improved scalability and demand management.
Jul 31, 08:45 UTC
Identified - We are working to resolve a long-standing issue of statistics via Dashboard/API being periodically unavailable. We are in the process of upgrading the backend to better scale with demand going forward; however we estimate this may take up to 2 weeks (tentative).
Jul 28, 13:40 UTC
Resolved - This incident has been resolved.
Jul 28, 13:28 UTC
Investigating - We're currently investigating an API outage currently affecting Billing, Ticketing, Scripting interface and Statistics. Traffic on the network is not affected.
Jul 23, 14:29 UTC
Resolved - Our team found an internal process failure on the API backend. The issue has been rectified and its impact will be reviewed going forward.
Jul 23, 14:17 UTC
Update - Our team continues to investigate the issue. Support ticketing is additionally affected.
Jul 23, 13:37 UTC
Investigating - We're currently investigating an API outage currently affecting Billing, Scripting interface and Statistics.
Jul 23, 12:32 UTC
Resolved - This has now been resolved.
Jul 23, 10:23 UTC
Monitoring - We have identified the root cause and monitoring the situation.
Jul 23, 08:45 UTC
Investigating - We are investigating an issue where domain statistics are incorrectly reporting as 0, despite traffic serving as normal on pull zone domains.