Vendor record
crates.io
Checked
Front door check counts and crates.io’s own incident posts. Use them to investigate a dependency; neither confirms what happened in your app.
Front door checks
We send a request to a documented crates.io endpoint and count the checks that got the answer it is documented to give.
Front door reachable in 2,879 of 2,879 checks with a clear answer, last 30 days, checked every 15 minutes from a single CheckUpstream location.
- Endpoint checked
- crates.io
- Scope
- apiNo vendor region
- First check in this window
- Latest clear answer
Checks 15 minutes apart cannot see disruptions shorter than that. A check that reached the front door does not show that every crates.io product, region or your app worked.
How we count front door checkscrates.io says
Incident posts from crates.io’s status page, with its titles, impact levels and times. They say what crates.io chose to post, not what reached your app.
A closed record shows when our record closed. Some older records closed when a post left the status page, without a resolution post from the vendor.
0
incidents crates.io posted, last 90 days
Most recent records · all dates
DoS Attack
Majorcrates.io’s postStarted, per crates.io
Closed in our record(1h 28m)
crates.io slowness
Minorcrates.io’s postStarted, per crates.io
Closed in our record(40m)
Reverse dependency pages unavailable
Minorcrates.io’s postStarted, per crates.io
Closed in our record(2d 22h)
Degraded performance on crates.io
Not specifiedcrates.io’s postStarted, per crates.io
Closed in our record(1h 8m)
Git index slow to update
Minorcrates.io’s postStarted, per crates.io
Closed in our record(2h 56m)
Your code, your dependencies
See which of your code paths call crates.io
Connect GitHub or GitLab to find where your public or private repository uses crates.io. Review each match and your alert settings.
Free to start. No credit card.
Use this record on your site
Add crates.io status to your page.
Choose the format your page supports, then copy the code. Badges show the recorded vendor status; they do not establish impact on your app.
Frequently Asked Questions
Is crates.io currently down?
crates.io's latest recorded status is Operational. Check the timestamp and linked source at the top of this page. A vendor status report does not establish whether your application was affected.
When did crates.io last have an outage?
The most recent closed incident record began 97 days ago and spans 1h 28m. The vendor reported a partial outage. Closure may reflect a disappeared post or an expired tracking period; it does not confirm vendor or application recovery. Check the dated history and source links.
Does CheckUpstream publish an uptime percentage for crates.io?
No. CheckUpstream checks crates.io’s front door every 15 minutes and publishes how many checks reached it over the last 30 days, with the endpoint checked. Checks 15 minutes apart cannot see disruptions shorter than that. A percentage would claim more than the checks can show.
How do I monitor crates.io in production?
Create your account, connect GitHub or GitLab and choose a public or private repository. Review the vendor matches and your alert settings. Available notification channels and history depend on your plan.
How does CheckUpstream track crates.io?
This record separates vendor-reported incidents from independent checks. Sources and coverage vary by vendor: review the linked source, check time and measurement scope. Neither kind of evidence establishes SLA credit eligibility.