- Level
- confirmed
- Worst impact
- Degraded
- Regions
- apac
- Down Index
- 22of 100
What to do
Check whether you use Hostinger in apac. 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 1h 15m it lasted.
Anything that failed between 2026-07-02 09:34 UTC and 2026-07-02 10:49 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 experiencing degraded performance issues on server srv169.niagahoster.com located in Singapore. Client websites hosted there could be temporarily inaccessible, face 503 errors or might load slower than usual. Our team is currently working to restore normal performance levels. We apologize for any inconvenience caused.
provider
- monitoring
A fix has been implemented and we are monitoring the results.
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-bc128fa1e3
Is Hostinger still down?
No, this incident was resolved 2026-07-02 10:49 UTC. For Hostinger's live state, see https://down.guide/hostinger.
How long did it last?
1h 15m, from 2026-07-02 09:34 UTC to 2026-07-02 10:49 UTC, by the times Hostinger posted.
What was affected?
Hostinger named in apac.
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.