Skip to content

Outage tracker / crates.io

Is crates.io down?

I'm having a problem

Vendor reports no incidentWhat crates.io reports

crates.io reports no incident on its status page.

As of the last successful poll, 2026-11-05 14:59 UTC.

crates.io's status page

Our regional reading

This is our own reading from outside, shown beside the vendor's statement. It is not counted as a separate outage.

Partially degradedchecked 5 minutes ago

crates.io is answering our probes, but its API is running at least 7.2x its 7-day median from South America. Everything else we check answered at its usual speed.

As of Nov 5, 2026, 3:00 PM UTC, RealUptime's checks of crates.io passed in all 10 regions that returned a reading.

Front-door and live API checks

our check readinglive · checked Nov 5, 2026, 3:00 PM UTC
US-East726 msChecks passing
US-West387 msChecks passing
Europe749 msChecks passing
Asia-Pacific1545 msChecks passing
US-Central105 msChecks passing
Canada295 msChecks passing
UK145 msChecks passing
Southeast Asia332 msChecks passing
Australia1357 msChecks passing
South America1104 msDegraded
their status pagetheir claim, not our reading

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

from crates.io's own status page, checked Nov 5, 2026, 2:27 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
1.5sp95 · latest
2s1s0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 287ms2026-10-08 UTC: p95 297ms2026-10-09 UTC: p95 337ms2026-10-10 UTC: p95 263ms2026-10-11 UTC: p95 249ms2026-10-12 UTC: p95 251ms2026-10-13 UTC: p95 427ms2026-10-14 UTC: p95 446ms2026-10-15 UTC: p95 477ms2026-10-16 UTC: p95 634ms2026-10-17 UTC: p95 672ms2026-10-18 UTC: p95 1.1s2026-10-19 UTC: p95 1.1s2026-10-20 UTC: p95 1.4s2026-10-21 UTC: p95 1.1s2026-10-22 UTC: p95 442ms2026-10-23 UTC: p95 1.1s2026-10-24 UTC: p95 1.1s2026-10-25 UTC: p95 1.0s2026-10-26 UTC: p95 1.2s2026-10-27 UTC: p95 534ms2026-10-28 UTC: p95 492ms2026-10-29 UTC: p95 687ms2026-10-30 UTC: p95 348ms2026-10-31 UTC: p95 352ms2026-11-01 UTC: p95 398ms2026-11-02 UTC: p95 1.2s2026-11-03 UTC: p95 1.5s2026-11-04 UTC: p95 1.7s2026-11-05 UTC: p95 1.5s
Oct 7Oct 21Nov 5
US-West
2.0sp95 · latest
2.5s1.3s0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 294ms2026-10-08 UTC: p95 396ms2026-10-09 UTC: p95 320ms2026-10-10 UTC: p95 326ms2026-10-11 UTC: p95 298ms2026-10-12 UTC: p95 298ms2026-10-13 UTC: p95 317ms2026-10-14 UTC: p95 275ms2026-10-15 UTC: p95 301ms2026-10-16 UTC: p95 367ms2026-10-17 UTC: p95 336ms2026-10-18 UTC: p95 322ms2026-10-19 UTC: p95 339ms2026-10-20 UTC: p95 340ms2026-10-21 UTC: p95 426ms2026-10-22 UTC: p95 392ms2026-10-23 UTC: p95 289ms2026-10-24 UTC: p95 353ms2026-10-25 UTC: p95 308ms2026-10-26 UTC: p95 385ms2026-10-27 UTC: p95 335ms2026-10-28 UTC: p95 331ms2026-10-29 UTC: p95 436ms2026-10-30 UTC: p95 484ms2026-10-31 UTC: p95 895ms2026-11-01 UTC: p95 745ms2026-11-02 UTC: p95 1.7s2026-11-03 UTC: p95 2.4s2026-11-04 UTC: p95 2.2s2026-11-05 UTC: p95 2.0s
Oct 7Oct 21Nov 5
Europe
985msp95 · latest
2s1s0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 388ms2026-10-08 UTC: p95 263ms2026-10-09 UTC: p95 341ms2026-10-10 UTC: p95 448ms2026-10-11 UTC: p95 496ms2026-10-12 UTC: p95 460ms2026-10-13 UTC: p95 492ms2026-10-14 UTC: p95 490ms2026-10-15 UTC: p95 540ms2026-10-16 UTC: p95 509ms2026-10-17 UTC: p95 518ms2026-10-18 UTC: p95 545ms2026-10-19 UTC: p95 590ms2026-10-20 UTC: p95 613ms2026-10-21 UTC: p95 380ms2026-10-22 UTC: p95 559ms2026-10-23 UTC: p95 620ms2026-10-24 UTC: p95 478ms2026-10-25 UTC: p95 464ms2026-10-26 UTC: p95 422ms2026-10-27 UTC: p95 334ms2026-10-28 UTC: p95 837ms2026-10-29 UTC: p95 380ms2026-10-30 UTC: p95 454ms2026-10-31 UTC: p95 555ms2026-11-01 UTC: p95 595ms2026-11-02 UTC: p95 1.5s2026-11-03 UTC: p95 1.4s2026-11-04 UTC: p95 1.7s2026-11-05 UTC: p95 985ms
Oct 7Oct 21Nov 5
Asia-Pacific
2.3sp95 · latest
10s5s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 10s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 502ms2026-10-08 UTC: p95 498ms2026-10-09 UTC: p95 595ms2026-10-10 UTC: p95 579ms2026-10-11 UTC: p95 430ms2026-10-12 UTC: p95 524ms2026-10-13 UTC: p95 479ms2026-10-14 UTC: p95 603ms2026-10-15 UTC: p95 505ms2026-10-16 UTC: p95 664ms2026-10-17 UTC: p95 582ms2026-10-18 UTC: p95 448ms2026-10-19 UTC: p95 455ms2026-10-20 UTC: p95 434ms2026-10-21 UTC: p95 1.2s2026-10-22 UTC: p95 1.3s2026-10-23 UTC: p95 1.2s2026-10-24 UTC: p95 724ms2026-10-25 UTC: p95 501ms2026-10-26 UTC: p95 777ms2026-10-27 UTC: p95 5.6s2026-10-28 UTC: p95 1.1s2026-10-29 UTC: p95 876ms2026-10-30 UTC: p95 1.5s2026-10-31 UTC: p95 1.0s2026-11-01 UTC: p95 1.3s2026-11-02 UTC: p95 1.8s2026-11-03 UTC: p95 2.4s2026-11-04 UTC: p95 2.2s2026-11-05 UTC: p95 2.3s
Oct 7Oct 21Nov 5
US-Central
652msp95 · latest
2s1s0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 266ms2026-10-08 UTC: p95 251ms2026-10-09 UTC: p95 210ms2026-10-10 UTC: p95 335ms2026-10-11 UTC: p95 423ms2026-10-12 UTC: p95 239ms2026-10-13 UTC: p95 310ms2026-10-14 UTC: p95 337ms2026-10-15 UTC: p95 310ms2026-10-16 UTC: p95 398ms2026-10-17 UTC: p95 291ms2026-10-18 UTC: p95 332ms2026-10-19 UTC: p95 330ms2026-10-20 UTC: p95 316ms2026-10-21 UTC: p95 531ms2026-10-22 UTC: p95 525ms2026-10-23 UTC: p95 423ms2026-10-24 UTC: p95 416ms2026-10-25 UTC: p95 433ms2026-10-26 UTC: p95 462ms2026-10-27 UTC: p95 437ms2026-10-28 UTC: p95 1.0s2026-10-29 UTC: p95 318ms2026-10-30 UTC: p95 231ms2026-10-31 UTC: p95 826ms2026-11-01 UTC: p95 604ms2026-11-02 UTC: p95 301ms2026-11-03 UTC: p95 230ms2026-11-04 UTC: p95 533ms2026-11-05 UTC: p95 652ms
Oct 7Oct 21Nov 5
Canada
848msp95 · latest
2s1s0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 321ms2026-10-08 UTC: p95 252ms2026-10-09 UTC: p95 439ms2026-10-10 UTC: p95 327ms2026-10-11 UTC: p95 270ms2026-10-12 UTC: p95 311ms2026-10-13 UTC: p95 286ms2026-10-14 UTC: p95 323ms2026-10-15 UTC: p95 351ms2026-10-16 UTC: p95 427ms2026-10-17 UTC: p95 263ms2026-10-18 UTC: p95 276ms2026-10-19 UTC: p95 297ms2026-10-20 UTC: p95 427ms2026-10-21 UTC: p95 483ms2026-10-22 UTC: p95 461ms2026-10-23 UTC: p95 452ms2026-10-24 UTC: p95 284ms2026-10-25 UTC: p95 342ms2026-10-26 UTC: p95 1.1s2026-10-27 UTC: p95 793ms2026-10-28 UTC: p95 828ms2026-10-29 UTC: p95 925ms2026-10-30 UTC: p95 701ms2026-10-31 UTC: p95 306ms2026-11-01 UTC: p95 770ms2026-11-02 UTC: p95 439ms2026-11-03 UTC: p95 655ms2026-11-04 UTC: p95 1.2s2026-11-05 UTC: p95 848ms
Oct 7Oct 21Nov 5
UK
803msp95 · latest
2s1s0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 138ms2026-10-08 UTC: p95 160ms2026-10-09 UTC: p95 174ms2026-10-10 UTC: p95 230ms2026-10-11 UTC: p95 174ms2026-10-12 UTC: p95 178ms2026-10-13 UTC: p95 226ms2026-10-14 UTC: p95 193ms2026-10-15 UTC: p95 161ms2026-10-16 UTC: p95 275ms2026-10-17 UTC: p95 309ms2026-10-18 UTC: p95 270ms2026-10-19 UTC: p95 228ms2026-10-20 UTC: p95 147ms2026-10-21 UTC: p95 242ms2026-10-22 UTC: p95 379ms2026-10-23 UTC: p95 335ms2026-10-24 UTC: p95 156ms2026-10-25 UTC: p95 353ms2026-10-26 UTC: p95 292ms2026-10-27 UTC: p95 293ms2026-10-28 UTC: p95 642ms2026-10-29 UTC: p95 1.2s2026-10-30 UTC: p95 794ms2026-10-31 UTC: p95 149ms2026-11-01 UTC: p95 278ms2026-11-02 UTC: p95 582ms2026-11-03 UTC: p95 543ms2026-11-04 UTC: p95 381ms2026-11-05 UTC: p95 803ms
Oct 7Oct 21Nov 5
Southeast Asia
2.1sp95 · latest
2.5s1.3s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 431ms2026-10-08 UTC: p95 398ms2026-10-09 UTC: p95 405ms2026-10-10 UTC: p95 329ms2026-10-11 UTC: p95 275ms2026-10-12 UTC: p95 337ms2026-10-13 UTC: p95 328ms2026-10-14 UTC: p95 386ms2026-10-15 UTC: p95 394ms2026-10-16 UTC: p95 334ms2026-10-17 UTC: p95 322ms2026-10-18 UTC: p95 1.0s2026-10-19 UTC: p95 1.4s2026-10-20 UTC: p95 975ms2026-10-21 UTC: p95 427ms2026-10-22 UTC: p95 346ms2026-10-23 UTC: p95 365ms2026-10-24 UTC: p95 338ms2026-10-25 UTC: p95 363ms2026-10-26 UTC: p95 506ms2026-10-27 UTC: p95 408ms2026-10-28 UTC: p95 367ms2026-10-29 UTC: p95 1.4s2026-10-30 UTC: p95 1.1s2026-10-31 UTC: p95 1.7s2026-11-01 UTC: p95 2.0s2026-11-02 UTC: p95 1.4s2026-11-03 UTC: p95 1.3s2026-11-04 UTC: p95 438ms2026-11-05 UTC: p95 2.1s
Oct 7Oct 21Nov 5
Australia
1.5sp95 · latest
2.5s1.3s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 542ms2026-10-08 UTC: p95 309ms2026-10-09 UTC: p95 561ms2026-10-10 UTC: p95 445ms2026-10-11 UTC: p95 502ms2026-10-12 UTC: p95 368ms2026-10-13 UTC: p95 650ms2026-10-14 UTC: p95 416ms2026-10-15 UTC: p95 418ms2026-10-16 UTC: p95 509ms2026-10-17 UTC: p95 532ms2026-10-18 UTC: p95 696ms2026-10-19 UTC: p95 823ms2026-10-20 UTC: p95 638ms2026-10-21 UTC: p95 561ms2026-10-22 UTC: p95 657ms2026-10-23 UTC: p95 568ms2026-10-24 UTC: p95 559ms2026-10-25 UTC: p95 599ms2026-10-26 UTC: p95 528ms2026-10-27 UTC: p95 429ms2026-10-28 UTC: p95 859ms2026-10-29 UTC: p95 1.7s2026-10-30 UTC: p95 1.6s2026-10-31 UTC: p95 890ms2026-11-01 UTC: p95 1.6s2026-11-02 UTC: p95 1.6s2026-11-03 UTC: p95 2.2s2026-11-04 UTC: p95 2.0s2026-11-05 UTC: p95 1.5s
Oct 7Oct 21Nov 5
South America
1.8sp95 · latest
5s2.5s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 525ms2026-10-08 UTC: p95 249ms2026-10-09 UTC: p95 323ms2026-10-10 UTC: p95 261ms2026-10-11 UTC: p95 231ms2026-10-12 UTC: p95 254ms2026-10-13 UTC: p95 435ms2026-10-14 UTC: p95 711ms2026-10-15 UTC: p95 384ms2026-10-16 UTC: p95 426ms2026-10-17 UTC: p95 547ms2026-10-18 UTC: p95 544ms2026-10-19 UTC: p95 370ms2026-10-20 UTC: p95 319ms2026-10-21 UTC: p95 287ms2026-10-22 UTC: p95 431ms2026-10-23 UTC: p95 3.7s2026-10-24 UTC: p95 489ms2026-10-25 UTC: p95 509ms2026-10-26 UTC: p95 446ms2026-10-27 UTC: p95 511ms2026-10-28 UTC: p95 326ms2026-10-29 UTC: p95 691ms2026-10-30 UTC: p95 1.6s2026-10-31 UTC: p95 320ms2026-11-01 UTC: p95 2.1s2026-11-02 UTC: p95 644ms2026-11-03 UTC: p95 529ms2026-11-04 UTC: p95 1.6s2026-11-05 UTC: p95 1.8s
Oct 7Oct 21Nov 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 that a second endpoint answered) rather than a normal pass or failure. That tells us about our own probe's reception, not about crates.io's health, so we publish no verdict for those readings rather than guessing in either direction. Read how we tell the difference.

