Your Site Is Down: A Ten-Minute Checklist

Start with what you can check in a minute

Before you assume the whole site is broken, open it in a second browser if you have one. Then try your phone on cellular data, not Wi-Fi. If the site loads there but not on your office computer or office internet, the issue may be local.

Check the page in a private or incognito window too. A saved login, a stale page, or a browser extension can make a site look down when it is not. If the site loads for other people but not for you, write that down before you call anyone.

• Try a different device, different browser, and different connection.
• Clear the page only after you know it is not a local problem.
• Note the exact error message if one appears.

Tell the difference between a site problem and a web address problem

If your page shows a message about the address not being found, the domain may be the issue. That can happen if a renewal was missed, the name was changed, or the domain points to the wrong place. If the site used to work and now sends people somewhere odd, that is a clue that the address settings need a look.

If the address loads but the site is blank, shows an error, or keeps timing out, the hosting side may be the problem. A site can also break after a bad update, a plugin conflict, or a file change. The shape of the error matters, so keep it simple and describe exactly what you see.

• A missing-address message points more toward the domain.
• A blank page or server error points more toward hosting or the site files.
• Do not change random settings before you know which part is failing.

Check for the easy business issues first

A site can go dark because a card on file expired, a renewal failed, or a billing notice was missed. If you or your staff handle domain or hosting payments, check the inbox tied to those accounts. Search for words like renewal, payment, billing, suspension, or action required.

If someone else handles the site, ask them if they saw a warning before the outage. Many problems give a warning first and then move to a shutdown later. A busy owner can miss those messages, so ask the person in charge to look for notices before making changes.

• Search all inboxes tied to the business, not just the main one.
• Check spam and promotions folders for renewal notices.
• Ask if the last payment method changed recently.

Think about the last change made to the site

If the site went down after an update, a new page, a plugin change, or a design edit, that is a strong clue. A small change can clash with something else already on the site. If you know the exact time the issue started, share that when you ask for help.

If you use WordPress, updates can help keep things current, but a bad update can also cause a problem. Do not keep clicking update again and again. That can make troubleshooting harder. Instead, note which update happened last and whether the site failed right after it.

• Write down the last change, who made it, and when.
• If the site broke after editing, stop editing until it is checked.
• Take a screenshot of the error if you can.

Who to call, and what to say

Call the person or team that manages your hosting, your domain, or your website files. If one person handles all of it, start there. If you are not sure who owns what, ask for the account holder or the person who can check server logs, billing, and recent updates.

Keep your message short and specific: say the site address, what you see, when it started, whether it fails on all devices, and whether anything changed right before it happened. If you have screenshots, send them. If you checked billing, say that too. That saves time and helps them sort the problem faster.

• Use a plain message: the site address, the error, the time it started, and what changed.
• Mention if it works on cellular data but not on office Wi-Fi.
• Ask them to check domain status, hosting status, and recent updates.

Keep customers informed while you fix it

If people cannot reach your site, they still need a way to contact you. Put a short update on your Google Business Profile if you can access it. You can also post on Instagram, Facebook, or TikTok if those are active for your business. Keep the message plain: the site is having a problem, you are working on it, and people can call or message you for now.

If you use a phone line, voicemail, or text replies, make sure the message matches what customers will see on social. Do not overexplain. A clear note builds trust better than a long apology. If you can, tell staff what to say so everyone gives the same answer.

• Put one short update everywhere you talk to customers.
• Share another contact method if you have one.
• Remove the update when the site is back.

After it is fixed, clean up the loose ends

Once the site is back, ask what caused the outage and what should change so it does not happen the same way again. That might mean updating billing details, keeping renewals under one email address, checking who has admin access, or writing down which person handles which part of the site.

Keep a small site note for your business with the domain login, hosting contact, update history, and emergency steps. Store it where you and one backup person can find it. If Brixel Proyect helps with your site, ask for the same plain summary so your team knows where things stand without hunting through messages.

• Save the cause, fix, and contact person in one place.
• Review payment details and renewal reminders.
• Limit who can make live changes without a second set of eyes.