- Level
- confirmed
- Worst impact
- Degraded
- Components
- Optimizer
- Regions
- us
What to do
Check whether you use Bunny.net Optimizer in us. 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 4h 18m it lasted.
Anything that failed between 2026-09-03 08:53 UTC and 2026-09-03 13:11 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
- identified
We are currently observing performance degradation with a Tier 1 transit provider in the Los Angeles area due to multiple fiber cuts on their network. This has impacted connectivity between the Bunny Optimizer LA cluster and a small number of US CDN PoPs. Traffic has been rerouted to minimize the impact.
provider
- resolved
This incident has been resolved.
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-69515d0af7
Is Bunny.net still down?
No, this incident was resolved 2026-09-03 13:11 UTC. For Bunny.net's live state, see https://down.guide/bunny.
How long did it last?
4h 18m, from 2026-09-03 08:53 UTC to 2026-09-03 13:11 UTC, by the times Bunny.net posted.
What was affected?
Bunny.net named Optimizer in us.
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.