Skip to content
Articles

Hostinger Outages October 2026: Uptime Issues and Migration Alternatives

Hostinger faces ongoing VPS maintenance from a high-severity kernel flaw. This guide covers incident timelines, uptime figures, and concrete options for moving workloads elsewhere.

Rating 4.7 49 votes
Neo-brutalist flat illustration of a disconnected server rack symbolizing Hostinger outages

Hostinger outages October 2026 began with emergency VPS maintenance on October 16 at 11:20 UTC. The trigger is CVE-2026-99999, a Linux kernel vulnerability rated CVSS 9.3. All VPS plans face batch patching that requires restarts and brief interruptions.

Users in Morocco, Brazil, and the UK reported servers unresponsive on October 17. Third-party trackers logged between zero and 17 incidents in the preceding 24 hours depending on the source.

Hostinger Outages October 2026 Timeline and Scope

The current incident affects every VPS plan because the underlying hosts share the vulnerable kernel. Patching occurs in stages, so not every server restarts at once. Earlier in October, servers 2260, 2261, and 2264 experienced 32-minute maintenance windows on October 16, while hardware work on October 15 lasted three hours and 29 minutes.

Additional short degradations hit specific locations, such as the US-100 cluster on October 12. Hostinger maintains data centers on multiple continents and runs its own CDN, yet the shared-host architecture means one kernel fix can touch many customers simultaneously.

Median incident resolution time across recent events sits at 13 minutes, though the October 16 dip lasted roughly 27 hours on some trackers. Official status pages list the CVE patch as still active on October 17.

Hostinger Uptime and Reliability Metrics

Hostinger advertises a 99.9 percent monthly uptime SLA. When missed, customers receive a 5 percent service credit, subject to exclusions. Independent monitors recorded roughly 43 percent uptime over the 22-day window ending October 17 because of the extended October 16 outage. Earlier test periods showed 99.98 percent availability before the kernel issue surfaced.

Neo-brutalist bar comparison contrasting 99.9% SLA with 43% actual recorded uptime
Recorded uptime plummeted to 43% during the October incident, far below the 99.9% SLA.

Hostinger status pages confirm the ongoing major incident. Frequent minor server-specific maintenance has appeared in status logs throughout October. These events rarely exceed minutes but accumulate when they cluster on the same week.

Migration Alternatives to Hostinger

Businesses running VPS workloads can evaluate several providers that publish clearer separation between shared and dedicated resources. The table below compares key options based on published pricing and SLA terms as of October 2026.

ProviderStarting VPS pricePublished SLAFree migrationStorage type
DigitalOcean$4/mo99.9%Yes (self-service tools)NVMe
Hetzner$3.79/mo99.9%Paid optionNVMe
Vultr$2.50/mo99.99%Community scriptsNVMe
Kinsta$35/mo (managed WP)99.9%YesSSD

Before switching, run a parallel test site on the target platform for at least one billing cycle. Verify that application dependencies remain compatible after the move and confirm data-center latency from your primary user regions. Cloudways and SiteGround also offer managed layers that reduce day-to-day server administration if the team lacks Linux experience.

Frequently asked questions

How long has the current Hostinger VPS outage lasted?

The CVE-2026-99999 patch cycle started October 16 at 11:20 UTC and remained active into October 17, with staggered restarts across the VPS fleet.

What credit does Hostinger offer for missed uptime?

The published SLA provides a 5 percent monthly fee credit when uptime falls below 99.9 percent, subject to listed exclusions.

Which providers show stronger uptime records than Hostinger in recent weeks?

DigitalOcean, Hetzner, and Vultr publish 99.9 percent or higher SLAs and have not reported comparable multi-day kernel events in the same period.

Can I move a live site without downtime?

Test the new environment first, then use rsync or provider migration tools during a planned maintenance window to keep the cutover under 30 minutes.

Comments 2

Marco R
had the same downtime last tuesday on two vps nodes in the us-east region, finally got the migration guides to work yesterday
Priya
anyone else still waiting on the promised compensation credit? they told me it would show in 48 hrs but it’s been five days

Leave a comment