30 days uptime
100.000%
30 of 30 days clean · 0m total downtime
All windows
Last resolved incident
2 days ago · lasted 2d 22h · Minor
5/23/2026, 6:47:52 PM · resolved 5/26/2026, 5:00:57 PM · Resolved
5/20/2026, 3:52:07 PM · resolved 5/20/2026, 5:00:25 PM · Resolved
4/14/2026, 8:48:45 PM · resolved 4/14/2026, 11:45:36 PM · Resolved
Official status page: https://status.crates.io (opens in new tab)
Live status pill for crates.io. Updates automatically — no maintenance, no API key.
PREVIEW
Drop into any HTML page — README, docs, vendor homepage. No iframe, no dependencies.
<script src="https://checkupstream.com/embed/badge.js?service=crates-io"></script>Self-contained, CSP-friendly. Theme + size are query params; revalidates every 60s.
<iframe src="https://checkupstream.com/embed/crates-io" style="border:0;width:260px;height:44px" loading="lazy" title="crates.io status badge"></iframe>GitHub READMEs, GitLab, MDX docs — links to the live reliability page.
[](https://checkupstream.com/reliability/crates-io)Useful for status-page composers (Notion, Slab, custom dashboards) that accept image URLs.
https://checkupstream.com/embed/crates-io/badge.svgcrates.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 2 days ago and lasted 2d 22h (degraded performance).
Looking for the live "is crates.io down" view? See the crates.io Status page.
crates.io's 30-day customer-perceived uptime is 100.000%. The figure is weighted (full-outage = 1.0, degraded = 0.3) so component blips don't collapse the score the way a raw incident-count would.
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.