Is crates.io down?

What works right now

• ●UpSparse indexYes: cargo can resolve versions (cargo build, cargo add, cargo update).200 in 36 ms
• ●UpCrate downloadsYes: cargo can download .crate files.200 in 40 ms
• ●UpWeb API (not critical)Yes: the website, cargo search, cargo publish, cargo owner and cargo yank work.200 in 50 ms

Failing for you? Check whether it is you

1. Is it you?

   Run curl -sI https://index.crates.io/config.json. A 200 means your network reaches the index; then look for a proxy or CARGO_HTTP_* setting, or a stale [source] override in ~/.cargo/config.toml.

What to do while crates.io is down

When crates.io is down, cargo cannot resolve or download crates you do not already have. Builds that only use crates already in your local registry cache keep working with --offline.

1. Build with what you already have

   Cargo keeps every crate it has downloaded in ~/.cargo/registry. Offline mode uses only that cache and fails only if a crate is missing.

   cargo build --offline
   # or for every cargo command in this shell:
   export CARGO_NET_OFFLINE=true

   Copy

2. Switch to a mirror (sparse protocol)

   Add this to ~/.cargo/config.toml. Mirrors serve the same files, and cargo still checks every download against the checksums in your Cargo.lock. Remove it when crates.io is back.

   [source.crates-io]
   replace-with = "mirror"
   
   [source.mirror]
   registry = "sparse+https://rsproxy.cn/index/"
   # another public mirror:
   # registry = "sparse+https://mirrors.ustc.edu.cn/crates.io-index/"

   Copy

3. Only the website is down?

   If the sparse index and downloads lines above are up and only the Web API is down, cargo build, cargo add and cargo update still work. Publishing, cargo search, cargo owner and cargo yank wait.

4. Vendor so this never blocks you again

   cargo vendor copies every dependency into vendor/ and prints the config to add. Commit it, or cache ~/.cargo/registry in CI.

   cargo vendor
   # then paste the [source] lines it prints into .cargo/config.toml

   Copy

Last 24 hours

Last 30 days

Incident timeline

Outages our checks saw, and incidents from the official status page, newest first.

1. OfficialJul 11, 14:22 UTC · 1.3 hDoS Attack

   This incident has been resolved. Big thanks to Fastly for providing their CDN services and their fast response time!

Official status

The official page: https://status.crates.io/.

Get alerts, or show it in your README

Follow the RSS feed of crates.io incidents in any reader, or paste this badge into a README; it updates itself.

[![crates.io status](https://tensorust-status.vercel.app/api/badge?id=crates-io)](https://tensorust.com/status/crates-io/)

How we check crates.io

Every 5 minutes, from Washington, D.C., with no API key. A failed check is retried once after 2 seconds before it counts; crates.io is down when every critical check fails, and degraded when some do or the official page reports a problem.

• https://index.crates.io/config.json: What cargo reads to resolve versions.
• https://static.crates.io/crates/serde/serde-1.0.0.crate: Where cargo downloads .crate files.
• https://crates.io/api/v1/crates/serde/1.0.0: The website and its API (search, publish, owners) (not critical: a failure shows as degraded, not down).

Other services