Skip to content

an endpoint that answers 1 % of the time was published as absent - #2780

Merged
Flotapponnier merged 1 commit into
mainfrom
cherry/publish-silent-endpoints
Oct 2, 2026
Merged

Flotapponnier merged 1 commit into
mainfrom
cherry/publish-silent-endpoints

Conversation

@Flotapponnier

Copy link
Copy Markdown
Collaborator

Cherry-pick from dev (#2779). This commit only.

Thirdweb is declared on 31 chain RPC benches and ranked on none: 0.3 % to 1.5 % success across 29 chains from our probes, 25 of 25 from a consumer connection. It serves browsers and refuses our probe hosts.

The exclusion was right. The silence was not: below the 5 % display floor a provider left the table, {{count}} and the headline, so a page naming one endpoint read as a chain that has one endpoint. iotex-rpc claimed "the only free public IoTeX RPC endpoint measured" where three were measured.

Adds belowDisplayFloor() (the exact complement of displayResults, with a partition test), a derived "Declared, but not answering our probes" block carrying each URL and its real success rate, and a headline that says "answering our probes" instead of "measured". Nothing authored, so an endpoint that recovers rejoins on its own.

Verified after the pick: tsc clean, 439 tests pass.

Thirdweb is declared on 31 chain RPC benches and ranked on none of them.
It answers 0.3 % to 1.5 % of our probes across 29 chains while returning
25 of 25 calls from a consumer connection: it serves browsers and refuses
our probe hosts.

The exclusion was right. A median drawn from a handful of replies is not
a measurement, and the 50 % ranking floor and the 5 % display floor both
exist for that. What was wrong is that the reader never learned it. Below
5 % a provider left the table, left {{count}}, and left the headline, so
a page naming one endpoint read as a chain that has one endpoint.

That is the flattering half of the fact. Our readers deploy on servers
and would meet the same wall, so the refusal is the most useful thing we
know about that endpoint.

Three changes, all derived from the measurement rather than authored, so
an endpoint that recovers rejoins the table on its own:

- belowDisplayFloor() in provider-filters, the exact complement of
  displayResults over the live set, with a test that the two partition it
  so nothing can fall into neither again.
- A "Declared, but not answering our probes" block under the endpoints
  list, naming each one with its URL and its real success rate, and
  saying that a provider can serve a browser and refuse a datacenter.
  This is separate from the authored excludedProviders block, which is
  for a provider we chose not to probe.
- The one-endpoint headline said "the only free public IoTeX RPC endpoint
  measured" on a chain where three were measured and two answered under
  2 % of the time. It now says "the only one of the N endpoints answering
  our probes", which is what the number behind it actually holds.

The section used to return null below two usable endpoints, so the pages
that needed the explanation most were the ones bailing out before it. It
renders when a silent endpoint exists, and still returns null when there
is nothing to paste at all.
@Flotapponnier
Flotapponnier merged commit 4210a39 into main Oct 2, 2026
2 checks passed
@Flotapponnier
Flotapponnier deleted the cherry/publish-silent-endpoints branch October 2, 2026 12:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant