Skip to main content
Bunny.net

Performance degradation in DE

Degraded Lasted 1h 58m · started · Bunny.net's page

Level
confirmed
Worst impact
Degraded
Components
CDN
Down Index
20of 100

What to do

  • Check whether you use Bunny.net CDN. 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 1h 58m it lasted.

    Anything that failed between 2026-10-24 18:45 UTC and 2026-10-24 20:43 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 3

  1. investigating

    We are currently investigating this issue affecting the CDN performance in DE.

    provider

  2. monitoring

    We've found and resolved the issue and are actively monitoring performance.

    provider

  3. resolved

    This incident has been resolved, we're not observing performance issues anymore.

    provider

Reports count in aggregate; nothing about you is shown.

Corrections

None so far.

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

Questions about DWN-d61ebff04a

Is Bunny.net still down?

No, this incident was resolved 2026-10-24 20:43 UTC. For Bunny.net's live state, see https://down.guide/bunny.

How long did it last?

1h 58m, from 2026-10-24 18:45 UTC to 2026-10-24 20:43 UTC, by the times Bunny.net posted.

What was affected?

Bunny.net named CDN.

What caused it?

Bunny.net hasn't published a root cause. If it does, it shows here.

Where does this come from?

Bunny.net's official status page, https://status.bunny.net, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.