Is Hostinger down?

Our provider, Oxylabs, is performing maintenance on their side, which has made the web scraping and web fetch tools temporarily unavailable. Workflows in OpenClaw, Hermes, and n8n that use these tools may fail until service is restored. All other services and tools are operating normally, and no action is needed on your part — affected workflows will resume working once the maintenance is complete. Expected resolution: end of day, October 29. We apologize for the inconvenience and will post an update here as soon as the tools are back.

Our team is aware about the released Node.js version 24.22.1, which fixes 7 security vulnerabilities, several of them high severity. We will be rolling this patched Node.js runtime out to our shared hosting platform so your applications receive these fixes. No actions are required from client side. We'll provide further updates soon. Thank you for your patience.

We're rolling out the Node.js security update (versions 24.22.1 and 22.23.4) across our hosting products: - Agency Hosting: We have deployed a patched version. Your websites are secured, no action is needed from customer's side. - Hostinger AI Builder: the update is ready and being rolled out. Websites will move to the updated version automatically. In the meantime, no action is needed from the customer's side. - Web Hosting and Cloud Hosting: the updated Node.js packages from our operating system vendor are expected within the next few hours, and we'll install them as soon as they're available. Meanwhile, we're deploying additional security rules on our servers to reduce exposure. No action needed yet. VPS clients manage Node.js themselves and can follow our guide: https://www.hostinger.com/blog/securing-nodejs/

We have completed the rollout for the Node.js security updates (24.22.1 and 22.23.4) across managed hosting products. No actions are necessary for customers running Agency Hosting, AI Builder, Web Hosting and Cloud Hosting Node.js applications. VPS clients manage Node.js themselves and can follow our guide: https://www.hostinger.com/blog/securing-nodejs/

Our team is aware about ongoing PHP security vulnerabilities CVE-2026-109618 and CVE-2026-109619 (php2shell). After conducting tests in our hosting environments, we have confirmed out platform is not vulnerable php2shell. We additionally implemented an extra layer of protection to ensure attack vectors cannot be accessed. Although our environments are not affected, we will be rolling out patched PHP versions across our infrastructure. No actions are required from client side. We'll provide further updates soon. Thank you for your patience.

We have completed update work in our Agency Hosting infrastructure and continue working to finish PHP upgrades to remaining managed hosting servers. We'll provide further updates on progress. Thank you for your patience.

All cPanel servers have been updated to the latest cPanel build, which includes the PHP fix (build 138.18), and the latest Alt-PHP version.

PHP upgrades are now complete across all managed hosting servers. Following the PHP security update, some websites show PHP version 8.5.11 rather than 8.5.12. This is expected. The security fix has been added to the PHP version your website already uses, so the version number does not change. To confirm the fix is applied, go to hPanel → Websites → Dashboard and open PHP Info from the sidebar. If the Build Date is October 21, 2026 or later, your website has the fix. No action is needed from clients on our Web Hosting, Agency Hosting, or cPanel Hosting plans. VPS clients manage PHP themselves and can follow our guide: https://www.hostinger.com/blog/protecting-php2shell/

On October 23, 2026, the PHP project announced a new vulnerability (CVE-2026-115560). It affects only websites with an unusual PHP setup. PHP will include the fix in its next regular release. Websites on our Web Hosting, Agency Hosting, and cPanel Hosting plans are already protected by the mitigation applied on October 21. No action is needed. We will install PHP's fix once it is released. VPS clients manage PHP themselves. If your VPS runs PHP, set session.upload_progress.enabled=0 in php.ini and restart PHP. If you already did this on October 21, you don't need to do anything else. Guide: https://www.hostinger.com/blog/protecting-php2shell/