Skip to content

Outage tracker / crates.io

Is crates.io down?

I'm having a problem

Operationalchecked 5 minutes ago

We reached crates.io from all 10 regions we check.

As of Oct 5, 2026, 8:59 PM UTC, crates.io answered RealUptime's probes in all 10 regions that returned a reading.

Functional endpoints verified

No outage recorded in the 44 days we have measured crates.io (since Aug 22, 2026).

our independent probeslive · checked Oct 5, 2026, 8:59 PM UTC
US-East256 msOperational
US-West265 msOperational
Europe144 msOperational
Asia-Pacific52 msOperational
US-Central174 msOperational
Canada186 msOperational
UK92 msOperational
Southeast Asia177 msOperational
Australia654 msOperational
South America59 msOperational
their status pagetheir claim, not our reading

crates.io reports: All systems operational (“All Systems Operational”)

from crates.io's own status page, checked Oct 5, 2026, 8:52 PM UTC

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

US-East
443msp95 · latest
1s500ms0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 580ms2026-09-07 UTC: p95 672ms2026-09-08 UTC: p95 595ms2026-09-09 UTC: p95 714ms2026-09-10 UTC: p95 627ms2026-09-11 UTC: p95 672ms2026-09-12 UTC: p95 273ms2026-09-13 UTC: p95 242ms2026-09-14 UTC: p95 291ms2026-09-15 UTC: p95 246ms2026-09-16 UTC: p95 444ms2026-09-17 UTC: p95 544ms2026-09-18 UTC: p95 487ms2026-09-19 UTC: p95 448ms2026-09-20 UTC: p95 435ms2026-09-21 UTC: p95 433ms2026-09-22 UTC: p95 447ms2026-09-23 UTC: p95 477ms2026-09-24 UTC: p95 459ms2026-09-25 UTC: p95 461ms2026-09-26 UTC: p95 384ms2026-09-27 UTC: p95 384ms2026-09-28 UTC: p95 361ms2026-09-29 UTC: p95 356ms2026-09-30 UTC: p95 319ms2026-10-01 UTC: p95 402ms2026-10-02 UTC: p95 432ms2026-10-03 UTC: p95 470ms2026-10-04 UTC: p95 472ms2026-10-05 UTC: p95 443ms
Sep 6Sep 20Oct 5
US-West
268msp95 · latest
1s500ms0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 554ms2026-09-07 UTC: p95 514ms2026-09-08 UTC: p95 378ms2026-09-09 UTC: p95 355ms2026-09-10 UTC: p95 351ms2026-09-11 UTC: p95 512ms2026-09-12 UTC: p95 554ms2026-09-13 UTC: p95 511ms2026-09-14 UTC: p95 600ms2026-09-15 UTC: p95 656ms2026-09-16 UTC: p95 708ms2026-09-17 UTC: p95 269ms2026-09-18 UTC: p95 287ms2026-09-19 UTC: p95 264ms2026-09-20 UTC: p95 291ms2026-09-21 UTC: p95 281ms2026-09-22 UTC: p95 336ms2026-09-23 UTC: p95 332ms2026-09-24 UTC: p95 328ms2026-09-25 UTC: p95 388ms2026-09-26 UTC: p95 363ms2026-09-27 UTC: p95 286ms2026-09-28 UTC: p95 348ms2026-09-29 UTC: p95 292ms2026-09-30 UTC: p95 281ms2026-10-01 UTC: p95 334ms2026-10-02 UTC: p95 381ms2026-10-03 UTC: p95 284ms2026-10-04 UTC: p95 280ms2026-10-05 UTC: p95 268ms
Sep 6Sep 20Oct 5
Europe
306msp95 · latest
1s500ms0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 307ms2026-09-07 UTC: p95 307ms2026-09-08 UTC: p95 406ms2026-09-09 UTC: p95 309ms2026-09-10 UTC: p95 309ms2026-09-11 UTC: p95 318ms2026-09-12 UTC: p95 318ms2026-09-13 UTC: p95 308ms2026-09-14 UTC: p95 314ms2026-09-15 UTC: p95 313ms2026-09-16 UTC: p95 529ms2026-09-17 UTC: p95 497ms2026-09-18 UTC: p95 476ms2026-09-19 UTC: p95 478ms2026-09-20 UTC: p95 524ms2026-09-21 UTC: p95 303ms2026-09-22 UTC: p95 301ms2026-09-23 UTC: p95 336ms2026-09-24 UTC: p95 408ms2026-09-25 UTC: p95 421ms2026-09-26 UTC: p95 406ms2026-09-27 UTC: p95 407ms2026-09-28 UTC: p95 373ms2026-09-29 UTC: p95 369ms2026-09-30 UTC: p95 306ms2026-10-01 UTC: p95 375ms2026-10-02 UTC: p95 315ms2026-10-03 UTC: p95 307ms2026-10-04 UTC: p95 299ms2026-10-05 UTC: p95 306ms
Sep 6Sep 20Oct 5
Asia-Pacific
733msp95 · latest
2s1s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 966ms2026-09-07 UTC: p95 946ms2026-09-08 UTC: p95 1.3s2026-09-09 UTC: p95 1.1s2026-09-10 UTC: p95 907ms2026-09-11 UTC: p95 830ms2026-09-12 UTC: p95 478ms2026-09-13 UTC: p95 937ms2026-09-14 UTC: p95 800ms2026-09-15 UTC: p95 927ms2026-09-16 UTC: p95 672ms2026-09-17 UTC: p95 729ms2026-09-18 UTC: p95 631ms2026-09-19 UTC: p95 355ms2026-09-20 UTC: p95 475ms2026-09-21 UTC: p95 563ms2026-09-22 UTC: p95 561ms2026-09-23 UTC: p95 868ms2026-09-24 UTC: p95 785ms2026-09-25 UTC: p95 538ms2026-09-26 UTC: p95 775ms2026-09-27 UTC: p95 1.2s2026-09-28 UTC: p95 639ms2026-09-29 UTC: p95 981ms2026-09-30 UTC: p95 594ms2026-10-01 UTC: p95 752ms2026-10-02 UTC: p95 544ms2026-10-03 UTC: p95 474ms2026-10-04 UTC: p95 674ms2026-10-05 UTC: p95 733ms
Sep 6Sep 20Oct 5
US-Central
387msp95 · latest
1s500ms0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 841ms2026-09-07 UTC: p95 905ms2026-09-08 UTC: p95 817ms2026-09-09 UTC: p95 719ms2026-09-10 UTC: p95 837ms2026-09-11 UTC: p95 560ms2026-09-12 UTC: p95 368ms2026-09-13 UTC: p95 279ms2026-09-14 UTC: p95 333ms2026-09-15 UTC: p95 363ms2026-09-16 UTC: p95 398ms2026-09-17 UTC: p95 465ms2026-09-18 UTC: p95 312ms2026-09-19 UTC: p95 333ms2026-09-20 UTC: p95 250ms2026-09-21 UTC: p95 279ms2026-09-22 UTC: p95 504ms2026-09-23 UTC: p95 520ms2026-09-24 UTC: p95 469ms2026-09-25 UTC: p95 370ms2026-09-26 UTC: p95 495ms2026-09-27 UTC: p95 292ms2026-09-28 UTC: p95 296ms2026-09-29 UTC: p95 311ms2026-09-30 UTC: p95 431ms2026-10-01 UTC: p95 370ms2026-10-02 UTC: p95 423ms2026-10-03 UTC: p95 396ms2026-10-04 UTC: p95 362ms2026-10-05 UTC: p95 387ms
Sep 6Sep 20Oct 5
Canada
386msp95 · latest
1s500ms0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 761ms2026-09-07 UTC: p95 721ms2026-09-08 UTC: p95 760ms2026-09-09 UTC: p95 866ms2026-09-10 UTC: p95 738ms2026-09-11 UTC: p95 554ms2026-09-12 UTC: p95 418ms2026-09-13 UTC: p95 218ms2026-09-14 UTC: p95 275ms2026-09-15 UTC: p95 272ms2026-09-16 UTC: p95 327ms2026-09-17 UTC: p95 363ms2026-09-18 UTC: p95 397ms2026-09-19 UTC: p95 364ms2026-09-20 UTC: p95 411ms2026-09-21 UTC: p95 449ms2026-09-22 UTC: p95 354ms2026-09-23 UTC: p95 553ms2026-09-24 UTC: p95 408ms2026-09-25 UTC: p95 448ms2026-09-26 UTC: p95 346ms2026-09-27 UTC: p95 441ms2026-09-28 UTC: p95 375ms2026-09-29 UTC: p95 394ms2026-09-30 UTC: p95 331ms2026-10-01 UTC: p95 417ms2026-10-02 UTC: p95 407ms2026-10-03 UTC: p95 410ms2026-10-04 UTC: p95 311ms2026-10-05 UTC: p95 386ms
Sep 6Sep 20Oct 5
UK
164msp95 · latest
500ms250ms0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 500ms. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 275ms2026-09-07 UTC: p95 259ms2026-09-08 UTC: p95 271ms2026-09-09 UTC: p95 305ms2026-09-10 UTC: p95 247ms2026-09-11 UTC: p95 230ms2026-09-12 UTC: p95 171ms2026-09-13 UTC: p95 179ms2026-09-14 UTC: p95 147ms2026-09-15 UTC: p95 185ms2026-09-16 UTC: p95 178ms2026-09-17 UTC: p95 175ms2026-09-18 UTC: p95 179ms2026-09-19 UTC: p95 162ms2026-09-20 UTC: p95 151ms2026-09-21 UTC: p95 176ms2026-09-22 UTC: p95 272ms2026-09-23 UTC: p95 210ms2026-09-24 UTC: p95 168ms2026-09-25 UTC: p95 163ms2026-09-26 UTC: p95 211ms2026-09-27 UTC: p95 185ms2026-09-28 UTC: p95 192ms2026-09-29 UTC: p95 145ms2026-09-30 UTC: p95 175ms2026-10-01 UTC: p95 276ms2026-10-02 UTC: p95 305ms2026-10-03 UTC: p95 313ms2026-10-04 UTC: p95 244ms2026-10-05 UTC: p95 164ms
Sep 6Sep 20Oct 5
Southeast Asia
328msp95 · latest
2s1s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 886ms2026-09-07 UTC: p95 985ms2026-09-08 UTC: p95 1.0s2026-09-09 UTC: p95 923ms2026-09-10 UTC: p95 869ms2026-09-11 UTC: p95 1.1s2026-09-12 UTC: p95 313ms2026-09-13 UTC: p95 332ms2026-09-14 UTC: p95 550ms2026-09-15 UTC: p95 306ms2026-09-16 UTC: p95 284ms2026-09-17 UTC: p95 329ms2026-09-18 UTC: p95 668ms2026-09-19 UTC: p95 441ms2026-09-20 UTC: p95 414ms2026-09-21 UTC: p95 566ms2026-09-22 UTC: p95 652ms2026-09-23 UTC: p95 541ms2026-09-24 UTC: p95 659ms2026-09-25 UTC: p95 418ms2026-09-26 UTC: p95 372ms2026-09-27 UTC: p95 414ms2026-09-28 UTC: p95 554ms2026-09-29 UTC: p95 404ms2026-09-30 UTC: p95 333ms2026-10-01 UTC: p95 514ms2026-10-02 UTC: p95 627ms2026-10-03 UTC: p95 656ms2026-10-04 UTC: p95 757ms2026-10-05 UTC: p95 328ms
Sep 6Sep 20Oct 5
Australia
654msp95 · latest
1s500ms0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 982ms2026-09-07 UTC: p95 780ms2026-09-08 UTC: p95 700ms2026-09-09 UTC: p95 640ms2026-09-10 UTC: p95 763ms2026-09-11 UTC: p95 677ms2026-09-12 UTC: p95 549ms2026-09-13 UTC: p95 570ms2026-09-14 UTC: p95 458ms2026-09-15 UTC: p95 570ms2026-09-16 UTC: p95 581ms2026-09-17 UTC: p95 579ms2026-09-18 UTC: p95 512ms2026-09-19 UTC: p95 614ms2026-09-20 UTC: p95 574ms2026-09-21 UTC: p95 633ms2026-09-22 UTC: p95 851ms2026-09-23 UTC: p95 429ms2026-09-24 UTC: p95 580ms2026-09-25 UTC: p95 545ms2026-09-26 UTC: p95 583ms2026-09-27 UTC: p95 621ms2026-09-28 UTC: p95 541ms2026-09-29 UTC: p95 715ms2026-09-30 UTC: p95 440ms2026-10-01 UTC: p95 430ms2026-10-02 UTC: p95 603ms2026-10-03 UTC: p95 580ms2026-10-04 UTC: p95 480ms2026-10-05 UTC: p95 654ms
Sep 6Sep 20Oct 5
South America
376msp95 · latest
2s1s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 595ms2026-09-07 UTC: p95 635ms2026-09-08 UTC: p95 523ms2026-09-09 UTC: p95 678ms2026-09-10 UTC: p95 695ms2026-09-11 UTC: p95 578ms2026-09-12 UTC: p95 512ms2026-09-13 UTC: p95 428ms2026-09-14 UTC: p95 463ms2026-09-15 UTC: p95 483ms2026-09-16 UTC: p95 266ms2026-09-17 UTC: p95 435ms2026-09-18 UTC: p95 249ms2026-09-19 UTC: p95 387ms2026-09-20 UTC: p95 557ms2026-09-21 UTC: p95 143ms2026-09-22 UTC: p95 251ms2026-09-23 UTC: p95 262ms2026-09-24 UTC: p95 298ms2026-09-25 UTC: p95 500ms2026-09-26 UTC: p95 716ms2026-09-27 UTC: p95 264ms2026-09-28 UTC: p95 334ms2026-09-29 UTC: p95 335ms2026-09-30 UTC: p95 276ms2026-10-01 UTC: p95 356ms2026-10-02 UTC: p95 347ms2026-10-03 UTC: p95 1.1s2026-10-04 UTC: p95 596ms2026-10-05 UTC: p95 376ms
Sep 6Sep 20Oct 5
Why some readings show as awaiting data. 1 of 20 readings for crates.io came back as a filtered response to our automated checks (a response code that refuses automated clients, such as 403, 405, 406, 429 or 451, a redirect loop, or a timeout we could rule out as a real outage using a second endpoint) rather than a normal success or failure. That tells us about our own probe's reception, not about crates.io's actual health, so we publish no verdict for those readings rather than guessing in either direction. Read how we tell the difference.

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: Awaiting dataUK: OperationalSoutheast Asia: OperationalAustralia: OperationalSouth America: Operational
  • APIprimaryUS-East: OperationalUS-West: OperationalEurope: OperationalAsia-Pacific: OperationalUS-Central: OperationalCanada: OperationalUK: OperationalSoutheast Asia: OperationalAustralia: OperationalSouth America: Operational

