esm.sh CDN Storage Errors and Cloudflare R2 Timeouts Breaking Package Downloads

What this error means

Storage error, please try again — dial tcp 172.64.66.1:443: i/o timeout is a esm.sh failure pattern reported for developers trying to fix esm.sh cdn returning storage errors and r2 timeout when fetching typescript definition files. Based on the imported evidence, treat this as a tool-specific troubleshooting page rather than a generic API error.

Why this happens

esm.sh issue #1358: Fetching vitest@4.1.6/dist/index.d.ts returns ‘Storage error, please try again’. JS files return ‘dial tcp 172.64.66.1:443: i/o timeout’ from Cloudflare R2 storage backend (d5197bc43c609ab3101c8fc931edb5e7.r2.cloudflarestorage.com). All /dist/ files affected. Reported 2026-05-12.

Common causes

• esm.sh is a popular CDN for npm packages used by Deno and modern JS toolchains. When esm.sh’s Cloudflare R2 backend experiences storage errors or timeouts, developers cannot import or resolve package types (.d.ts files), breaking builds and type checking. The error affects all /dist/ files for affected packages, making entire package versions unusable through the CDN.
• esm.sh issue #1358: Fetching vitest@4.1.6/dist/index.d.ts returns ‘Storage error, please try again’. JS files return ‘dial tcp 172.64.66.1:443: i/o timeout’ from Cloudflare R2 storage backend (d5197bc43c609ab3101c8fc931edb5e7.r2.cloudflarestorage.com). All /dist/ files affected. Reported 2026-05-12.

Quick fixes

1. Confirm the exact error signature matches Storage error, please try again — dial tcp 172.64.66.1:443: i/o timeout.
2. Check the esm.sh account, local tool state, and provider configuration involved in the failing workflow.
3. Compare the failing environment with a known working setup, then change one configuration value at a time.

Platform/tool-specific checks

• Verify the command, editor, extension, or API client that produced the error.
• Compare local settings with CI, deployment, or editor-level settings when the error appears in only one environment.
• Avoid deleting credentials, local model data, or project settings until the failing scope is clear.

Step-by-step troubleshooting

1. Capture the exact error message and the command, editor action, or request that triggered it.
2. Check whether the failure is account/auth, quota/rate, model/provider, local runtime, or deployment configuration.
3. Review the source evidence below and compare it with your environment.
4. Apply one change at a time and rerun the smallest failing action.
5. Keep the working fix documented for the team or deployment environment.

How to prevent it

• Keep provider/tool configuration documented.
• Record non-secret diagnostics such as tool version, provider name, model name, and command path.
• Add a lightweight check before CI or production workflows depend on the tool.

Sources checked

• https://github.com/esm-dev/esm.sh/issues/1358

Evidence note: esm.sh issue #1358: Fetching vitest@4.1.6/dist/index.d.ts returns ‘Storage error, please try again’. JS files return ‘dial tcp 172.64.66.1:443: i/o timeout’ from Cloudflare R2 storage backend (d5197bc43c609ab3101c8fc931edb5e7.r2.cloudflarestorage.com). All /dist/ files affected. Reported 2026-05-12.

Related errors

• Cloudflare R2 storage timeout errors
• esm.sh package not found or unavailable
• CDN TypeScript definition fetch failures

FAQ

What should I check first?

Start with the exact Storage error, please try again — dial tcp 172.64.66.1:443: i/o timeout text and the smallest action that reproduces it.

Can I ignore this error?

No. Treat it as a failed esm.sh workflow until the root cause is understood.

Is this guaranteed to have one fix?

No. The imported evidence supports the troubleshooting path above, but tool behavior can vary by account, plan, version, provider, and local configuration.

How do I know the fix worked?

Rerun the same command, editor action, or request. The fix is working when that action completes without Storage error, please try again — dial tcp 172.64.66.1:443: i/o timeout.