When your website goes down, the right person to call depends on the root cause of the outage. If the entire server or your professional email is offline, contact your hosting provider or IT support. If the site displays a database error or a blank white screen, contact your website management or development team.
Determine the scope of the outage
The first step when a website goes down is to figure out whether the problem is global or isolated to your specific web files. You can use free online uptime monitoring tools to test if the site is down for everyone or just for you. If the tool reports that the site is fully accessible from other locations, the issue is likely related to your local internet connection, your office router, or a cached version of the page in your browser.
If the testing tool confirms the site is down for all visitors, you are dealing with a server outage, a domain name system error, or a critical error within your content management system. Checking your business email can also provide clues. If your email is working, your domain is probably still active. That does not clear your web host, though, because many businesses run email on a separate service such as Google Workspace or Microsoft 365. If your email and website are hosted by the same company, working email points more toward a recent code update or plugin failure on the website itself.
- Test the URL using an external uptime checker
- Clear your browser cache and try loading the page
- Check if your business email is still working
- Ask a colleague on a different network to test the link
When to contact your IT support or hosting provider
You should contact your IT department or your web hosting provider when the infrastructure underlying your website fails. This includes issues related to server hardware crashes, expired domain name registrations, secure sockets layer certificate failures, or network routing problems. Hosting providers have direct access to the server logs and can restart services or restore server functionality much faster than a standard web designer.
Internal IT teams are also responsible for managing your company network, office firewalls, and employee computers. If your employees cannot access the content management system dashboard or if your business email is failing alongside the website, your internal or outsourced IT support professional is the correct person to diagnose the underlying infrastructure breakdown.
- Server hardware failure or unexpected downtime
- Domain name expiration or incorrect DNS routing
- SSL certificate installation and renewal errors
- Network-wide internet or firewall blocks
When to contact your website management team
You should contact your website management agency or developer when the server is online, but the website itself is throwing errors or displaying incorrectly. Common culprits include a broken software update, a malfunctioning plugin, corrupted database tables, or a coding error introduced during recent site edits. These issues require technical code-level intervention rather than server-level administration.
Website managers can quickly access the site backend via secure file transfer protocol or database management tools to roll back recent changes or disable faulty code. While your hosting provider can sometimes restore a daily backup, your web developer is uniquely qualified to investigate why the error occurred in the first place and prevent it from happening again.
- Internal database connection errors
- White screen of death after a plugin update
- Broken layout or missing styling after edits
- Malware infection or unauthorized site defacement
The companies behind your website, and what each one controls
A big reason website outages get confusing is that a working site depends on several companies at once, and each one can only see its own piece. Knowing who handles what saves you from being passed back and forth.
| Who | What they control | Call them when |
|---|---|---|
| Domain registrar | Your web address and its renewal | The domain has expired or a renewal payment failed |
| Web host | The server, its uptime and server-level backups | The whole site is unreachable, slow to the point of failing, or showing server errors |
| Website manager or developer | The site software, plugins, theme and custom code | The site broke after an update or edit, or shows an application error |
| IT support | Your office network, computers, firewall and often your email | The site works on cell data but not at the office, or staff cannot get online at all |
Sometimes one company wears two of these hats, and a small business may have no IT provider at all. If your domain name system (DNS) is managed by a separate service, add that company to your list too, since a wrong setting there can take a healthy site offline.
What the error on your screen is telling you
The exact wording on the screen is one of the best clues you have. Take a screenshot before you refresh or change anything, then use this chart to choose your first call.
| What you see | What it usually means | Call first |
|---|---|---|
| This site can’t be reached, or a DNS error such as DNS_PROBE_FINISHED_NXDOMAIN | The web address is not pointing to a server. The domain may have expired or a DNS setting may have changed | Registrar, or whoever manages your DNS |
| A parked page or a renewal notice instead of your site | The domain registration has lapsed | Registrar |
| Your connection is not private | The security (SSL) certificate has expired or is not set up correctly | Host |
| 502, 503 or 504 error | The server is overloaded, in maintenance or not responding in time | Host |
| 500 internal server error | Something failed on the server. It can be the server setup or a website code problem | Host first, then developer |
| 403 forbidden | A permission setting or security rule is blocking visitors | Host, then developer |
| 404 on pages that used to work | A page was removed or its address changed | Developer or website manager |
| Error establishing a database connection | WordPress cannot reach its database. The database server may be down or the login details may be wrong | Host first, then developer |
| There has been a critical error on this website, or a blank white page | A plugin, theme or code error, often right after an update | Developer or website manager |
| A red browser warning such as Deceptive site ahead, or strange pages and redirects | The site may be hacked | Developer, and see how to fix a hacked website |
A five-minute check before you call anyone
- Try it on your phone with Wi-Fi turned off. If the site loads on cell data but not at the office, the website is probably fine and the trouble is on your network.
- Run an outside check. Free tools such as Down for Everyone or Just Me and Pingdom test your address from outside your building.
- Look up your domain. The free ICANN Lookup tool at lookup.icann.org shows the expiration date and which registrar holds the domain.
- Search your inbox for billing notices. A declined card on a hosting or domain renewal is a common and easily fixed cause.
- Ask what changed. Find out whether anyone updated a plugin, edited the site or changed a setting in the last day or two.
- Check your host’s status page. Many hosts post known outages there, which can save you a long wait on hold.
How to get a faster fix when you call
For a real outage, phone or live chat usually beats an email or support ticket, since written requests tend to sit in a lower priority queue. Have this ready so nobody has to start from zero:
- The web address, and your account name or customer number
- When the problem started and when you last saw the site working
- The exact error message, with your screenshot
- What the outside check showed, and whether it fails on cell data too
- Any recent updates, edits or new plugins
- What your email is doing, and whether it is hosted with the same company
If the host and your developer each say the problem belongs to the other, ask the host to confirm in writing that the server is healthy and what its logs show, then pass that to your developer. Hosts usually fix their own outages at no charge, but cleaning up software problems may be billed, so ask before work starts.
Be careful with the restore button
Restoring a backup can be the quickest way back online, but it rolls the site back to that date. Orders, form entries, blog posts and edits made since then can disappear. Ask whoever is doing the restore to save a copy of the current site first, and download any recent orders or leads. If the site may have been hacked, an old backup may also still contain the same hole, so have someone find the cause too.
Keep customers in the loop during an outage
Your phone still works when your website does not. If the outage lasts more than a little while, post a short note on your social media and your Google Business Profile with the best way to reach you. Your host or developer may also be able to put up a simple temporary page with your phone number. For a Tacoma service business that gets calls from its site, staff should also know to take bookings by phone until things are back.
Make the next outage shorter
- Turn on auto-renew for your domain and hosting, and keep the card and contact email on those accounts current.
- Set up uptime alerts so you hear about an outage from a free monitoring tool instead of a customer.
- Write a one-page emergency sheet with your registrar, host, developer and IT contacts, and keep a copy off the website and off your work email.
- Hold your own logins. Ideally the registrar and hosting accounts are in the business’s name, as explained in who owns your website.
- Confirm your backups can be restored, and that a copy is stored away from the main server.
- Decide who to call after hours. Many developers do not offer 24/7 support, so ask now. If outages keep happening, it may be time for a more reliable host.
If you would rather have one team watching all of this, contact us and we can talk through what ongoing website management would look like for your business.
Key takeaways
- Test your website using an external uptime checker to confirm if it is down for everyone.
- Contact your hosting provider or IT team for server outages, domain issues, and email failures.
- Contact your website management team for code errors, plugin conflicts, and database issues.
- Keep records of your hosting credentials and developer contact information accessible in an offline format.
Related questions
How can I check if my website is down for everyone?
You can use free online uptime checking tools that ping your web address from multiple locations around the world to verify its status instantly.
Will my web host automatically fix my website if it breaks?
Web hosts typically guarantee server uptime, but they rarely maintain the actual website code, meaning software errors are usually the owner's responsibility to fix.
What is the white screen of death?
The white screen of death is a common content management system error where the page displays entirely blank, usually caused by a fatal PHP code error.
How do I find out who hosts my website?
Check old invoices and card statements for hosting charges, then ask whoever built your site. A hosting lookup tool can often identify the company too, using your web address. If you find the site runs through a service that sits in front of the server, you may need to ask your developer which company holds the actual hosting account.
Will a short outage hurt my Google rankings?
A brief outage rarely does lasting harm, because Google expects sites to have the occasional problem. A site that stays down or returns server errors for a long stretch can see Google crawl it less and eventually drop pages from search. Once you are back online, check Google Search Console for errors.
What if my domain has already expired?
Call your registrar right away. Registrars usually allow a period after expiration to renew, but the length and fees vary, and once it ends someone else may be able to register the name. Email on that domain can stop working as well, so treat it as urgent.
