- Level
- confirmed
- Worst impact
- Degraded
- Components
- Hostinger DNS
- Down Index
- 21of 100
What to do
Check whether you use Hostinger Hostinger DNS. 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 5h 19m it lasted.
Anything that failed between 2026-03-02 22:13 UTC and 2026-03-03 03:32 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 4
- investigating
We are performing an emergency maintenance work on one of the servers for our authoritative DNS service. This may lead to cPanel DNS services not being reachable, stable or unavailable. Our team is currently working to restore normal performance levels. We apologize for any inconvenience caused.
provider
- identified
The issue has been identified and a fix is being implemented.
provider
- monitoring
A fix has been implemented and we are monitoring the results.
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-a4fcf3131b
Is Hostinger still down?
No, this incident was resolved 2026-03-03 03:32 UTC. For Hostinger's live state, see https://down.guide/hostinger.
How long did it last?
5h 19m, from 2026-03-02 22:13 UTC to 2026-03-03 03:32 UTC, by the times Hostinger posted.
What was affected?
Hostinger named Hostinger DNS.
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.