- 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 8d 17h it lasted.
Anything that failed between 2026-04-27 12:31 UTC and 2026-05-06 06:13 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
- investigating
We are currently fine-tuning rate limits for traffic originating from AWS and Microsoft network ranges to improve the overall user experience. During this time, some API and automated integrations may experience elevated 429 (Too Many Requests) error rates. This does not affect regular use of our services and client website visitors. We will provide updates as the adjustments progress.
provider
- resolved
The 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-9f19248440
Is Hostinger still down?
No, this incident was resolved 2026-05-06 06:13 UTC. For Hostinger's live state, see https://down.guide/hostinger.
How long did it last?
8d 17h, from 2026-04-27 12:31 UTC to 2026-05-06 06:13 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.