- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 21of 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 5h 9m it lasted.
Anything that failed between 2026-05-16 22:16 UTC and 2026-05-17 03: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 4
- investigating
We are currently experiencing degraded performance issues on U4S Node-2, located in Kuala Lumpur. Our team is currently working to restore normal performance levels. We apologize for any inconvenience caused.
provider
- identified
The fix is in progress.
provider
- monitoring
The fix has been applied and we are closely monitoring the situation.
provider
- resolved
The issue has been resolved. We apologize for any inconvenience caused, and thanks for your patience.
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-fd3353c10b
Is Hostinger still down?
No, this incident was resolved 2026-05-17 03:25 UTC. For Hostinger's live state, see https://down.guide/hostinger.
How long did it last?
5h 9m, from 2026-05-16 22:16 UTC to 2026-05-17 03: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.