Rewindex

Changescrates.iocrates.io outage

crates.io: Major incident: crates.io outage

Major incidentmajor (vendor)Changed Detected stspg.io (opens in new tab)
Summary

Summary pending. The diff below shows exactly what changed.

Incident page: the full timeline of updates

What changed

Struck in red is what crates.io removed; blue is what they added. Muted text is unchanged context.

AddedTitle#1
Before: not present
After: crates.io outage
AddedImpact#2
Before: not present
After: major
AddedStatus#3
Before: not present
After: resolved
AddedStart time#4
Before: not present
After: 2020-06-12 18:59 UTC
AddedResolved time#5
Before: not present
After: 2020-06-12 19:21 UTC
AddedAffected components#6
Before: not present
After: crates.io
AddedUpdateinvestigating#7
Before: not present
After: We are aware of an issue preventing users from accessing crates.io directly or through its API
AddedUpdateidentified#8
Before: not present
After: The issue appears to be caused by an outage in Cloudfront.
AddedUpdatemonitoring#9
Before: not present
After: A fix has been implemented and we are monitoring the results.
AddedUpdateresolved#10
Before: not present
After: This incident has been resolved.

First version of this incident archived by Rewindex. View the live incident (opens in new tab).

Archive proof

Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.

How the archive is checked, and what it cannot prove.

Rewindex captured this after the last checkpoint; the next run (00:41 UTC) commits it.

This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.

History of this incident

Friday, June 12, 2020

1 incident change

All crates.io changescrates.io profileMarkdownJSON