September 19th, 2024

Support for IPv6

Backblaze has launched IPv6 support for its S3 Compatible API to enhance network performance and accommodate more devices, while still supporting IPv4 during the transition. Future expansions are planned.

Read original articleLink Icon
Support for IPv6

Backblaze has announced the rollout of IPv6 support for its S3 Compatible API, which began on September 18, 2024. This transition is part of a phased deployment aimed at enhancing network performance and accommodating the growing demand for IP addresses due to the increasing number of connected devices. IPv6 expands the address space from 32 bits to 128 bits, allowing for virtually unlimited unique IP addresses. Customers using IPv6-enabled systems will benefit from this upgrade without needing to take any action, as Backblaze has maintained the same endpoint URL for both IPv4 and IPv6. The deployment is designed to improve network performance by simplifying IP assignments and reducing reliance on Network Address Translation (NAT), which can introduce latency. Backblaze's network architecture has been adapted to support this transition, with a focus on traffic engineering and scalability. The company is also exploring ways to extend IPv6 support to its B2 Native API and Computer Backup services in the future. IPv4 will continue to be supported alongside IPv6 for the time being, ensuring a smooth transition for all users.

- Backblaze has initiated IPv6 support for its S3 Compatible API.

- The transition aims to improve network performance and accommodate more connected devices.

- Customers do not need to take any action to benefit from the IPv6 upgrade.

- IPv4 will still be supported during the transition period.

- Future plans include extending IPv6 support to additional Backblaze services.

Link Icon 12 comments
By @kuon - 7 months
About two years ago, when we deployed our datacenter, I insisted for IPv6 first.

All out management network is IPv6 only, all kvm, switches, routers...

It was a pain and gives nearly no practical advantage (at the time), but the motivation was to make everyone "intimate" with IPv6. We learned a lot and we even discovered some implementation bugs (for example, Cisco default link local address is not /64 and this is not compliant with more recent RFC and will make them unable to communicate with BSD systems).

Now we have IPv6 everywhere and everybody from dev to sysadmin is aware of IPv6 and we start to see some real advantages. VPN are easier to manage, routing is easier, firewall is easier, clustering, failover... everything is "cleaner".

We still have IPv4 (dual stack) on some servers, but about 80% of them are IPv6 only with DNS64/NAT64.

By @kstrauser - 7 months
Outstanding. As Google’s IPv6 traffic portion approaches 50% (https://www.google.com/intl/en/ipv6/statistics.html) it’s clear IPv6 is here, now, today. I wouldn’t dream of launching a new public-facing greenfield project without it.
By @Habgdnv - 7 months
I am running as many IPv6 only services as I can. All MY core services that I use daily are v6 only. At the end of 2024 i am still shocked to see how much new software does not work without ipv4. My most recent struggle was with Seq - the opentelemetry server for example. It is full of new software created in the recent few years that just refuses to work without ipv4. And not because it need to reach some server on the internet. It just does not work if you do not have ipv4 (even private).
By @ComputerGuru - 7 months
This seems as good a place to ask as any: how does one obtain a (larger) block of IPv6 not via their ISP/datacenter and then route it (to a network they control) through their ISP/datacenter-provided IPv6 uplink? Is that even possible?
By @doublepg23 - 7 months
I was very happy to get symmetric Gig internet at my new place but very bummed that my ISP doesn’t offer IPv6.

I had enjoyed learning about and deploying it on my LAN whenever Comcast added support (SLAAC is magical) but I guess I’ll be waiting for quite a while to play with it again :(

By @everfrustrated - 7 months
There's also a cool trick you can do with IPv6 addresses for servers where you use RA to broadcast your IPv6 prefix on the LAN and the OS assigns itself a valid public IPv6 using the MAC address for uniqueness. Very clean and easy.
By @elchief - 7 months
Hoping AWS and my ISP implement IPv6 before I retire...

(AWS has partially implemented IPv6, but it's still not usable in my mind)

By @BrandoElFollito - 7 months
I had to get into IPv6 for real when I switched ISPs and the French Free relies on IPv6 for some services.

IPv6 is hard. You have to learn brand new concepts for something which is only a medium for your actual apps (I self host a lot).

I do not know if there would have been a way to make it more "advanced user" friendly but if the was, it's a lost opportunity to get wider adoption faster.

By @Tempest1981 - 7 months
> route when you can, switch only when you need to mantra

Naive question: isn't switching faster than routing?

By @BruhWasH3r3 - 7 months
IPv6 is great, but it does open up new challenges with traffic management, reputation, and bot analysis. We need advances there.
By @daft_pink - 7 months
We need something better than IPv6 that better addresses the needs of users. IPv6 does too much and is too complicated.