The Rust Programming Language Outage History
9 incidents recorded over the last 365 days, 9 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded The Rust Programming Language Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Nov 4, 2026 | Git index updates delayedThe queue has been processed and new publishes are behaving normally again. | 2h 18m | Resolved |
| Oct 26, 2026 | Background job processing stalledThis incident has been resolved. | 1h 10m | Resolved |
| Jul 11, 2026 | DoS AttackThis incident has been resolved. Big thanks to Fastly for providing their CDN services and their fast response time! | 1h 19m | Resolved |
| Jun 14, 2026 | crates.io slownessThe primary source of the load appears to have been a scraper abusing our API. We have blocked the scraper and the replica database has returned to its normal heavily loaded state instead of being overloaded. | 33 min | Resolved |
| May 23, 2026 | Reverse dependency pages unavailableThis incident has been resolved. | 70h 12m | Resolved |
| May 20, 2026 | Degraded performance on crates.ioAll endpoints are now operational and available again. | 1h 5m | Resolved |
| Apr 14, 2026 | Git index slow to updateThe indexes are now back to normal operations. | 2h 56m | Resolved |
| Feb 12, 2026 | Git index slow to updateThe background worker has caught up, and crate publishes are now updating normally in both indexes. | 9 min | Resolved |
| Nov 10, 2025 | Degraded performance on crates.ioEverything continues to look stable, so we can consider this resolved. | 1h 17m | Resolved |
Hear about the next one while it is open
Everything above is a record written after the fact. We can email you when the next The Rust Programming Language incident opens instead, at the point where knowing still changes what you do.
Free, no password, no card. Unsubscribe in one click.
How to Read This The Rust Programming Language Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before The Rust Programming Language acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single The Rust Programming Language outage in this window ran 2d 22h, against a mean recovery of 8h 60m. If you depend on The Rust Programming Language in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.