Resolved after 2 hours 56 minutes, affecting crates.io, on April 14, 2026.
The background worker has been told to get itself together. The queue is now trending downwards, but git index updates are still running an hour behind. We are continuing to monitor, but we expect this to resolve over the next few hours.
Affected components
Update timeline
- investigating Apr 14, 2026, 08:48 PM UTC
The crates.io background worker is having a bad morning, and a backlog of Git index updates has accumulated. We have given the worker some coffee and it's catching up, but index updates for newly-published crates are running about an hour behind right now. The sparse index (used by default by all modern Rust versions) is unaffected.
- monitoring Apr 14, 2026, 09:08 PM UTC
The background worker has been told to get itself together. The queue is now trending downwards, but git index updates are still running an hour behind. We are continuing to monitor, but we expect this to resolve over the next few hours.
- resolved Apr 14, 2026, 11:44 PM UTC
The indexes are now back to normal operations.
Your product runs on more than crates.io
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services