CDN Log Delivery Delay

Summary

CDN Log Delivery Delay

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.

• Started

  Mar 3, 2026 · 10:12 AM

• Resolved

  Mar 4, 2026 · 2:32 PM

• Duration

  1d 4h 20m

• Severity

  Minor

• ◆

  Identified

  Mar 3 · 10:12 AM Bunny.net

  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 4 · 2:32 PM Bunny.net

  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.