Bunny.net VS Hurricane Electric

I wanted to migrate a static website from a VPS to a CDN to improve website loading time and SEO performance. After a few searches, I discovered a new sleek CDN called BunnyCDN, which beats all performance charts in latency with an average of 40ms. That's what I was looking for! - Source: dev.to / about 2 months ago

This is great news. Now I can utilize any CDN provider that supports S3. Like bunny.net [1] which has image optimization, just like Supabase does but with better pricing and features. I have been developing with Supabase past two months. I would say there are still some rough corners in general and some basic features missing. Example Supabase storage has no direct support for metadata [2][3]. Overall I like the... - Source: Hacker News / 27 days ago

It seems there's no discord community yet for bunny.net, would someone be interested in setting this up? Source: 5 months ago

Use a CDN like Bunny and you can host images for like $1/mo + less than $0.10/gb of bandwidth. Source: 6 months ago

You'll want a CDN like Bunny (at least for the files), instead of a web host. Source: 7 months ago

Hurricane Electric is a global internet service provider offering internet transit tools, network and applications, as well as data center colocation and hosting services. As of May 2023, Hurricane Electric was one of the largest global IP networks as measured by network adjacencies in both IPv4 and IPv6. More information regarding Hurricane Electric can be found on their corporate website: https://he.net/ . Source: 5 months ago

Another one I'll mention, as it might be rather to quite easy - depending upon one's IPv6 knowledge/experience - and it's also free. It's slightly dated (some bits have changed since it was created, but it's mostly still highly applicable). Anyway, Hurricane Electric's IPv6 Certification - can even get oneself spiffy "badge"s - like I've got one of those (details & score style) (also available in different... Source: 9 months ago

The other comment with the answer disappeared, but it was to create a static route for the /64 on PFSENSE1 to the WAN IPV6 of the PFSENSE2. This allows that WAN to pass the traffic through the he.net IPV6 tunnel. Source: 11 months ago

I have been using he.net's tunnelbroker service for sometime. I am familiar with it and it works well. Source: 11 months ago

Likely due to too much abuse from the free he.net tunnels. They have no way to differentiate between your tunnel used for legitimate purposes, and a tunnel created solely for malicious purposes. This sort of problem occurs with any shared resources especially free ones, you get the same problem using free VPNs or TOR etc. Source: 12 months ago