Check your own site while you wait on crates.io

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: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Awaiting data
  • APIprimaryUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Degraded Answering, but 7.2x slower than its 7-day median.

Email me when crates.io reports an incident on its status page, and again when it reports it resolved.

Get an email when crates.io reports an incident

Email me when crates.io reports an incident on its status page, and again when it reports it resolved. No account, no card.

Delivery channel

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

This is crates.io's own statement from its status page, with our regional reading beside it.

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 our checks show, and what people reported

  • North America
    Checks passingUS-East, US-West, US-Central, Canada
    • US-East
      Checks passinglatency: 726msstatus code: 200checked: Nov 5, 2026, 2:35 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
      Checks passinglatency: 387msstatus code: 200checked: Nov 5, 2026, 2:37 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
      Checks passinglatency: 105msstatus code: 200checked: Nov 5, 2026, 2:54 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
      Checks passinglatency: 295msstatus code: 200checked: Nov 5, 2026, 2:57 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
    Degradedlatency: 1104msstatus code: 200checked: Nov 5, 2026, 2:54 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
    Checks passingEurope, UK
    • Europe
      Checks passinglatency: 749msstatus code: 200checked: Nov 5, 2026, 2:35 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
      Checks passinglatency: 145msstatus code: 200checked: Nov 5, 2026, 2:56 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
    Checks passingAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Checks passinglatency: 1545msstatus code: 200checked: Nov 5, 2026, 1:54 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
      Checks passinglatency: 332msstatus code: 200checked: Nov 5, 2026, 2:56 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
      Checks passinglatency: 1357msstatus code: 200checked: Nov 5, 2026, 3:00 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 probe events

