![\"\"](\"https:\/\/imagedelivery.net\/LqiWLm-3MGbYHtFuUbcBtA\/wp-content\/uploads\/sites\/55\/2026\/10\/2026-10-29_12-46.png\/public\")
<\/p>When your Hostinger hosting plan reaches its resource limits, the Websites section of Hostinger dashboard shows the warning “Your hosting resource limits have been reached” on the hosting plan’s card.<\/p>
<\/p>
If the plan is only close to its limits, the card shows “Some resources are close to reaching limits” instead, next to the plan’s resource usage percentage. There are four resource limits to watch: CPU, I\/O, RAM and processes, and PHP workers. Reduce usage by optimizing your website code, plugins, and caching, or upgrade your hosting plan if your website has outgrown its resources.<\/p>
![\"\"](\"https:\/\/imagedelivery.net\/LqiWLm-3MGbYHtFuUbcBtA\/wp-content\/uploads\/sites\/55\/2026\/10\/2026-10-29_12-26.png\/public\")
<\/div>The Resources Usage page shows the message “Your plan has reached its resource limits”. To see which resources reached their limits, check the CPU<\/b>, Memory<\/b>, Throughput (I\/O)<\/b>, and PHP Workers<\/b> charts in the Other resources<\/b> section. Each chart shows the plan’s limit as a dashed line and marks the times the limit was reached as Faults<\/b>.<\/p> When you reach the maximum threshold for available CPU<\/b>, your website becomes slower and starts scheduling requests from your visitors instead of serving them instantly. There will be no error messages, but the website will feel sluggish.<\/p> Find out your website’s peak hours and ensure your CPU stays below 80%<\/b> during the busiest times. This will guarantee that all visitors have the best possible experience on your website.<\/p> Usually, high CPU usage is caused by poorly optimized website code. We suggest you:<\/p> If you tried the above suggestions, but the site’s performance is still poor, it indicates that your website has grown<\/b> and needs more resources to keep up with the load. In this case, consider upgrading your hosting plan<\/a>.<\/p> Disk I\/O<\/b> or disk throughput<\/b> is a limit on how fast data can be written\/read. This limit helps measure disk performance. When you reach the maximum threshold for available I\/O, your website will slow down, similar to when the CPU threshold is reached. For this reason, the same above-mentioned solutions<\/b> apply.<\/p> When your hosting plan reaches the limit of processes<\/b> or RAM<\/b>, your website visitors may encounter the 503 Service Unavailable<\/a><\/b> error.<\/p> It is critical<\/b> to ensure you never reach these limits<\/b>. If you reach the limit of processes or RAM 10-20 times<\/b> within one month, it is a very strong indication that your website needs a larger pool of resources to handle the load. We recommend you reduce the number of processes to the minimum<\/b> and, if the issues persist, upgrade your hosting plan<\/b> as soon as possible to ensure the best uptime for your website.<\/p> If your Next.js app is showing high Max Process usage on a web hosting plan, a platform optimization is available that significantly reduces the number of processes spawned at runtime. New deployments apply this automatically. To apply it to an existing app:<\/p> After redeployment, process usage should decrease substantially. Monitor resource usage<\/a> in Hostinger dashboard to confirm.<\/p> PHP workers are processes that handle PHP requests on your server. Each worker can process one request at a time. If your hosting plan has reached its PHP worker limit, users may experience delays or timeouts when accessing your site. Some of the recommendations:<\/p> Keeping CPU, I\/O, RAM, processes, and PHP workers below their limits keeps your website fast and available to visitors.<\/p> NOTES<\/b><\/p> Fixing Hostinger hosting plan limits reached by reducing CPU, I\/O, RAM, process, and PHP worker usage, or upgrade to stop slower website performance.<\/p>\n","protected":false},"author":581,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_content_updated_date":"","include_on_kodee":true,"footnotes":""},"categories":[260],"tags":[],"class_list":["post-1430","post","type-post","status-publish","format-standard","hentry","category-order-usage"],"hreflangs":[{"locale":"en-US","link":"https:\/\/www.hostinger.com\/support\/1583532-what-to-do-if-your-hosting-plan-limits-are-reached-in-hostinger","default":1},{"locale":"es-ES","link":"https:\/\/www.hostinger.com\/es\/support\/1583532-el-uso-del-recursos-muestra-que-se-alcanzaron-los-limites-del-plan-de-hosting","default":0},{"locale":"fr-FR","link":"https:\/\/www.hostinger.com\/fr\/support\/1583532-l-usage-des-ressources-montre-que-les-limites-du-plan-d-hebergement-ont-ete-atteintes","default":0},{"locale":"id-ID","link":"https:\/\/www.hostinger.com\/id\/support\/1583532-paket-hosting-telah-melebihi-batas-penggunaan","default":0},{"locale":"pt-BR","link":"https:\/\/www.hostinger.com\/br\/support\/1583532-o-uso-de-recursos-mostra-que-os-limites-do-plano-de-hospedagem-foram-atingidos-no-hostinger","default":0},{"locale":"uk-UA","link":"https:\/\/www.hostinger.com\/ua\/support\/1583532-\u0449\u043e-\u0440\u043e\u0431\u0438\u0442\u0438-\u044f\u043a\u0449\u043e-\u0432\u0438\u0447\u0435\u0440\u043f\u0430\u043d\u043e-\u043b\u0456\u043c\u0456\u0442-\u0445\u043e\u0441\u0442\u0438","default":0}],"include_on_kodee":true,"_links":{"self":[{"href":"https:\/\/www.hostinger.com\/support\/wp-json\/wp\/v2\/posts\/1430","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.hostinger.com\/support\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.hostinger.com\/support\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.hostinger.com\/support\/wp-json\/wp\/v2\/users\/581"}],"replies":[{"embeddable":true,"href":"https:\/\/www.hostinger.com\/support\/wp-json\/wp\/v2\/comments?post=1430"}],"version-history":[{"count":10,"href":"https:\/\/www.hostinger.com\/support\/wp-json\/wp\/v2\/posts\/1430\/revisions"}],"predecessor-version":[{"id":23924,"href":"https:\/\/www.hostinger.com\/support\/wp-json\/wp\/v2\/posts\/1430\/revisions\/23924"}],"wp:attachment":[{"href":"https:\/\/www.hostinger.com\/support\/wp-json\/wp\/v2\/media?parent=1430"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.hostinger.com\/support\/wp-json\/wp\/v2\/categories?post=1430"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.hostinger.com\/support\/wp-json\/wp\/v2\/tags?post=1430"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}![\"\"](\"https:\/\/imagedelivery.net\/LqiWLm-3MGbYHtFuUbcBtA\/wp-content\/uploads\/sites\/55\/2026\/10\/2026-10-29_12-44.png\/public\")
<\/div>CPU<\/h2>
\n
If your CPU usage is high, check your analytics<\/a> for any loopback requests<\/a> or signs of a potential DDoS<\/a> attack. These issues can also lead to CPU or RAM overages and cause website performance degradation.<\/div>I\/O (Input\/Output)<\/h2>
RAM and Processes<\/h2>
Reducing Max Process count for Next.js apps<\/h3>
\n
PHP Workers<\/h2>
\n
\n