CDN Log Delivery Delay

What to do

• Check whether you use Bunny.net CDN Logging. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 1d 4h it lasted.

  Anything that failed between 2026-03-03 10:12 UTC and 2026-03-04 14:32 UTC may need a replay.

• Subscribe to Bunny.net's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=bunny works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Bunny.net 2

1. identifiedMar 3, 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.

   provider

2. resolvedMar 4, 2026, 2: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.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.