Skip to main content
Hostinger

Emergency Server lt-1629 Maintenance

Degraded Lasted 22m · started · Hostinger's page

Level
confirmed
Worst impact
Degraded
Down Index
15of 100

What to do

  • Check whether your product depends on Hostinger. 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 22m it lasted.

    Anything that failed between 2026-03-04 20:29 UTC and 2026-03-04 20:51 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 3

  1. investigating

    We are performing an emergency maintenance on server 1629, located in Lithuania. <ervices could be temporarily inaccessible or might load slower than usual. Our team is currently working to restore normal performance levels. We apologize for any inconvenience caused.

    provider

  2. monitoring

    A fix has been implemented and we are monitoring the results.

    provider

  3. resolved

    This incident has been resolved.

    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-4fc410bcc3

Is Hostinger still down?

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

How long did it last?

22m, from 2026-03-04 20:29 UTC to 2026-03-04 20:51 UTC, by the times Hostinger posted.

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.