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 articleBackblaze 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.
Related
Why content providers need IPv6
Content providers are urged to adopt IPv6 for better services, bypassing ISP translation devices. IPv6 improves user experience, reduces latency, and boosts reliability. Major companies like Google and Netflix are already benefiting from IPv6, pushing ISPs to support its adoption.
Backblaze Drive Stats for Q2 2024
Backblaze monitored 284,876 drives in Q2 2024, reporting an annualized failure rate of 1.71%. Two models had zero failures, and the company is exploring AI for predicting drive failures.
The backbone behind Cloudflare's Connectivity Cloud
Cloudflare has increased its backbone capacity by over 500% since 2021, operating data centers in 330 cities globally, utilizing advanced technologies for efficient data transfer and enhancing connectivity, especially in Africa.
Zero-click Windows TCP/IP RCE impacts all systems with IPv6 enabled, patch now
Microsoft warns of a critical TCP/IP vulnerability (CVE-2024-38063) affecting all IPv6-enabled Windows systems, allowing remote code execution. Users should prioritize patching to mitigate risks, as the exploit is wormable.
Cloudflare Network Issues Affecting Service Reachability
On September 17, 2024, Cloudflare faced network issues affecting certain IPv4 prefixes, disrupting CDN and application security services. The incident was resolved within 15 minutes after identification and fix implementation.
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.
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 :(
(AWS has partially implemented IPv6, but it's still not usable in my mind)
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.
Naive question: isn't switching faster than routing?
Related
Why content providers need IPv6
Content providers are urged to adopt IPv6 for better services, bypassing ISP translation devices. IPv6 improves user experience, reduces latency, and boosts reliability. Major companies like Google and Netflix are already benefiting from IPv6, pushing ISPs to support its adoption.
Backblaze Drive Stats for Q2 2024
Backblaze monitored 284,876 drives in Q2 2024, reporting an annualized failure rate of 1.71%. Two models had zero failures, and the company is exploring AI for predicting drive failures.
The backbone behind Cloudflare's Connectivity Cloud
Cloudflare has increased its backbone capacity by over 500% since 2021, operating data centers in 330 cities globally, utilizing advanced technologies for efficient data transfer and enhancing connectivity, especially in Africa.
Zero-click Windows TCP/IP RCE impacts all systems with IPv6 enabled, patch now
Microsoft warns of a critical TCP/IP vulnerability (CVE-2024-38063) affecting all IPv6-enabled Windows systems, allowing remote code execution. Users should prioritize patching to mitigate risks, as the exploit is wormable.
Cloudflare Network Issues Affecting Service Reachability
On September 17, 2024, Cloudflare faced network issues affecting certain IPv4 prefixes, disrupting CDN and application security services. The incident was resolved within 15 minutes after identification and fix implementation.