Bunny CDN Security Incident
0 comments
- Points18
- Comments3
0 comments
Story details from Hacker News ↗ · linked article on status.bunny.net.
Bunny CDN Security Incident was first seen on Hacker News · Front page on Oct 30, 2026. Since then it has appeared in 27 checks on 2 different days. Its best position was #8 of 30, reached on Oct 30, 23:07 UTC. It dropped off the list after Oct 31, 02:37 UTC.
Position on Hacker News · Front page at every check (lower is better).
Best rank per day (UTC).
Platform metric as reported by Hacker News.
A few top-level comments from Hacker News, shortened. Read the full thread on Hacker News.
While neither investigation has found any indication of unauthorized access to our server, we cannot completely rule out the possibility. If unauthorized access to our CDN node did occur, the potentially exposed information would have been: temporarily cached CDN content, Pull Zone configurations, and TLS…
Prompt and competent response, as expected from bunny. "Last week, one of our infrastructure providers reported unauthorized access involving third-party server management software. One of our CDN nodes, located in Armenia, was hosted on a server supplied by this provider. After receiving the alert from the affected…
Bunny used Gcore in Armenia. Gcore themselves got hacked, not Bunny. Bunny was just an affected downstream, in only one of their POPs. https://lowendtalk.com/discussion/222315/gcore-compromised-v... The title is heavily misleading.
Archived daily, weekly and monthly lists that include this entry.
Not at the moment. It was last on the list on Oct 31, 02:37 UTC, after 2 days of trending.
#8 on Hacker News · Front page, on Oct 30, 23:07 UTC. Trendoday checks this list every 15 minutes.
It was first seen on Oct 30, 2026 and has been on the list on 2 days (27 checks) since.
18 points and 3 comments; submitted by SondreDag on Oct 30, 2026.