The server is gone. Now what
Recovering a Small Business Website After a Hosting Failure, Backup or No Backup
Your host has crashed, suspended you, lost your files or quietly stopped existing. Nothing you do in the next ten minutes will make it worse if you do not start deleting things. Find out what actually failed, hunt down the newest good copy, then move it somewhere you control.
November 14, 2026 · 9 min read
The short answer
To recover a website after a hosting failure, first confirm what failed: the host, the domain or DNS. Then find the newest backup containing both files and database, restore it on a new host, test it on a temporary address, and point DNS at it last. Check business email separately, then test every form. No backup means rebuilding.
On this page
- Prove it is the host before you move anything
- The backup hunt, from most likely to most desperate
- Restore in private, and touch DNS last
- What Google does while your server is on the floor
- No backup at all, and the case for not rebuilding the old thing
- Three dull habits that make this a two-hour problem next time
Prove it is the host before you move anything
It is entirely possible to move a whole website to a new company over a problem at the registrar, and then find the same blank page waiting there too. Your site has three separate suppliers, and they fail differently. Security patches arrive on the host's schedule too, which is the subject of what shared hosting shares besides a server. The symptom usually tells you which one, for free. Check from a phone on cellular so your own network is not part of the question.
| Probably failed | First move | |
|---|---|---|
| A numbered error: 500, 502, 503, 504 | The server or the software on it | Check the host's status page. Then read 500, 503 or 504 |
| "Error establishing a database connection" | The database, or the link to it | See the database error page. Often recoverable without moving |
| A host notice saying suspended | The account: unpaid, or flagged for abuse or malware | Read the email they sent, then the suspension page |
| "This site can't be reached," and email is failing too | The domain or DNS, probably not the host | Check your domain's expiration, then DNS |
| A parking page or an ad for your own name | The domain expired | Call the registrar today. Do not wait |
| The host's own site is gone too, and nobody answers | The host itself | Go to the backup hunt below |
If the domain is the failure, ICANN's published timeline matters. After expiration, a domain may enter a 30-day Redemption Grace Period, which can involve a redemption fee; if not restored, it goes to PendingDelete for 5 days and is then released first-come, first-served. We are not lawyers, so if a registrar or host dispute is what stands between you and your name, take it to your own attorney.
The backup hunt, from most likely to most desperate
A working WordPress backup has two halves, the files and the database. Your images and theme live in the files. Your actual words usually live in the database. Owners regularly find a folder called "website backup" and learn it contains a logo and a theme from 2019. So check what you find before you celebrate. Look in this order, and download anything promising to your own computer right now.
- 1.The host's control panel, if you can still get in. Many hosts keep some copies. Do not count on how far back they go.
- 2.A backup plugin's outside storage. Look in Dropbox, Google Drive or Amazon S3 accounts tied to the business. A plugin may have been faithfully filing copies there for years.
- 3.The developer. Even one who left may have an old copy on a laptop. A short, friendly message works better than a threatening one. See when a developer disappears.
- 4.A staging or test copy. Look for old addresses such as a "staging" or "dev" subdomain that may still be running elsewhere.
- 5.Your own computer and email. Text sent for the original site, photos you supplied, and PDFs of pages you approved.
- 6.The Wayback Machine. Last, and only for what it can do. See below.

