Skip to main content
Hostinger

Emergency Server SG-134 Maintenance

Degraded Lasted 3m · started · Hostinger's page

Level
confirmed
Worst impact
Degraded
Down Index
11of 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 3m it lasted.

    Anything that failed between 2026-06-18 16:00 UTC and 2026-06-18 16:02 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 performing an emergency maintenance on cpanel server 134, located in singapoore. Client websites hosted there 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. resolved

    The incident is fixed.

    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-3200d38195

Is Hostinger still down?

No, this incident was resolved 2026-06-18 16:02 UTC. For Hostinger's live state, see https://down.guide/hostinger.

How long did it last?

3m, from 2026-06-18 16:00 UTC to 2026-06-18 16:02 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.