Crates Io status history
Current state: operational — “All Systems Operational” per https://status.crates.io (Atlassian Statuspage), checked 2026-09-24 12:28 UTC.
How long do Crates Io incidents last?
From 9 incidents with a vendor-posted start and resolve time. Longest on record: Reverse dependency pages unavailable — 2.9 days (2026-05-23 18:47 UTC). Excluded, never estimated: nothing. Duration is the gap between the vendor's own posted timestamps — it is not measured downtime, uptime or an SLA figure, and a vendor that posts every blip will look worse here than one that posts nothing. Same rule as the outage-duration dataset.
Incidents on record (9)
| Started | Incident | Status | Impact | Duration |
|---|---|---|---|---|
| 2026-07-11 14:22 UTC | DoS Attack | resolved | major | 1 h 19 min |
| 2026-06-14 01:20 UTC | crates.io slowness | resolved | minor | 33 min |
| 2026-05-23 18:47 UTC | Reverse dependency pages unavailable | resolved | minor | 2 d 22 h |
| 2026-05-20 15:52 UTC | Degraded performance on crates.io | resolved | none | 1 h 05 min |
| 2026-04-14 20:48 UTC | Git index slow to update | resolved | minor | 2 h 56 min |
| 2026-02-12 19:36 UTC | Git index slow to update | resolved | minor | 9 min |
| 2025-11-10 23:56 UTC | Degraded performance on crates.io | resolved | minor | 1 h 17 min |
| 2025-11-01 03:15 UTC | Git index slow to update | resolved | minor | 3 h 22 min |
| 2025-09-02 22:48 UTC | Sparse Index CDN Invalidations Slow to Update | resolved | minor | 44 min |
Titles, statuses and impact levels are the vendor's own words. Durations marked approx. are inferred from the poll that first found the incident gone. Shows the latest 60; the JSON has everything we hold (up to 400 days).
Watch Crates Io with the template
Put this in config.json of your fork and add a WEBHOOK_URL secret:
{
"vendors": [
"crates-io"
],
"format": "auto",
"map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
"unreachable_after": 3,
"mute_maintenance": false
}