What the Wayback Machine will and will not give back
The Internet Archive's Wayback Machine help page, read in November 2026, describes viewing archived versions of publicly available web pages. It also says the archive skips pages behind passwords or forms, can be limited by robots exclusions and site owners' requests, and will not contain the original site's functionality where forms or JavaScript are involved. Its help page does not describe restoring a site. So treat it as a record of what your pages said, a place to recover text and maybe some images. It may have nothing at all for a small site. It is not a backup.
Restore in private, and touch DNS last
The most common mistake here is moving your name to the new server first and fixing things in public while customers watch. Do it in the other order. Your domain and your site are separate things, so the new site can be built and tested at a temporary address while the old name keeps pointing wherever it points.
- 1
Open a hosting account in your own name
Your business, your card, an address you read. This is not the day to let someone else hold it. Note the plan's backup terms.
- 2
Restore files and database, then load the site on a temporary address
Click every page, and look for missing images. Note the backup date, since anything newer is gone and may need re-entering.
- 3
Copy your current DNS settings before you change anything
Take screenshots. Your email records live in the same place as your website's address, and they need to stay exactly as they are.
- 4
Point the website's records to the new host
Only those records. Old values can linger for a while on some networks, so a mixed picture for a short time is normal.
- 5
Confirm the security certificate and the padlock
A new server may need a new certificate. If browsers warn visitors, see an expired SSL certificate and the not secure warning.
- 6
Send test messages to yourself
Business email in both directions, then every form. Moves break both, quietly. If email went down, this page on lost email after a move is next, and testing a form takes about four minutes.
What Google does while your server is on the floor
Do not panic over an afternoon. But do not leave it until spring. Google Search Central, read in November 2026, says server errors slow down its crawling, that indexed pages are kept at first, "but eventually dropped" if they keep returning errors, and that crawling gradually picks up again once the server answers normally. It gives no fixed number of days, and neither will we.
While you work, keep customers reaching you by other means. Correct your Google Business Profile if needed, since your phone number there still works when your site does not. Change your voicemail greeting. If the restore will take a while, a plain page on your own domain with your name, service area and phone number beats an error. Understand the trade: the old addresses will still be missing, so restore them under the same addresses as soon as you can, and check your indexing once you are back.
A backup nobody has restored is a rumor with a file name.
No backup at all, and the case for not rebuilding the old thing
Sometimes the hunt turns up nothing. You lost the files, and the host is not coming back. That is bad. It is not the end of the business, since you still have your domain, your customers, your reviews and your phone number. Rebuild from what you can gather: the Wayback Machine for text, your Business Profile and phone for photos, and old invoices for your service list.
Then notice what just happened. You no longer have to preserve a site that may have been holding you back. A new site does not have to be the old one reconstructed. Decide from what the site actually has to do, which is usually far less than the old one tried to do.
| When it fits | Cost | |
|---|---|---|
| WordPress site down, and access still works | A server-side break that does not require moving hosts | $249 fixed, with a refund if we cannot fix it |
| Site infected, and the host pulled the plug | A suspension caused by malware | $349 fixed on WordPress |
| A restore from a good backup, or a custom site | Files exist but the work is larger than a fixed repair | Quoted once we have seen what you have |
| Nothing recoverable | You rebuild. Up to 10 pages is enough for many one-person shops | $1,500, or $375 down and $93.75 a month at 0% |
| Keeping the next one safe | Daily off-server backups, test-restored, and someone watching | From $55 a month |
Three dull habits that make this a two-hour problem next time
Keep a copy somewhere the host cannot reach
A backup on the same server dies with the server. Automatic off-server copies, weekly or better for a site that changes, cost little and are easy to set up. Then restore one once a quarter. Otherwise, you have only a hope.
Own the accounts and read the notices
Put the domain and hosting in your own name, and send renewal and suspension notices to an address you actually read. Many "hosting failures" are a card that expired and three unread emails.
Write one page of notes
Who the registrar is, who the host is, where the backups go, and a screenshot of your DNS. Keep it where a person could find it if you were on a roof, or in a hospital.
If you would rather pay someone to have those habits, our plan, starting at $55 a month, includes them, and the maintenance section spells out what else a very small business gets. Compare the price in what upkeep actually costs. Other paths through the mess are in the repair guide and across our section for small businesses. If your site is down right now, call (210) 346-0848 and tell us what you see.
Questions owner-operators ask
With a clean backup and access to DNS, it can be a short job. Without a backup, it becomes a rebuild. We will not promise a time for a site we have not seen, because the state of the backup decides nearly everything. DNS changes can also take a while to appear everywhere. Having your registrar login and a copy of your files ready shortens it the most.
Ask them in writing for any backups they hold, and ask for dates. Your rights depend on the terms you agreed to, and many hosting terms put backups on the customer. We are not lawyers, so take any claim for losses to your own attorney. Meanwhile, keep hunting for other copies, because a dispute will not bring your site back this week.
Partly, if it captured your site. It can help you recover text and possibly images from public pages. According to its help page, it does not capture pages behind passwords or forms, and it does not keep the original functionality where forms or JavaScript are involved. Use it as a reference for rewriting, not as a backup. Plan on rebuilding the forms, the booking and the structure.
Only if your email is tied to that host or if DNS sat there too. Many businesses use a separate email service, which keeps running during a web host's outage. Check where your email's records point before you change any DNS, and screenshot them. Moving the website carelessly is often what breaks the email, days after the site itself came back.
Usually not. A domain and a host are separate things, even if you bought them from the same company. Look up your registrar with a WHOIS search and confirm you hold the account. If the same failed company was your registrar too, the process is harder. Start with ICANN's list of accredited registrars and your own attorney, and do not rush to buy a new name.
Backups stored off the server, a restore you can test, a person to reach when it breaks, and an account in your own name. Ask how long backups are kept and who pays to restore one. The cheapest plan is fine for a simple site if you handle those things yourself. If you will not, pay someone to, because you have now seen the alternative.
Keep reading
- Nobody was lookingWebsite Maintenance for One-Person Businesses: Who Looks After the Site When You CannotSmall business website care from $55 a month: hosting, updates, backups and small edits, what quietly fails when nobody looks, and when not to pay us.
- When the builder goes quietWhat to Do When Your Web Developer Disappears: The Domain First, Then Everything ElseYour web developer stopped answering. Secure the domain, hosting, code and logins in that order, using ICANN's rules, and know when to call an attorney.
- One owner, one phoneWeb Design for One-Person Businesses: What You Need and What to RefuseWebsite design for one-person businesses: the short page list, what to refuse to pay for, and fixed prices from $1,500, or when a builder plan is better.
- The build sideSmall Business Website Development: Who Holds the Keys When the Builder LeavesWebsite development for independent contractors: who owns the code, domain and accounts, what custom means at $1,500, and what you must maintain yourself.
- Probably not. Sometimes yes.iOS App Development for Small Businesses: When an iPhone App Earns Its KeepWhen an iPhone app makes sense for a very small company, what from $3,750 buys, Apple's fees and rules as of 2026, and what to try before you build.
- Two stores, one budgetMobile App Development for Small Business: iPhone, Android or a Web App FirstiPhone and Android apps for a small business: web app from $575, native from $3,750, Google Play and Apple fees as of 2026, and what to build first.
- Everything in MicrobusinessSee the section
From the Insights desk
- Why Every San Antonio Small Business Needs AI Agents: Increase Sales, Cut Costs, and Improve Local Customer ExperienceAI agents are practical tools San Antonio small businesses can deploy today to increase sales, cut costs, and improve local customer experience.
- Your Website Is Telling You It's Broken. Here Is the Translation.500, 502, mixed content, white screen, robots.txt blocking Google. Your site talks in a dialect built for engineers. Here is what each message actually means about your business — and what it costs while you look it up.
Tell us what's on the screen, and what copies you've found
Send the error, the host's name and anything that looks like a backup. A person at DataCram replies with what is recoverable and what the next step costs.
Which of these sounds like you? (pick any)
Rather talk now? Call (210) 346-0848.