Skip to content

nine production pages quote an Alchemy limit Alchemy retired in August - #2936

Merged
Flotapponnier merged 1 commit into
mainfrom
fix/alchemy-throughput-main
Oct 9, 2026
Merged

Flotapponnier merged 1 commit into
mainfrom
fix/alchemy-throughput-main

Conversation

@Flotapponnier

Copy link
Copy Markdown
Collaborator

nine production pages quote an Alchemy limit Alchemy retired in August

Every keyed RPC page discloses the tier each probe runs on, and the Alchemy
line reads "a Free plan key (30M CU per month, 25 requests per second)". The
30M is right. The 25 rps is a figure Alchemy stopped publishing six weeks ago.

Our own pricing catalogue says so by name, with the commit that did it:
"Throughput RESOLVED to 300 CU/s by wave 2: alchemyplatform/docs commit
3e0a4485, 2026-08-24, 'Update Free tier throughput limit from 500 to 300
CU/s'. www.alchemy.com/pricing still renders the stale '500 CU/s (25 rps)'
and must not be published."

25 rps is that retired 500 CU/s divided by a 20-CU request. Read live today,
alchemy.com/docs/reference/pricing-plans.md gives
"| Base Throughput (CUs/second) | 300 |" for Free, and the marketing page has
caught up as well: it now renders "300 CU/s (15)".

Replaced with what Alchemy publishes, in Alchemy's own unit. Not a converted
request rate: the conversion depends on the method mix, which is the whole
subject of bench 282 next door, where the same 300 CU/s buys 11.5 requests a
second of the dapp mix and 30 of plain eth_blockNumber.

Cherry-picked from dev (#2930), which carries this with the rest of an audit
of benches 282 and 283 against the providers' own documentation. Only the nine
disclosure lines come to main: 9 files, 9 insertions, 9 deletions, nothing
else. The benches that audit corrects are both dev-gated.

I wrote these lines on 2026-10-09 while correcting a different inaccuracy in
the same sentence.

Every keyed RPC page discloses the tier each probe runs on, and the Alchemy
line reads "a Free plan key (30M CU per month, 25 requests per second)". The
30M is right. The 25 rps is a figure Alchemy stopped publishing six weeks ago.

Our own pricing catalogue says so by name, with the commit that did it:
"Throughput RESOLVED to 300 CU/s by wave 2: alchemyplatform/docs commit
3e0a4485, 2026-08-24, 'Update Free tier throughput limit from 500 to 300
CU/s'. www.alchemy.com/pricing still renders the stale '500 CU/s (25 rps)'
and must not be published."

25 rps is that retired 500 CU/s divided by a 20-CU request. Read live today,
alchemy.com/docs/reference/pricing-plans.md gives
"| Base Throughput (CUs/second) | 300 |" for Free, and the marketing page has
caught up as well: it now renders "300 CU/s (15)".

Replaced with what Alchemy publishes, in Alchemy's own unit. Not a converted
request rate: the conversion depends on the method mix, which is the whole
subject of bench 282 next door, where the same 300 CU/s buys 11.5 requests a
second of the dapp mix and 30 of plain eth_blockNumber.

Cherry-picked from dev (#2930), which carries this with the rest of an audit
of benches 282 and 283 against the providers' own documentation. Only the nine
disclosure lines come to main: 9 files, 9 insertions, 9 deletions, nothing
else. The benches that audit corrects are both dev-gated.

I wrote these lines on 2026-10-09 while correcting a different inaccuracy in
the same sentence.
@Flotapponnier
Flotapponnier merged commit 0fe11ef into main Oct 9, 2026
2 checks passed
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