Get an email when we see crates.io go down, and when it is back

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.

Delivery channel

Double opt-in: nothing is sent until you click the link in the confirmation email. One email when a measured outage opens, one when it closes, and a one-click unsubscribe in every one. We do not send anything else to this address.

What are you seeing? (optional)

No account needed, and we never store your IP address. Reports are counted separately from our own measurements and are always shown as unverified.

What we measured, and what people reported

  • North America
    OperationalUS-East, US-West, US-Central, Canada
    • US-East
      Operationallatency: 256msstatus code: 200checked: Oct 5, 2026, 8:50 PM UTC
      0 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-West
      Operationallatency: 265msstatus code: 200checked: Oct 5, 2026, 8:47 PM UTC
      0 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-Central
      Operationallatency: 174msstatus code: 200checked: Oct 5, 2026, 8:17 PM UTC
      0 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.
    • Canada
      Operationallatency: 186msstatus code: 200checked: Oct 5, 2026, 8:26 PM UTC
      0 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 America
    Operationallatency: 59msstatus code: 200checked: Oct 5, 2026, 8:11 PM UTC
    0 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.
  • Europe
    OperationalEurope, UK
    • Europe
      Operationallatency: 144msstatus code: 200checked: Oct 5, 2026, 8:59 PM UTC
      0 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.
    • UK
      Operationallatency: 92msstatus code: 200checked: Oct 5, 2026, 8:21 PM UTC
      0 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 Pacific
    OperationalAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Operationallatency: 52msstatus code: 200checked: Oct 5, 2026, 8:36 PM UTC
      0 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 Asia
      Operationallatency: 177msstatus code: 200checked: Oct 5, 2026, 8:20 PM UTC
      0 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.
    • Australia
      Operationallatency: 654msstatus code: 200checked: Oct 5, 2026, 8:15 PM UTC
      0 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

