Skip to main content
Hostinger

Investigating

Degraded Lasted 27m · started · Hostinger's page

Level
confirmed
Worst impact
Degraded
Regions
in
Down Index
20of 100

What to do

  • Check whether you use Hostinger in in. Check your stack

    Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.
  • Confirm your retries, queues and scheduled jobs caught up after the 27m it lasted.

    Anything that failed between 2026-04-23 23:00 UTC and 2026-04-23 23:27 UTC may need a replay.
  • Subscribe to Hostinger's feed to hear about the next one first. RSS feed

    https://down.guide/feed?provider=hostinger works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Hostinger 2

  1. investigating

    We are investigating a incident in the server 1979 located in india, services could not work properly or load slower than usual

    provider

  2. resolved

    We think the impact from the issue is over.

    provider

Reports count in aggregate; nothing about you is shown.

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Questions about DWN-e82d6b77fb

Is Hostinger still down?

No, this incident was resolved 2026-04-23 23:27 UTC. For Hostinger's live state, see https://down.guide/hostinger.

How long did it last?

27m, from 2026-04-23 23:00 UTC to 2026-04-23 23:27 UTC, by the times Hostinger posted.

What was affected?

Hostinger named in in.

What caused it?

Hostinger hasn't published a root cause. If it does, it shows here.

Where does this come from?

Hostinger's official status page, https://statuspage.hostinger.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.