CheckUpstream measured crates.io at 100.000% availability across 2029 independent checks (global · api). 5 incidents were recorded in the past 12 months; the most recent resolved 51 days ago after 1 hour. Status signals are polled from crates.io's official Atlassian Statuspage status page, alongside independent probes and community reports.
90 days measured availability how this is computed
100.000%
global · api · n=2029 · p95 742ms (30d)
Share of our own checks against crates.io endpoints that returned crates.io's expected response. Evidence that their API edge is answering correctly — not that every product behind it works.
Vendor disclosed: 2 incidents · 90 of 90 days with none posted · 0m of declared impact
Fewer incidents in the last 30 days than 55% of 232 tracked services.
Share of each window with no impact declared by crates.io
7d
100.000%
30d
100.000%
90d
100.000%
180d
99.980%
1y
99.990%
Does crates.io actually matter to you?
A crates.io outage only matters if something you ship depends on it. Point us at a public repository and we will read its dependencies and tell you — no account, nothing stored.
Check a repository →Live crates.io status for your README or docs. Updates itself — no API key, no maintenance.
[](https://checkupstream.com/reliability/crates-io)GitHub READMEs, GitLab, MDX docs — links to the live reliability page.
crates.io is currently Operational. CheckUpstream tracks crates.io in real-time across the official status page, RSS / Atom feeds, and community telemetry. Refresh this page for the latest reading.
crates.io's last resolved incident started 51 days ago and lasted 1h 28m (a partial outage).
Looking for the live "is crates.io down" view? See the crates.io Live status page.
Apr 14, 20:48 UTC · resolved in 2h 56m · Resolved
crates.io's 30-day measured availability is 100.000%, from CheckUpstream's own probes against crates.io endpoints. It is the share of checks that returned the expected response, not a figure taken from crates.io's status page.
Sign up to CheckUpstream and add crates.io to a watchlist. We send incident alerts via Slack, email, webhook, or PagerDuty within seconds of detection, covering both the official status page and community signals (HN, Reddit, Bluesky, Cloudflare Radar).
We poll crates.io's official status page on a 1-5 minute cadence, parse its RSS / Atom feed as a fallback, ingest community signals from social platforms, and aggregate per-org SDK telemetry. Multiple sources reduce false positives versus any single feed alone.