- Level
- confirmed
- Worst impact
- Degraded
- Components
- CDN
- Down Index
- 21of 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 3h 36m it lasted.
Anything that failed between 2026-06-03 09:02 UTC and 2026-06-03 12:38 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 have identified an issue on free cert issuance and renewals for custom CDN domains. We have observed a delay from Lets Encrypt API endpoint causing these delays. Existing certificates on custom domains will continue to function as normal - however new and cert renewals via our free certificate option may experience a delay to the certificate issuance.
provider
- resolved
We no longer see delays stemming from Lets Encrypt and the issue is considered 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-ff6ed8abdd
Is Bunny.net still down?
No, this incident was resolved 2026-06-03 12:38 UTC. For Bunny.net's live state, see https://down.guide/bunny.
How long did it last?
3h 36m, from 2026-06-03 09:02 UTC to 2026-06-03 12:38 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.