- Level
- confirmed
- Worst impact
- Degraded
- Regions
- us
What to do
Check whether you use Hostinger in us. 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 16m it lasted.
Anything that failed between 2026-05-24 01:13 UTC and 2026-05-24 01:29 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
One of our providers is currently experiencing network issues that might directly impacting services in this region. CDN services might be affected. We are currently working on a resolution and will update You in the process. Thank You for Your patience.
provider
- resolved
The third-party connectivity issues affecting the US-BOS region have been resolved, and all CDN services are operating normally. Thank you for your patience while we worked with our provider to fix this.
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-940439d256
Is Hostinger still down?
No, this incident was resolved 2026-05-24 01:29 UTC. For Hostinger's live state, see https://down.guide/hostinger.
How long did it last?
16m, from 2026-05-24 01:13 UTC to 2026-05-24 01:29 UTC, by the times Hostinger posted.
What was affected?
Hostinger named in us.
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.