Rewindex

Changescrates.ioRequest timeouts/Slow responses

crates.io: Major incident: Request timeouts/Slow responses

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

Part of an outage event

AWS us-east-1 outage, Dec 22, 2021 · 40 vendors, 40 incidents

crates.io’s incident started in the same window without naming AWS (timing only, not evidence of a link). (timing only, posted −15 min vs the first vendor naming AWS)

See the cascade chart and every vendor →

Detected automatically from incidents that started together and named the same provider. A link means one vendor’s incident named another, not a confirmed cause.

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: Request timeouts/Slow responses
AddedImpact#2
Before: not present
After: major
AddedStatus#3
Before: not present
After: resolved
AddedStart time#4
Before: not present
After: 2021-12-22 12:27 UTC
AddedResolved time#5
Before: not present
After: 2021-12-22 15:07 UTC
AddedAffected components#6
Before: not present
After: crates.io
AddedUpdateinvestigating#7
Before: not present
After: We are currently investigating an incident that causes slow responses and request timeouts on crates.io.
AddedUpdateinvestigating#8
Before: not present
After: We are continuing to investigate this issue.
AddedUpdatemonitoring#9
Before: not present
After: An outage of one of our service providers impacts our primary database and one of our application dynos. Currently, write operations will fail (uploading new crates, ...) and downloads will not be counted. About 25% of all download requests hit the affected dyno and will fail with a timeout. Cargo itself should be mostly unaffected due to retries.
AddedUpdatemonitoring#10
Before: not present
After: Our service provider is still working to restore full functionality, but unfortunately there is no ETA for full recovery at this time. We continue to monitor the situation.
AddedUpdateresolved#11
Before: not present
After: All of our affected infrastructure has recovered and full functionality has been restored. Some caches may require a bit of warming up, so some slow responses should still be expected.

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

Wednesday, December 22, 2021

1 incident change

All crates.io changescrates.io profileMarkdownJSON