Git index updates delayed, 2h 18mdeclared on their status page2026-11-04
Background job processing stalled, 1h 10mdeclared on their status page2026-10-26
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

check 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 check readings and crates.io's own claim at the time, side by side.

Full check history for crates.io: 90 days of check results by region, month-by-month uptime by our checks, and every probe event 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

Run a service people depend on? Give them a status page on your own domain, checked every minute from six regions, for $9 a month. Get Starter

Put this badge in your README

crates.io uptime by RealUptime's checksLive, from this page's own readings.
[![crates.io uptime by RealUptime's checks](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 by RealUptime's checks" height="20"></a>

Share of checks passed over 30 days; the window is printed on it. If our readings go stale it says stale, and if we have no readings it says so and shows no color. How the badge works.

To cite this page: RealUptime, "Is crates.io down?", https://realuptime.io/outages/crates-io. The readings change with every check, so give the date you read them.

What we check

primaryfunctional: live API
https://index.crates.io/config.json
secondary
https://status.crates.io/api/v2/status.json

What our check can and cannot see

A pass means a public route of the service's API answered our request normally. We do not check what it returned, so it does not show that the data is right, that sign-in works or that the rest of the product works.

Host checked: index.crates.io

RealUptime is not affiliated with crates.io; the name identifies what we checked, 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 passing check there says an API answered, though it still does not show that every feature of the service works for you. Read the full methodology.