How to troubleshoot HTTP Error 429 at Hostinger

Identify HTTP Error 429 or rate limits on your website due to Hostinger infrastructure protections or resource usage

Updated 3 weeks ago

HTTP Error 429 (Too Many Requests) is a rate-limiting response indicating that a server has received more requests than it is configured to handle within a specific timeframe, often caused by Hostinger infrastructure protections or website traffic spikes.

Step 1 – Identify the traffic type

Hostinger has implemented automated server-level rate limits for automated traffic from specific network ranges, including Meta, AWS, and Microsoft.

  • If you experience issues with social media link previews (Facebook, Instagram, WhatsApp) or automation tools (Zapier, Make, n8n), the error is likely due to these infrastructure protections.
  • For detailed information on these specific measures, refer to the guide on server-level rate limits.

Step 2 – Check for a double-CDN setup

If your domain uses Hostinger CDN and Cloudflare at the same time, Hostinger applies a rate limit to that traffic.

Confirm your domain is not routing through both CDNs at once. See Hostinger CDN vs Cloudflare guide for details on identifying and fixing this or see Hostinger CDN: 429 Too Many Requests errors if your domain only uses Hostinger CDN.

Step 3 – Check Hostinger hosting plan limits

If the error affects regular visitors, it may be related to your website performance.

  1. Go to the Resources Usage section on Hostinger dashboard.
  2. Review your CPU and RAM usage to determine if your website is reaching the limits of your current hosting plan.
    1. If needed, consider optimizing your website for a more efficient resource usage.
    2. For a temporary resource increase, you can boost your hosting plan.
    3. If you are consistently hitting the resource limits, consider upgrading your hosting.

Step 4 – Audit WordPress plugins and scripts

High-frequency or resource-intensive scripts and security configurations in the WordPress Admin area can trigger 429 errors.

  1. Temporarily deactivate security plugins like Wordfence to verify if the rate limit clears.
  2. Make sure your WordPress core, themes, and plugins are up to date.
  3. Review your .htaccess file for custom rules that may be blocking IP ranges too aggressively.

By acknowledging Hostinger’s automated protections and auditing your website’s resource usage, you can quickly restore full connectivity for both your users and third-party integrations.

Additional resources