You uploaded a list of redirects, and somewhere around item 21 Cloudflare stopped taking them:
This account has reached the maximum number of items
The documentation says your free plan holds ten thousand. The import stops at twenty. Both of those are true at the same time, and the reason is a migration that was supposed to finish in 2025.
What the documentation says
Bulk Redirects quotas, read off Cloudflare’s availability table on 22 July 2026:
| Plan | URL redirects across lists | Lists | Rules |
|---|---|---|---|
| Free | 10,000 | 5 | 15 |
| Pro | 25,000 | 5 | 15 |
| Business | 50,000 | 5 | 15 |
| Enterprise | 1,000,000 | 25 | 50 |
Ten thousand on the free plan is a real number and it is current. It is simply not the number every account was actually given.
Where twenty comes from
Until February 2025 the free plan allowance was twenty. The changelog entry that raised it is dated 12 February 2025, and it carries a note that turned out to matter more than the new figures:
Limits are updated gradually. Some customers may still see previous limits until the rollout is fully completed in the first half of 2025.
The rollout was expected to finish by the middle of 2025. Accounts were still reporting the old cap in July 2026.
How to tell which quota your account has
Do not go looking for a number in the dashboard. The quota that governs the import is the one provisioned on the account, and the plan documentation is not a reading of it.
The check that works is the one that fails. Add items to a Bulk Redirect List until it
refuses. If item 21 comes back with This account has reached the maximum number of items,
your account is still on the old allowance no matter what the plan page says.
Getting it corrected
This is fixed by asking, and the ask is small. Post on the Cloudflare Community with your domain and the exact error text, or open a ticket if your plan has one.
What that gets you varies. On 8 January 2026 someone hit the cap while importing a list and was told:
There is already a ticket on Cloudflare’s side, in order to fix the underlying issue. There is no ETA. […] I’m afraid you will have to wait, until the underlying issue has been fixed.
On 2 July 2026 someone reported the same error, in the same words, and a Cloudflare engineer replied about forty five minutes later:
I have corrected your Bulk Redirect limits.
Same problem, same year, two outcomes. The difference appears to be whether a staff member picks the thread up rather than anything you can control, so include the error text verbatim and name the domain. That is what the thread that got fixed did.
What to use while you wait
Here is the distinction that goes unexplained in every thread, and it solves part of the problem on its own.
Bulk Redirects live on the account. Cloudflare’s own wording: they “allow you to define a large number of URL redirects at the account level, which can apply across domains in your account”. One list, every zone.
Single Redirects live on the zone. The free plan allowance is ten rules, and it is ten rules per zone, not ten across the account. Six domains with four redirects each fit inside the free plan without touching Bulk Redirects at all.
Two limits worth knowing before you lean on Single Redirects. Wildcards work on every plan, but regular expressions start at Business. And both kinds of rule need the DNS record to be proxied through Cloudflare, which is easy to forget on a domain you park rather than serve.
One more thing to check if these redirects carry advertising click IDs: Bulk Redirects drop the incoming query string unless you say otherwise, and the setting that fixes it has a trap of its own. That is a separate test, and it takes a minute.
Why searching did not help you
The threads that get resolved end like the July one did: a single sentence from an engineer saying the limits have been corrected, and nothing after it. No cause, no scope, no note about who else is affected. Nothing that would rank, and nothing a search engine could show you when you went looking with the error message in hand.
That is why the first page of results for this error is documentation stating a number your account does not have.
When this stops being a support ticket
If you run one domain and a handful of redirects, none of this needs a tool. Ten Single Redirect rules on the free plan cover it, and if you need the bulk list, one forum post gets your quota corrected.
It changes shape when the redirects outlive your attention. Fifty parked domains pointing at one site, several people editing rules, a quota that depends on a support ticket, and no record of which domain was supposed to point where. That is the part 301.st exists for: redirects across many domains, with the history of who changed what. If your answer is still one list in the dashboard, keep the list.