The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
A 429 response means a request was rate-limited, but it does not by itself mean your site is down or overloaded. First identify who sees it: only a bot or integration, all visitors behind a CDN or proxy, or people using the site and WordPress admin. That pattern points to the right next check.
First, identify who is affected
Check the failing URL and when the error began. Then establish whether it appears for a person browsing the site, in WordPress administration, or only when an external service fetches a page. A social-preview or monitoring alert alone does not prove that visitors cannot reach the site.
| Symptom | Likely branch to investigate | First action |
|---|---|---|
| Only social previews, integrations, CRM/API synchronization, or monitoring fail | Automated-traffic rate limit applied at the server level to certain network ranges | Check service status, retry later, and use backoff for repeated requests. |
| Visitors routed through multiple CDN or proxy layers receive 429s | Proxy/CDN topology may make requests appear to come from a small number of addresses | Check whether two proxy/CDN services are active and keep one in use. |
| Regular visitors or WordPress admin are affected | Possible hosting-resource limit or application-level cause, such as a plugin, script, or custom rule | Review resource usage, then investigate recent WordPress or configuration changes. |
These are diagnostic branches, not proof of a cause. HTTP 429 is a rate-limit response; it is not, by itself, evidence that the server is overloaded or that a plugin is responsible.
Recommended Free Tools
If only automated services or link previews fail
Hostinger documents server-level limits for automated traffic from certain network ranges. It names social services such as Facebook, Instagram, and WhatsApp; automation tools such as Zapier, Make, and n8n; CRM systems such as HubSpot and Salesforce; and uptime monitoring as examples that may be affected. Hostinger says ordinary visitors can still access site content during this class of limit. Its support article says these limits apply across customers and are not specific to an individual plan or domain (Hostinger Help Center: server-level rate limits for automated traffic).
- Check the Hostinger status page for current service notices.
- Retry after a short interval instead of repeatedly sending requests immediately after each 429.
- If the integration supports retries, configure exponential backoff: increase the wait between attempts after each rate-limit response, ideally with a maximum delay and attempt limit supported by that integration.
Hostinger says high-activity periods of this kind typically resolve within a few hours; that is an expectation, not a guaranteed recovery time for a particular site or integration. A hosting-plan upgrade is not the targeted fix for this infrastructure-wide limit.
If a CDN or proxy may be involved
Check whether Hostinger CDN and Cloudflare proxying are both active for the domain. Hostinger’s troubleshooting guidance says the domain should not route through both at once. A proxy in front of Hostinger CDN can cause the hosting server to see visitors as requests from only a handful of proxy addresses, changing how per-visitor limits behave and potentially causing a 429 to affect everyone. Review the DNS and proxy arrangement in Hostinger’s CDN configuration guidance and keep one CDN or proxy active.
Capture the failing request if Hostinger CDN is active
- Open the affected page in a browser and open Developer Tools, then select the Network panel.
- Reproduce the error and select the request whose status is 429. Record its exact URL and the time it occurred.
- Inspect the response headers and, if present, copy the value of
x-hcdn-request-id.
Hostinger says a 429 behind its CDN almost always comes from the hosting server or a plugin; the CDN itself returns 429 only as a last-resort protection at attack-level request volumes. Some plugins deliberately return 429 for repeated requests, including security, login-limiting, form-spam, or API-rate-limit functions. The header and request details can help distinguish the affected request, but they do not alone identify the underlying cause.
If regular visitors or WordPress admin are affected
Check whether the hosting account is reaching resource limits
In hPanel, open Websites, select the site, then go to Hosting and Resources Usage. Review CPU and RAM around the time the 429s occur. If usage is reaching the plan’s limits, reduce resource demand; a temporary resource boost may help with a short-lived spike. Consider a plan change only if the usage data shows a persistent limit. These steps address diagnosed resource constraints, not every 429.
Test WordPress components and custom rules
A security plugin, another plugin or script, or an aggressive custom .htaccess rule may contribute to the error. Make one change at a time so you can identify what affects the response, and record the original setting before testing.
- Update WordPress core, themes, and plugins.
- If a plugin is a plausible cause, temporarily deactivate it and test the affected URL. Hostinger suggests testing a security plugin such as Wordfence this way. If the error clears, restore or replace components methodically rather than leaving security protections disabled.
- If no single plugin explains the problem, disable plugins in a controlled sequence and test after each change. If a theme is suspected, temporarily try a default theme.
- Review custom
.htaccessrules, especially rules that block IP ranges or restrict repeated requests. Revert only the rule you have identified as relevant, then retest.
Hostinger’s general troubleshooting guidance also lists request volume, resource limits, attacks, and faulty plugins or themes as possible causes. Treat those as possibilities to check against the symptoms, not a diagnosis based on the status code alone.
Quick Recap
Best Value
Rank #4
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
