Skip to main content
Hostinger

Degraded ID CDN service

Degraded Lasted 16m · started · Hostinger's page

Level
confirmed
Worst impact
Degraded
Components
Hostinger CDN
Down Index
14of 100

What to do

  • Check whether you use Hostinger Hostinger CDN. 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-03-20 01:33 UTC and 2026-03-20 01: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

  1. investigating

    The websites that have our ID CDN enabled may experience degraded performance. We are currently working on implementing the necessary changes. Please note, that no data will be lost and Your websites will not be affected. Thank You for Your patience.

    provider

  2. monitoring

    A fix has been implemented and we are monitoring the results.

    provider

  3. 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-35d3336472

Is Hostinger still down?

No, this incident was resolved 2026-03-20 01:49 UTC. For Hostinger's live state, see https://down.guide/hostinger.

How long did it last?

16m, from 2026-03-20 01:33 UTC to 2026-03-20 01:49 UTC, by the times Hostinger posted.

What was affected?

Hostinger named Hostinger CDN.

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.