Fix a 429 Too Many Requests response from an RSS feed in Feedzy
A 429 Too Many Requests response means the source has rate-limited how often your site can request that feed. A custom User Agent alone will not fix this.
The feed still opens in your browser because one manual visit stays well inside the source's limit.
If you have not changed your User Agent yet, start with How to change user agent in Feedzy, then apply the request-frequency checks below.
1) Reduce how often Feedzy requests the feed
Feedzy caches each feed and only requests it again when the cache expires.
- Feedzy block and Feedzy Loop block: open Additional options and change Feed Caching Time.
- Elementor widget and classic widget: change For how long we will cache the feed results.
- Shortcode: set
refresh, for examplerefresh="1_days".
The default is 12 hours. If the source is rate-limiting, confirm it was not lowered, then raise it to 1 day or longer when possible.
For custom intervals, see How to change the caching time interval in Feedzy widget and How to change cache lifetime for a specific feed.
💡 Tip: Each block, widget, and shortcode has its own cache. Multiple displays of the same source can multiply requests.
2) Confirm what status code the source returned
Go to Feedzy > Settings > General, set Logging Level to Error (or higher), retest, then check Feedzy > Settings > Logs.
Use the feed's canonical XML URL directly. Tracking/redirect links can add extra requests and hit limits faster.
3) If you own or administer the source site
When the feed is published from a site you control, the block can be lifted at the source. Ask your host or CDN provider to check the application, edge, bot-protection, rate-limit, and firewall logs for the feed's path, and give them:
- The times the requests failed.
- The canonical feed URL.
- The IP address of the server making the requests, if you know it.
- Any request identifiers from the failed responses, such as a Cloudflare Ray ID.
You can then ask them to allow the feed path or exempt it from the rate-limit rule.
4) If 429 escalates into 403
Once a source has rate-limited your site repeatedly, its bot-protection or firewall layer can start refusing the requests outright. The response then changes to a persistent 403 Forbidden that no longer recovers on its own.
If this happens, continue with Fix a 403 Forbidden response from an RSS feed in Feedzy.