- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 23of 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 19h 4m it lasted.
Anything that failed between 2026-03-25 16:22 UTC and 2026-03-26 11:25 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 Horizons that use custom domains pointing to the Hostinger CDN. Customers with custom domains (CNAME) connected via the Hostinger CDN are affected by this. Our teams are actively investigating the root. We will provide further updates as soon as more information is available. We apologize for the inconvenience.
provider
- investigating
We are continuing to investigate this issue.
provider
- resolved
This incident has been largely resolved. The team is working on further mitigation to prevent such incidents in the future.
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-6c983cf6ad
Is Hostinger still down?
No, this incident was resolved 2026-03-26 11:25 UTC. For Hostinger's live state, see https://down.guide/hostinger.
How long did it last?
19h 4m, from 2026-03-25 16:22 UTC to 2026-03-26 11:25 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.