The short answer
This message means WordPress can't reach the database where all your content lives. The most common cause by far is the hosting company's database server being down or overloaded — which fixes itself when they fix it — followed by resource limits, wrong credentials after a change, or a damaged database. Your first move costs nothing: check whether it's a hosting outage before touching anything. The reassuring headline: this error almost never means your content is gone. If your host says their side is fine and you're out of safe options, our WordPress repair service can take a proper look — asking is free.
What the error actually means
WordPress keeps everything you've ever written — pages, posts, products, settings — in a database, which is a separate service on your hosting. Every page view starts with WordPress knocking on the database's door. This error is the door not answering. The important distinction: the content almost certainly still exists; the connection to it has failed. That's why this error looks catastrophic — every page replaced by one stark sentence — yet usually resolves completely. Think of it as the shop's stockroom being unreachable, not the stock being destroyed.
Want a professional pair of eyes on your own site? Request a free website review — plain-English findings, no obligation.
Checks anyone can do first
Before any technical step, rule out the simple explanations. Look at the site on your phone with Wi-Fi off, to be sure it isn't your connection. Check your hosting provider's status page — most maintain one, and database outages are usually acknowledged there within minutes. Search your inbox for maintenance or suspension emails from the host, and confirm the hosting bill has actually been paid: suspended accounts frequently surface as database errors. Note exactly when it started. Then, if the host's status page shows an incident, simply wait — refreshing every thirty seconds won't speed up their engineers, and most outages clear within the hour.
The likely causes, in order
On shared hosting — where most small-business WordPress sites live — the ranking runs roughly like this. First, the database server itself is down or overloaded: not your fault, and extremely common. Second, your account has hit its resource limits: a traffic spike, a runaway plugin or a brute-force attack can exhaust your allowance and the database stops answering. Third, wrong credentials: the database username or password stored in WordPress no longer matches the hosting account — classic after a migration, a password reset, or a hosting change. Fourth, corrupted database tables, often after an interrupted operation or a server crash. Fifth, full disk space on the server, which stops the database writing anything. Only then come the exotic causes.
Safe checks for a confident owner
If you're comfortable in your hosting control panel, three checks carry almost no risk. Look at your disk usage — a full account breaks databases in confusing ways, and deleting old backups or logs from the panel can bring a site straight back. Open the panel's database tool (usually phpMyAdmin): if the tool itself can't connect, the problem is the database server, which settles the 'is it me or them?' question instantly. Some hosts offer a 'repair database' or 'check database' button in the panel — running the read-only check is safe and tells you whether tables are damaged. One rule throughout: photograph or write down any setting before you change it, so every step is reversible.
Tasks that need technical access
The remaining fixes are where a confident-looking tutorial can quietly sink a business site. Verifying the database credentials means comparing wp-config.php against the hosting panel — but a mistyped edit to that file turns 'database error' into 'blank white screen'. WordPress has a built-in repair mode, but enabling it means editing configuration, and leaving it enabled afterwards is a security hole. Reading server error logs to distinguish corruption from overload takes practice. And restoring the database from a backup is safe only when you know the backup is complete and predates the problem. These are all legitimate fixes — they're just the point where a steady hand and recent backups stop being optional.
What not to do
Don't reinstall WordPress: the error isn't in WordPress's files, and a reinstall over a live database risks turning one problem into two. Don't change the database password repeatedly 'to see if it helps' — each change must also be made in wp-config.php, and mismatches multiply. Don't download and run 'repair scripts' from forums; scripts with database write access from strangers are how sites get hacked. Don't assume it's a hack — it usually isn't, though a sudden flood of attack traffic can cause it; our guide to what to do if a website is hacked covers the signs if you have genuine reason to suspect one. And don't panic-delete anything in the database tool: there is no undo button.
If the database itself is damaged
Corruption sounds terminal but usually isn't. Individual tables can often be repaired in place — the data stays, the structure gets fixed — and where repair fails, restoring the database from a backup predating the damage is the fallback. What matters is the cause: a table that crashed once during a server restart is bad luck, but corruption that keeps returning points at failing hosting, and repairing it monthly is treating the symptom. Keep more than one backup generation where you can; if damage went unnoticed for a week, last night's backup contains the same damage. And after any restore, test the forms and checkout — the parts that make you money — before declaring victory.
After it's back: stop it recurring
A one-off outage needs no follow-up, but repeat database errors are your hosting telling you something. Ask the host directly whether your account is hitting resource limits; if the answer is yes — or vague — the fix is a bigger plan or better hosting, not more repairs. Our plain-English guide to website hosting explains what actually matters when choosing. Uptime monitoring that emails you the moment the site drops is cheap and turns 'a customer told us' into 'we already know'. And if the site matters to the business, a maintenance plan means someone is watching, updating and backing up so this page of the internet is one you never need again.
When to get help — and what it costs
Always call your host first: it's free, and in the most common scenario the fix is entirely theirs. Escalate to a developer when the host says their side is healthy, when credentials or corruption are involved, when you don't have a backup you trust, or when the site simply can't stay down. Most single repairs are quoted from £95, depending on the cause and complexity. You approve a fixed written quote before any work begins, and the initial enquiry is free — tell us what you're seeing, including how long it's been down and what your host said, and you'll get an honest assessment. If you'd like eyes on the wider health of the site while you're at it, the free website check is the place to start.
Common questions
Is my content gone? Almost certainly not — the error means unreachable, not erased, and content typically reappears untouched once the connection is restored. How long does this usually last? Hosting outages typically clear within minutes to a few hours; credential and corruption fixes take as long as the diagnosis plus the repair, and you'll always get an honest timescale from us after a look rather than a guess before one. Is this the same as being hacked? No — and most cases aren't attacks, though sustained attack traffic can overload a database into this state, so it's worth asking your host whether they saw unusual traffic. Will it hurt my Google rankings? A few hours of downtime won't; a site erroring for days will start to, which is one more reason persistent cases deserve proper attention rather than hope.
Want this handled for you?
Get a free, plain-English review of your website — what's working, what isn't, and what's worth fixing first.
Get a Free Website ReviewRelated services: WordPress Development · Website Repairs