Website Down? A Web Hosting Outage Response Checklist for Site Owners
website downtimehosting outagesincident responsetroubleshootinguptimehosting support

Website Down? A Web Hosting Outage Response Checklist for Site Owners

WWebHosting.Live Editorial Team
2026-11-09
7 min read

Use this practical outage checklist to identify DNS, server, application, SSL, and network failures, escalate support, and prevent repeat downtime.

When a website goes down, the fastest path to recovery is to identify which layer has failed before changing anything. This web hosting outage checklist helps you separate DNS, hosting-server, application, database, SSL, and network problems, preserve useful evidence, contact your provider effectively, and build a repeatable uptime-readiness routine.

Overview

A down website does not always mean the hosting server has failed. A domain may point to the wrong nameservers, a DNS record may be missing, an SSL certificate may be rejected, a WordPress update may have triggered a fatal error, or the origin server may be healthy while a network path is unavailable.

Start by recording the time, affected hostname, exact browser message, and whether the problem affects every visitor or only one connection. Avoid repeatedly refreshing the page while making unrecorded changes. A clear timeline makes it easier to compare provider notices, server logs, DNS results, and application changes.

Use this order for an initial triage:

  1. Confirm the symptom from more than one network or device.
  2. Check whether the domain resolves to the expected address.
  3. Check the hosting provider's status page and control panel.
  4. Test the web server and SSL response separately from the application.
  5. Review recent deployments, plugin updates, configuration changes, and resource alerts.
  6. Escalate to hosting support with timestamps and technical evidence.

If the site serves online payments, bookings, customer accounts, or other critical functions, follow your existing incident procedure first. For less critical sites, this workflow provides a practical starting point.

What to track

1. Symptoms and scope

Record the exact result rather than describing the site as simply down. Useful distinctions include a DNS error, connection timeout, refused connection, server error, redirect loop, certificate warning, blank page, slow response, or an application-specific error. Test the homepage and one known internal URL. If possible, compare HTTP and HTTPS and test both the bare domain and the www hostname.

Note whether the failure is global, regional, limited to mobile users, limited to logged-in users, or limited to a particular function such as checkout. A single user's browser cache or local DNS resolver can create a misleading result.

2. DNS and domain status

Check the domain's nameservers and the records used by the website. From a terminal, commands such as dig example.com, dig www.example.com, or nslookup example.com can show whether the hostname resolves and which address is returned. Replace the example domain with the affected hostname.

Compare the result with the address configured in the hosting panel. Also check for a recently changed nameserver, A record, CNAME, or DNS proxy setting. DNS changes can appear inconsistent while different resolvers update their cached answers, so record the resolver used and the result observed.

3. Server, application, and database layers

Use curl -I https://example.com to inspect response headers and the HTTP status without loading the full page. A timeout suggests a different investigation from a 500-level response, although the result alone does not identify the cause.

In the hosting control panel, review resource graphs, service notices, error logs, access logs, PHP or runtime versions, scheduled tasks, and recent backups. For a content management system, check whether a plugin, theme, extension, core update, or configuration edit happened shortly before the incident. If the application reports a database connection failure, verify database credentials, database service health, connection limits, and available storage before restoring or editing files.

4. SSL, network, and security signals

Check whether the certificate covers the hostname visitors use and whether the hosting panel shows an expired, pending, or failed renewal. Do not disable certificate verification as a permanent fix. A certificate problem can make an otherwise reachable website appear unavailable.

Compare results from a second connection, such as a mobile network, and use an external monitoring service if one is available. Review firewall, web application firewall, rate-limit, and IP-blocking events. Do not assume a security block is an outage until you have checked the relevant logs.

Printable outage checklist

  • Record the first observed time and timezone.
  • Save the exact error message and affected URL.
  • Test from a second network or monitoring location.
  • Check DNS resolution for the root and www hostnames.
  • Run an HTTP header request and save the result.
  • Check the provider status page, alerts, and control panel.
  • Review recent releases, updates, DNS edits, and account changes.
  • Capture relevant logs, screenshots, and monitoring alerts.
  • Open a support ticket and keep its reference number.
  • Record each change made during recovery.

Status-page reference table

