- Level
- confirmed
- Worst impact
- Degraded
- Components
- User sites
- Down Index
- 23of 100
What to do
Check whether you use Hostinger User sites. 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 2d 17h it lasted.
Anything that failed between 2026-03-14 20:44 UTC and 2026-03-17 14:15 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
- investigating
We are currently investigating an issue affecting websites built with Website Builder and Horizons that use custom domains pointing to the Hostinger CDN. Updating the domain's CNAME to point to connect.hostinger.com may resolve the issue, as a temporary fix. Our teams are actively investigating the root cause. We will provide further updates as soon as more information is available. We apologize for the inconvenience.
provider
- identified
The issue has been identified and a fix is being implemented.
provider
- 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-4da26e3118
Is Hostinger still down?
No, this incident was resolved 2026-03-17 14:15 UTC. For Hostinger's live state, see https://down.guide/hostinger.
How long did it last?
2d 17h, from 2026-03-14 20:44 UTC to 2026-03-17 14:15 UTC, by the times Hostinger posted.
What was affected?
Hostinger named User sites.
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.