New

The new HostCloud is live. Web Hosting for ₹1 for your first month.

Web Hosting for ₹1 · first month

Claim offerClaim
Hosting & Performance

Website down because your host or CDN is down? A playbook for the first 60 minutes

When your hosting or CDN fails, you cannot fix their servers, but you can diagnose fast, communicate well and limit the damage. Here is a step-by-step playbook.

13 November 2026 · 9 min read
Website down because your host or CDN is down? A playbook for the first 60 minutes

Website down because your host or CDN is down? A playbook for the first 60 minutes

TL;DR: When your site goes down, spend the first minutes confirming whether the problem is yours, your host's or your CDN's. Check from another network, check the provider's status page, then post a short status message, switch to a workaround if you have one (bypass the CDN, point DNS to the origin, show a static page) and keep customers informed. The 18 November 2025 Cloudflare outage, which Cloudflare said was caused by an oversized configuration file and not an attack, showed that even large providers fail, so prepare before it happens.

Minute 0 to 10: confirm and locate

  1. Is it down for everyone? Test from mobile data and another device. See is my website down or just me.
  2. Check the error. A 5xx from the CDN, a connection timeout, a DNS failure and an SSL error point to different layers.
  3. Check your provider's status page and social account.
  4. Check your origin directly. Use the server IP or a hosts-file entry to bypass the CDN.
  5. Check recent changes. Did you deploy, update a plugin or change DNS?

Timeline of the first 60 minutes of an outage: confirm, communicate, workaround and recover

Which layer failed?

Symptom Likely layer
Error page from the CDN with a provider logo CDN or its bot or WAF service
Timeout, origin works by IP CDN edge or routing
Site fails by IP and domain Host, server or network
DNS lookup fails DNS provider
Certificate error SSL or CDN configuration

See DNS record checks.

Minute 10 to 30: communicate

Silence costs more than the outage. Post a short, honest update:

  • What users see
  • That you are aware and working on it
  • When you will update next

Use social media, a banner on another channel, email to key customers and a status page hosted somewhere else. Update every 30 minutes even if there is no news.

Minute 20 to 60: workarounds

  • Bypass the CDN. If your origin is healthy, change DNS to point directly to it. Keep TTLs low so it takes effect quickly. See DNS propagation.
  • Serve a static page from a separate host with a maintenance message and contact details.
  • Turn off the proxy for specific records if the provider allows it.
  • Switch checkout to a backup if payments are affected.
  • Pause ad campaigns that send traffic to a broken site.

Do not change DNS blindly. Know what each record does and take notes so you can reverse it.

Recovery

When the provider reports restoration, check that your site really works end to end: homepage, login, checkout, forms and email. Clear caches, restore DNS settings, review logs and watch for another failure. Then write down what happened.

Prepare before the next outage

What happened on 18 November 2025

Cloudflare reported that a configuration change led to an automatically generated file growing beyond its expected size, which crashed software handling traffic for several services. It said it found no evidence of an attack. Reports describe thousands of sites showing errors for several hours. The lesson is not to avoid a provider, but to know your dependencies and have a plan.

FAQs

What should I do when my website goes down?

Confirm whether it is down for everyone, check your provider's status page, communicate, and use a workaround if you have one.

How do I know if the CDN is the problem?

If the origin works by IP but the domain fails or shows a CDN error, the CDN layer is likely at fault.

Should I bypass my CDN during an outage?

If your origin is healthy and secure, pointing DNS to it can restore access, but plan the change and reverse it later.

How often should I update customers?

Every 30 minutes or so, even if just to say you are still working on it.

Where should I host my status page?

Somewhere separate from your main site and CDN.

Can I get compensation for downtime?

Check the SLA, since remedies are usually service credits.

How can I prepare for the next outage?

Monitor externally, keep backups, write a runbook, use low DNS TTLs and know your dependencies.

Was the November 2025 Cloudflare outage a cyberattack?

Cloudflare said it found no evidence of an attack.

Conclusion

You cannot stop a provider outage, but you can shorten its impact. Confirm the layer, communicate early, use a tested workaround and write the playbook before you need it.

HostCloud helps Indian websites with reliable hosting, domains and support. See the options at https://hostcloud.in.

Sources:

Related posts