What to checkWhere to lookWhat to record
Platform incidentProvider's current status pageIncident title, affected service, update time
Account or resource issueHosting control panel and billing areaWarnings, suspensions, quota alerts, maintenance notices
Domain or DNS issueRegistrar and DNS management consoleNameservers, changed records, propagation observations
Application issueSite and server logsStatus code, timestamp, URL, related error lines
Network or security issueFirewall, CDN, and monitoring dashboardsBlocked requests, regions, rule changes, alert times

Keep the provider's status-page URL, support portal, emergency contact method, and account identifier in an internal runbook. URLs, panel labels, and escalation options can change, so verify them during routine reviews.

Cadence and checkpoints

First 15 minutes

Confirm the scope, capture the error, test another connection, and check the status page. Avoid changing DNS or restoring a backup before establishing whether the provider or application is actually at fault.

After 15 to 30 minutes

Run DNS and HTTP checks, review control-panel alerts and logs, and identify the last known change. If the site is business-critical, open a support request even if the provider has posted a broad incident. Include the hostname, approximate start time, timezone, tests performed, and any relevant account or server identifier.

Support escalation template

You can adapt this message:

Subject: Website outage investigation for example.com

Observed from: [time and timezone]
Affected hostnames: [domain and subdomain]
Symptoms: [exact error or status code]
Scope: [all visitors, one network, region, or function]
Checks completed: [DNS, HTTP, control panel, logs, second network]
Recent changes: [deployment, DNS edit, update, or none known]
Evidence: [screenshots, timestamps, command output, monitoring alert]
Requested help: Please confirm whether the server, account, network, DNS service, or related platform component has an incident and advise on the next diagnostic step.

Do not include passwords, private keys, full payment details, or sensitive customer data in a ticket.

After recovery

Verify the homepage, representative internal pages, login, forms, transactions, email notifications, scheduled jobs, and monitoring alerts as applicable. Keep the recovery timeline until the incident review is complete.

How to interpret changes

A DNS failure usually produces resolution errors or an unexpected destination before the request reaches your hosting server. A server or network failure is more likely to produce a timeout, connection refusal, or provider-side notice. An application failure often returns an HTTP error, a blank response, or a site-specific message while the server itself remains reachable. An SSL problem commonly appears as a browser certificate warning or a failed secure connection. These patterns overlap, so use them to choose the next test rather than treating them as proof.

Look for correlation across independent signals. If external monitoring fails while your local test succeeds, investigate network path, DNS caching, regional routing, or filtering. If DNS is correct but HTTP responses changed immediately after a deployment, compare the application change with the error log. If several unrelated sites on the same hosting account fail together, check shared resource, account, or provider-level causes.

Track recurring variables in a simple incident log: date, duration, affected service, apparent layer, provider ticket, trigger, mitigation, and confirmed root cause. Repeated short outages may be more useful to investigate as a pattern than as separate events. A hosting performance test and ongoing monitoring workflow can complement this checklist; see How to Test Web Hosting Speed and Uptime. If incidents repeatedly involve resource limits, compare your current plan with guidance on shared hosting versus VPS.

When to revisit

Review this outage plan quarterly, after any provider migration, control-panel redesign, DNS change, major application update, or recurring incident. Confirm that monitoring still checks the right hostnames and URLs, credentials and account contacts are current, backups can be located, and the team knows who may approve a rollback or provider escalation.

After every incident, complete a short post-incident review:

  • What failed, and at which layer?
  • When was the issue first detected?
  • When did the correct responder begin investigating?
  • Which evidence established the cause?
  • Which action restored service?
  • What change would shorten detection or recovery next time?
  • Should monitoring, backups, DNS documentation, hosting capacity, or the provider support plan change?

Schedule a small outage-readiness drill each quarter. Test DNS lookups, monitoring notifications, support access, backup location, and the escalation template without deliberately taking production offline. If the site has outgrown its current plan or the provider cannot offer suitable visibility and support, document the evidence before comparing alternatives. For a planned move, use a dedicated website migration checklist rather than treating an emergency outage as the migration window.

Save this article with your internal runbook, replace the example commands and URLs with your own values, and update provider-specific details whenever your hosting environment changes. The goal is not to memorize every failure mode; it is to make the next outage more observable, less chaotic, and easier to resolve.

Related Topics

#website downtime#hosting outages#incident response#troubleshooting#uptime#hosting support
W

WebHosting.Live Editorial Team

Senior SEO Editors

Senior editor and content strategist. Writing about technology, design, and the future of digital media. Follow along for deep dives into the industry's moving parts.