Skip to content

rate limits: update for staging, and errant value in production #1881

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Apr 1, 2025
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions content/en/docs/rate-limits.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@
title: Rate Limits
slug: rate-limits
date: 2018-01-04
lastmod: 2024-12-17
lastmod: 2025-04-01
show_lastmod: true
---

Expand Down Expand Up @@ -268,7 +268,7 @@ being overwhelmed by clients that make too many requests at once.
| /acme/revoke-cert | 10 | 100 |
| /acme/renewal-info | 1000 | 100 |
| /acme/* | 250 | 125 |
| /directory | 40 | N/A |
| /directory | 40 | 40 |

Subscribers who exceed these limits will receive a `503 Service Unavailable`
HTTP response code. The response will include a `Retry-After` header.
Expand Down
30 changes: 22 additions & 8 deletions content/en/docs/staging-environment.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@
title: Staging Environment
slug: staging-environment
date: 2018-01-05
lastmod: 2024-06-11
lastmod: 2025-04-01
show_lastmod: 1
---

Expand All @@ -17,13 +17,27 @@ If you're using Certbot, you can use our staging environment with the `--test-ce

# Rate Limits

The staging environment uses the same rate limits as [described for the production environment](/docs/rate-limits) with the following exceptions:

* The **Certificates per Registered Domain** limit is 30,000 per week.
* The **Duplicate Certificate** limit is 30,000 per week.
* The **Failed Validations** limit is 60 per hour.
* The **Accounts per IP Address** limit is 50 accounts per 3 hour period per IP.
* For ACME v2, the **New Orders** limit is 1,500 new orders per 3 hour period per account.
The staging environment uses the same rate limits as [described for the production environment](/docs/rate-limits) but with different values:

* The **[New Registrations per IP Address](/docs/rate-limits/#new-registrations-per-ip-address)** limit is 50 per 3 hours.
* The **[New Registrations per IPv6 Range](/docs/rate-limits/#new-registrations-per-ipv6-range)** limit is 500 per 3 hours (the same as production).
* The **[New Orders per Account](/docs/rate-limits/#new-orders-per-account)** limit is 1500 per 3 hours.
* The **[New Certificates per Registered Domain](/docs/rate-limits/#new-certificates-per-registered-domain)** limit is 30000 per second.
* The **[New Certificates per Exact Set of Hostnames](/docs/rate-limits/#new-certificates-per-exact-set-of-hostnames)** limit is 30000 per week.
* The **[Authorization Failures per Hostname per Account](/docs/rate-limits/#authorization-failures-per-hostname-per-account)** limit is 200 per hour.
* The **[Consecutive Authorization Failures per Hostname per Account](/docs/rate-limits/#consecutive-authorization-failures-per-hostname-per-account)** limit is 3600 per 6 hours.

The [Overall Requests Limits](/docs/rate-limits/#overall-requests-limit) are:

| Endpoint | Requests per IP (per second) | Burst Capacity |
|--------------------|------------------------------|----------------|
| /acme/new-nonce | 20 | 10 |
| /acme/new-account | 5 | 15 |
| /acme/new-order | 20 | 40 |
| /acme/revoke-cert | 10 | 100 |
| /acme/renewal-info | 1000 | 100 |
| /acme/* | 20 | 20 |
| /directory | 40 | 40 |

# Staging Certificate Hierarchy

Expand Down
Loading