DoS Attack, 1h 20mdeclared on their status page2026-07-11
crates.io slowness, 33mdeclared on their status page2026-06-14
Reverse dependency pages unavailable, 70h 13mdeclared on their status page2026-05-23
Degraded performance on crates.io, 1h 5mdeclared on their status page2026-05-20
Git index slow to update, 2h 56mdeclared on their status page2026-04-14
Git index slow to update, 10mdeclared on their status page2026-02-12
Degraded performance on crates.io, 1h 18mdeclared on their status page2025-11-10
Git index slow to update, 3h 22mdeclared on their status page2025-11-01

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 servers

Put this badge in your README

crates.io uptime measured by RealUptimeLive, from this page's own readings.
[![crates.io uptime measured by RealUptime](https://realuptime.io/outages/crates-io/badge.svg?days=30)](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

At or above your target

We measured none of downtime for crates.io over the last 30 days, which is 100% uptime by our reading. A 99.9% target allows 43 minutes over that period.

By our measurement there is no shortfall to claim for this period.

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.

What we check

primaryfunctional: live API
https://index.crates.io/config.json
secondary
https://status.crates.io/api/v2/status.json
RealUptime is not affiliated with crates.io; the name identifies what we measured, and nothing here speaks for crates.io's own team. We send a single web request to crates.io from 10 regions on our own schedule and time the response. We do not see inside crates.io's systems, do not use an account or real transaction, and are not the same signal crates.io's own team has access to. Treat this as one external data point, not a verdict. At least one endpoint we check for crates.io is a real functional API call (marked “functional” above), not just a landing page, so a clean read there is a stronger signal than reachability alone, though it still does not cover every feature of the service. Read the full methodology.