Git index slow to update

What to do

• Check whether you use crates.io crates.io. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 3h 22m it lasted.

  Anything that failed between 2025-11-01 03:15 UTC and 2025-11-01 06:38 UTC may need a replay.

• Subscribe to crates.io's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=crates-io works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from crates.io 5

1. monitoringNov 1, 2025, 3:15 AM UTC

   Due to a large number of crate versions being published in the last few hours, the legacy Git crate index is currently approximately 245 crate versions (or about two hours) behind. The sparse index (which has been the default since Rust 1.70, released in June 2023) is unaffected.

   provider

2. monitoringNov 1, 2025, 4:04 AM UTC

   The queue burndown has slowed due to an unusual number of crate publishes in the last hour, but it is slowly making progress and is now at 206 pending syncs. It could be anywhere from 2-4 hours from here until it catches up.

   provider

3. monitoringNov 1, 2025, 5:01 AM UTC

   Now at 116 pending syncs. Probably 1½ hours before we're caught up, give or take.

   provider

4. monitoringNov 1, 2025, 6:01 AM UTC

   57 pending syncs.

   provider

5. resolvedNov 1, 2025, 6:38 AM UTC

   All published crates have been synced to the Git index, and there is now no backlog.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.