Bunny.net: Degraded Optimizer Response times

What to do

Check whether you use Bunny.net Optimizer. 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 2h 25m it lasted.
Anything that failed between 2026-09-25 14:49 UTC and 2026-09-25 17:15 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.

investigatingSep 25, 2026, 2:49 PM UTC
We are currently investigating degraded optimizer processing, causing increased latency in serving assets on CDN. This issue sits under image transformation and asset compression only.
provider
resolvedSep 25, 2026, 5:15 PM UTC
A subset of optimizer workers exhibited disk performance issues, impacting Optimizer software's throughput. A fix has been deployed to all servers sharing this same hardware model and performance is back at normal levels again.
provider

Reports count in aggregate; nothing about you is shown.

None so far.

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

Is Bunny.net still down?

No, this incident was resolved 2026-09-25 17:15 UTC. For Bunny.net's live state, see https://down.guide/bunny.

How long did it last?

2h 25m, from 2026-09-25 14:49 UTC to 2026-09-25 17:15 UTC, by the times Bunny.net posted.

What was affected?

Bunny.net named Optimizer.

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.