429 on API and UI

We are experiencing getting 429 responses when using the rest API to configure routes which we have been trying to troubleshoot (see general-helpGetting 429 on REST API but missing retry-after in body ). Not being able to update the routes has caused issues for our operations, so as a workaround we have tried using the UI to configure routes, but both when we configure CIDR or Hostname routes we also get 429 responses, so we currently have no way of creating, removing or editing routes.
Our API uses an Account based API token.

LazarusOP•11/25/25, 11:54 AM

We have tried creating routes with multiple different users with the same results

LazarusOP•11/28/25, 9:05 AM

For reference it turned out that we had hit the limit of amounts of tunnels we could configure for our account, https://developers.cloudflare.com/cloudflare-one/account-limits/#cloudflare-tunnel.
The 429 response led us to believe it was a throttling, so in our opinion another reponse, such as 409, could have been more appropriate

Cloudflare Docs

Account limits

This page lists the default account limits for rules, applications, fields, and other features. These limits may be increased on Enterprise accounts. To request a limit increase, contact your account team.

429 on API and UI

Similar Threads

Similar Threads

Similar Threads