Is crates.io down?
Partially downchecked 4 minutes ago
Part of crates.io is not answering our probes: its web surface from South America and Australia. Its API, the surface we treat as the service's own, answered from every region we check.
As of Sep 13, 2026, 5:15 PM UTC, crates.io answered RealUptime's probes in all 10 regions that returned a reading. Our Australia and South America probes reached some of its surfaces and not others.
We have an outage open for crates.io, 2h 27m so far.
Last outage: 3h on Sep 12, 2026 (web surface, from South America, intermittent).
crates.io reports: All systems operational (“All Systems Operational”)
crates.io's own component breakdown, as they publish it
- crates.ioOperational
- docs.rsOperational
These are crates.io's components, named and scored by crates.io. We do not map them onto the functions we check above, because we have no way to know which of their components our checks touch. Two lists, side by side, neither one rewriting the other.
This is crates.io's own claim about their service, shown separately from what we measured. We never change our own numbers based on what a vendor reports, and this reading never changes theirs. Read both.
crates.io response time, by region
Is it crates.io, or is it you?
Watching an outage above does not tell you whether your own connection or site is also having a problem. Enter your own URL for one live check, right now, no signup. This checks the site you enter, not crates.io -- it cannot diagnose crates.io's own systems.
What we measured, function by function
crates.io answers on more than one surface, and they can fail apart. Each row is one surface, checked from the same regions. The verdict above follows the api row, because that is the surface we treat as this service's own; a failure on any other row is a partial outage, not a full one.
- WebUS-East: OperationalUS-West: OperationalEurope: OperationalAsia-Pacific: OperationalUS-Central: OperationalCanada: OperationalUK: OperationalSoutheast Asia: OperationalAustralia: DownSouth America: Down
- APIprimaryUS-East: OperationalUS-West: OperationalEurope: OperationalAsia-Pacific: OperationalUS-Central: OperationalCanada: OperationalUK: OperationalSoutheast Asia: OperationalAustralia: OperationalSouth America: Operational
Open incident
What we measured, and what people reported
- North AmericaOperationalUS-East, US-West, US-Central, Canada
- US-EastOperationallatency: 179msstatus code: 200checked: Sep 13, 2026, 5:15 PM UTC0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach crates.io normally. We do not have enough reports from US-East to say anything about what people there are seeing.
- US-WestOperationallatency: 102msstatus code: 200checked: Sep 13, 2026, 5:00 PM UTC0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach crates.io normally. We do not have enough reports from US-West to say anything about what people there are seeing.
- US-CentralOperationallatency: 148msstatus code: 200checked: Sep 13, 2026, 5:11 PM UTC0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach crates.io normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
- CanadaOperationallatency: 140msstatus code: 200checked: Sep 13, 2026, 5:10 PM UTC0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach crates.io normally. We do not have enough reports from Canada to say anything about what people there are seeing.
- South AmericaPartially downlatency: 36msstatus code: 200checked: Sep 13, 2026, 4:58 PM UTC0 people in the last 5 minutesNot enough reports to sayOur South America probes reach crates.io normally. We do not have enough reports from South America to say anything about what people there are seeing.
- EuropeOperationalEurope, UK
- EuropeOperationallatency: 101msstatus code: 200checked: Sep 13, 2026, 5:14 PM UTC0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach crates.io normally. We do not have enough reports from Europe to say anything about what people there are seeing.
- UKOperationallatency: 94msstatus code: 200checked: Sep 13, 2026, 5:13 PM UTC0 people in the last 5 minutesNot enough reports to sayOur UK probes reach crates.io normally. We do not have enough reports from UK to say anything about what people there are seeing.
- Asia PacificPartially downAsia-Pacific, Southeast Asia, Australia
- Asia-PacificOperationallatency: 407msstatus code: 200checked: Sep 13, 2026, 5:11 PM UTC0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach crates.io normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
- Southeast AsiaOperationallatency: 102msstatus code: 200checked: Sep 13, 2026, 5:03 PM UTC0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach crates.io normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
- AustraliaPartially downlatency: 225msstatus code: 200checked: Sep 13, 2026, 4:52 PM UTC0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach crates.io normally. We do not have enough reports from Australia to say anything about what people there are seeing.
Somewhere else or not sure: 0 people in the last 5 minutes
These are unverified reports from people using crates.io, counted separately from what our own probes measure. Anyone can file one, no account is needed, and the region on a report is chosen by the person filing it. We never open, extend or close an outage in our record based on report volume: only our own measurements do that. We have not received any reports for crates.io yet, which is not evidence that nothing is wrong.
Recent outages
measured entries are our own probes' readings; declared entries are the vendor's. How this check works
We have been measuring crates.io since August 22, 2026. We show nothing from before that date, and we never add an outage we did not observe ourselves, from any source.
Need this in writing? Generate an SLA evidence report for crates.io covering any window you pick, with our measurements and crates.io's own claim at the time, side by side.
Full availability history for crates.io: 90-day availability by region, month-by-month uptime, and every incident on record.
Monitor your own site the same way
This page shows what we see when we check this service, using the same ten regions, for a site you run. RealUptime Monitor watches your own servers from inside your network, and it starts free.
Start monitoring your own serversTell me when this goes down
Get told when we measure this
We will tell you when our probes stop reaching crates.io, and again when they can reach it again. That is our own measurement from ten regions, not crates.io's status page. No account, no card.
Put this badge in your README
Live, from this page's own readings.[](https://realuptime.io/outages/crates-io)<a href="https://realuptime.io/outages/crates-io"><img src="https://realuptime.io/outages/crates-io/badge.svg?days=30" alt="crates.io uptime measured by RealUptime"></a>The badge shows the share of our probes that succeeded over the last 30 days, and the window is printed on it so the number always says what period it covers. If our readings go stale it says stale, and if we have no readings it says so: it will not show green on data we cannot vouch for. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.
What crates.io's SLA implies, from our measurement
Below your target
We measured 2h 27m of downtime for crates.io over the 545h 20m since we started watching it on 2026-08-22, which is 99.5493% uptime by our reading. A 99.9% target allows 32 minutes over that period.
That is 1h 54m more than the target allows. The figure above is the pro-rata share of one month's fee for the time we could not reach it. Your contract probably uses a tiered credit schedule instead, and we have not read it, so treat this as one common way to reason about a credit rather than the amount they owe.
Separately, we measured 14h 31m where only one of our regions was affected. It is excluded above because most SLAs would not credit it, and it is the kind of outage a single-vantage monitor never sees at all.
This is computed from our own probe measurements, not from crates.io's SLA instrumentation. Their contract is normally measured against their own systems, with their own exclusions and a claim window, so their figure and ours will differ. Use this to start the conversation and ask for their number. It is not legal advice and it is not a determination of what you are owed.