FREEWebsite & Growth Audit — find out what's slowing your business down
protect

Website Down? The First-Hour Checklist and When to Call for Help

A calm first-hour checklist for a website outage: confirm it is really down, spot the likely cause, protect your business, and know when to hand it to specialists.

By Tech Pumpkin teamPublished Nov 19, 2026Updated Nov 19, 20263 min read

// quick answer

If your website is down, first confirm it is down for everyone, not just you. Then check the obvious causes — expired domain or hosting, a recent update or change, an error message, or a hosting outage — and tell your team and customers what is happening. If the cause is not obvious within the first hour, or there are signs of a hack or data loss, bring in specialists rather than experimenting on a live site.

// key points

  • First confirm the outage is real, using a second device, network or an online status checker.
  • Expired domains, hosting problems and recent updates cause a large share of outages.
  • The exact error message is the most useful clue for whoever fixes it.
  • Do not keep changing things on a broken live site; that can make recovery harder.
  • Monitoring, backups and a maintenance plan stop most outages from happening again.
// in this article
  1. 1. Is it down for everyone, or just you?
  2. 2. Check the expensive-but-simple causes
  3. 3. What changed recently?
  4. 4. Read the error message
  5. 5. Protect the business while it is down
  6. 6. Know when to stop and call for help
  7. After the fix: stop it happening again
  8. FAQs

A website outage always seems to happen at the worst time: during a campaign, a launch or a busy sales day. The first hour matters most. A calm, structured check usually tells you what kind of problem you have — and whether it is something to fix yourself or something to hand over immediately.

1. Is it down for everyone, or just you?

Before anything else, confirm the problem is real:

  • Open the site on your phone using mobile data, not office Wi-Fi.
  • Ask a colleague in another location to try.
  • Use an online “is it down for everyone or just me” checker.

If it works elsewhere, the issue may be your network, browser cache or a local DNS problem rather than the website itself.

2. Check the expensive-but-simple causes

  • Domain expired? Check your registrar account and renewal emails.
  • Hosting suspended or unpaid? Check your hosting dashboard and billing.
  • Hosting provider outage? Look at your host’s status page.
  • SSL certificate expired? Browsers show a security warning instead of the site.

3. What changed recently?

Most outages follow a change: a plugin or theme update, a new feature going live, a DNS or email change, or a hosting migration. Note what changed and when — it is the single most useful piece of information for whoever investigates.

4. Read the error message

Write down or screenshot exactly what you see:

  • 500 Internal Server Error — something failed on the server, often code, configuration or a faulty update.
  • 502 / 503 / 504 — the server is overloaded, unavailable or timing out.
  • “Error establishing a database connection” — the site cannot reach its database.
  • A blank white page — common after a failed WordPress plugin or theme update.
  • Unfamiliar pages, redirects or warnings — possible signs of a hack.

5. Protect the business while it is down

  • Pause paid ads that send traffic to the broken site.
  • Let your team know, so they can handle calls and emails.
  • Post a short update on your social channels if customers rely on the site.

6. Know when to stop and call for help

Hand it over to specialists if:

  • You cannot identify the cause within the first hour.
  • There are signs of a hack, malware or data loss.
  • The site takes payments, bookings or leads, and every hour costs revenue.
  • Fixing it means touching the server, database or code.

Repeated trial-and-error on a broken live site can overwrite evidence, corrupt data and make a clean restore harder. A specialist will usually check logs, isolate the fault on a copy of the site and restore from a known-good backup if needed.

After the fix: stop it happening again

Every outage is a signal. Uptime monitoring alerts you the moment the site goes down, tested backups make recovery fast, and a maintenance plan with updates tested on staging prevents the most common causes in the first place.

Frequently asked questions

Why is my website down?

Common causes are an expired domain or hosting plan, a hosting outage, a faulty update or change, an expired SSL certificate, traffic spikes and security attacks.

How do I know if my website is down for everyone or just me?

Try another device on a different network, ask someone elsewhere to check, or use an online website status checker.

What should I do first when my website goes down?

Confirm the outage, check your domain, hosting and recent changes, note the exact error message, and call for help if the cause is unclear or the site is critical to sales.

How can I prevent website downtime?

Use uptime monitoring, keep tested backups, apply updates on a staging site first and have a maintenance plan with a team that can respond quickly.

#Troubleshooting#Website down#Website maintenance

Tech Pumpkin team

Written and reviewed by the specialists who do this work for clients.

// related serviceWebsite TroubleshootingSee how we help →

// got a question about this?

Start a conversation with our team.

Tell our assistant what you’re working on — a real person reads every message and follows up.

Start a Conversation →

// new insights by email

Practical guides, no spam.

Tech Pumpkin AIInstant assistant. Let's start building.