JavaScript Libraries Now Served from R2

TL;DR: Chainguard Libraries for JavaScript will be served from Cloudflare R2 instead of Google Artifact Registry beginning Mar 4, 2026. Customers who restrict outbound network access may need to allow traffic from our R2 domain host. 

NOTE: If you are already using Chainguard Containers, the same R2 domain host is used, and action may not be required.

Chainguard is updating how we serve our JavaScript Libraries. Beginning on Mar 4, 2026, Chainguard  Libraries for JavaScript will be delivered from Cloudflare R2 instead of Google Artifact Registry. This change is part of our ongoing investment in performance, scalability, and reliability for Chainguard Libraries customers.

This communication includes the following topics: 

What is changing?

We are migrating the hosting and delivery of Chainguard Libraries for JavaScript from Google Artifact Registry to Cloudflare R2. Customers who restrict outbound network access may need to allow traffic from the following third party host:

• Hostname: 9236a389bd48b984df91adc1bc924620.r2.cloudflarestorage.com
• Port: 443
• Protocol: HTTPS

Our documentation on Chainguard Libraries network requirements has been updated to include this new domain.

Why is Chainguard making this change?

This change is being made to improve the overall customer experience, including:

• Faster pull times and improved performance
• Better load distribution across customers
• Improved scalability and reliability

As adoption of Chainguard Libraries continues to grow, this infrastructure improvement ensures we can deliver consistent performance and reliability at scale.

How will this affect me?

If your organization restricts outbound network access via firewalls, VPNs, and IDS/IPS systems, you will need to add a rule to allow traffic from our R2 domain into your networks. If this domain is not allowlisted, pulls for Javascript Libraries may fail after Mar 4, 2026. This change only impacts Javascript Libraries at this time. However, we plan to serve Chainguard Libraries for our other language ecosystems from the same R2 domain at a future date.

What do I need to do?

1. Review your organization’s firewall or egress policies.
2. Ensure that your firewall allows traffic to and from the following host:
   1. Hostname: 9236a389bd48b984df91adc1bc924620.r2.cloudflarestorage.com
   2. Port: 443
   3. Protocol: HTTPS
3. Validate pulls in a staging or non-production environment.

FAQs

• Are other Chainguard products affected?
  The same R2 domain is used across our products including both Chainguard Containers and Chainguard Libraries. While this change only affects Chainguard Libraries for Javascript today, we plan to serve Chainguard Libraries for Python and Java from the same R2 host in the future.
• Where can I find the updated network requirements?
  See our updated documentation at https://edu.chainguard.dev/chainguard/libraries/network-requirements

Need help or have questions?

We're here to help - visit our support portal at support.chainguard.dev.

- Chainguard Team