Live  /  Providers  /  Hostinger

Hostinger

hostinger.comNo open incidents

Independent assessment — SquidGrid is not affiliated with Hostinger. Provider-published information is labeled as such; SquidGrid’s own measurements are observations of network paths, not determinations of fault.

SaaS & business software · SquidGrid tracks Hostinger’s own status and independently measures the internet paths that reach it, so you can tell a provider-side problem from a problem on the route to it.

Public — what Hostinger is reporting

Current & recent incidents

Resolved

Emergency Server my-kul-u4s-node1-4 Maintenance

None impact · 2026-09-26 14:12 UTC

Resolved

Emergency Server Agency BR-Node9 Maintenance

None impact · 2026-09-25 17:26 UTC

Resolved

Emergency Server US-900 Maintenance

None impact · 2026-09-25 13:22 UTC

Resolved

.shop DNS Issues

None impact · 2026-09-25 05:57 UTC

Resolved

Emergency Server UK-1476 Maintenance

None impact · 2026-09-24 21:05 UTC

Resolved

Emergency Server US-1685 Maintenance

None impact · 2026-09-23 21:21 UTC

Resolved

Emergency Server us-1683 Maintenance

None impact · 2026-09-23 20:57 UTC

Mirrored from the provider’s own published status. Times in UTC.

Independent path health

A status page tells you what Hostinger has published. SquidGrid independently observes the actual routes from its own worldwide fleet against their own baselines — so when a path moves off its usual range before (or without) a status post, you still see it, and you see where.

Hostinger runs its services on other companies’ networks rather than operating its own, so path measurements roll up to its hosting providers. SquidGrid’s assessment of Hostinger is its published incident record, archived and analyzed above and kept after the provider’s own page forgets it.

SquidGrid is not affiliated with Hostinger.