Rate limit adjustment was approved by Let's Encrypt but the default 50-cert limit is still being enforced on our domain

Approved rate limit adjustment (300–1,000) not taking effect - still hitting (50) limit

We manage a platform where we issue TLS certificates for a large number of subdomains under tailb2240b.ts.net. We submitted a rate limit adjustment request and received an approval email confirming the new limit is 300–1,000. However, we are still getting:

429 rateLimited: too many certificates (50) already issued for "tailb2240b.ts.net"

Based on the LE documentation, the (50) in that error message is the enforced limit, not the count - meaning the default 50 is still active despite the approval.

A few questions:

  1. Is there a way to verify whether a rate limit override is actually deployed for a domain?
  2. Could there be a delay between the approval email and the override taking effect?

We also submitted a separate account-scoped request for 1,000–3,000 which was rejected with the advice to reuse certificates between restarts. We are actively working on that fix, but we still need the approved domain limit to actually be enforced in the interim.


My domain is: tailb2240b.ts.net

I ran this command: N/A - certificates are issued automatically by our platform

It produced this output: 429 rateLimited: too many certificates (50) already issued for "tailb2240b.ts.net"

My web server is: N/A

The operating system my web server runs on is: Linux

My hosting provider, if applicable, is: AWS

I can login to a root shell on my machine: No

I'm using a control panel to manage my site: No

The version of my client is: N/A - managed internally

We submitted two separate requests for this domain - the first was approved (300–1,000) and a second was rejected (1,000–3,000). Could the second submission have interfered with or overridden the first? The domain tailb2240b.ts.net is our tailnet domain assigned to us by Tailscale.

Sorry about this! I see we made a typo on our end while setting up your rate limit adjustment. We received your new adjustment request and expect to process it, and correct our error, this week.