What should I do when my web shop suddenly goes offline?

First check from mobile data whether the site is really unreachable, and read your host's and payment provider's status pages. Take a backup if the site partly works, tell customers briefly, and do not change settings blindly.

How do I know whether my host is the problem?

Check the host's status page, then look at errors and resource usage in your hosting panel. If the whole site is unreachable or shows 502 or 503, the cause is often the server or load. If only payment fails, look at the payment provider.

What does a 503 error mean on a web shop?

A 503 means the server cannot handle the request right now, usually because of overload or maintenance. On busy days the limits of your hosting plan are a frequent cause. Check logs and resource usage in your hosting panel.

Should I tell customers the shop is down?

Yes, briefly and honestly, without promising a fix time you do not control. A social media post or a maintenance page with contact details protects trust. Also tell customers with open orders that their order is safe.

How do I prevent a crash during a sale?

Update well before the sale and test the checkout, use caching and a hosting plan that fits peak traffic, and switch on uptime monitoring with alerts. Keep tested off-site backups ready as well.

Can you fix an outage at my host?

No, we cannot fix an outage at your hosting company or payment provider. We can find out whether the problem is in your shop or on their side, repair the shop if it is broken, and tell you what to ask the host.

Downtime

Web shop crashes? What to do, step by step

Web shop crashed or slow on a busy day? Find out whether host, shop or payment provider is failing, what to tell customers and how to prevent it.

By IT bugsolutions
Updated October 23, 2026
6 min read

When your web shop crashes, first find out who is down: the shop itself, your host or your payment provider. Check the site from another network, check the host and provider status pages, tell customers briefly what is happening, and do not change settings blindly. Then restore from a clean backup or call for help.

Key takeaways

Decide first where the failure sits: shop, host or payment provider.
Take a backup of the current state before you fix anything.
Tell customers early and plainly. Silence costs more trust than an outage.
Monitoring, tested backups and a plan for busy days make most crashes shorter.

What should you do first when your web shop is down?

Stay calm and look before you click. A shop that fails during a sale or a campaign feels like an emergency, but random changes make most outages worse.

Reload the shop on your phone using mobile data, not your office wifi. This rules out your own network and browser cache.
Note exactly what you see: a blank page, an error code such as 502 or 503, a slow spinner, or a working homepage with a broken cart.
Check whether the whole site is affected or only the checkout, the admin or one page.
Read the status pages of your host and your payment provider.
Check your inbox for messages from your host. Hosts often announce maintenance or limits there.

This takes five minutes and tells you which of the next steps applies. If your whole site is simply unreachable, our guide on what to do when your website is down covers the first emergency steps; this article focuses on shops under load and on money.

Is it your host, your shop or your payment provider?

The error you see tells you where to look. This table is a rough guide, not a diagnosis.

What you see	Likely place	First move
Site not reachable at all	Host, DNS or domain	Host status page, domain expiry
502 or 503 error	Server overloaded or app crashed	Host panel, error logs
Very slow, then times out	Load, database or a heavy plugin	Resource usage in host panel
Shop works, payment fails	Payment provider or settings	Provider status and dashboard
"Error establishing database connection"	Database	Database service and credentials

Every page request travels through a chain. A fault at any link shows up as an error.

A request passes the browser, DNS, perhaps a CDN, the web server, the shop application and the database. Any link can fail, and the symptom shows which one. Our pages on a website that is down and the 503 Service Unavailable error go deeper into each case.

Why do shops crash at the busiest moment?

Busy moments expose weak spots that stay hidden on quiet days. A newsletter goes out, a social post takes off, or a sale starts, and hundreds of visitors arrive within minutes.

Each visitor asks the server to build pages, query the database and run the shop plugins. Cheap shared hosting has fixed limits on processes and memory. When those run out, you get 502, 503 or timeouts. Uncached pages, a heavy plugin, a slow search or an unoptimised image gallery make it worse.

Other common triggers are an update done right before the campaign, an expired certificate, or a full disk because logs and old backups piled up. Slow pages before the crash are often the warning. Read more in our guide to a slow website.

Look at the logs

Your host panel usually shows error logs and resource graphs. A flat line at the limit during the outage tells you load was the cause. A sudden PHP or database error tells you code or data was the cause.

What do you tell your customers while the shop is down?

Say something short, true and early. Customers forgive an outage faster than silence.

Post a one-line notice on social media and in your newsletter reply address
Put a simple maintenance page on the site if you can, with an email address or phone number
Tell customers with open orders whether their order is safe
Say when you will update them next, not when it will be fixed, unless you are sure
Pause paid advertising so you do not pay for clicks that cannot buy

Do not promise a fix time you cannot control. After the shop is back, check for orders that were paid but never recorded and contact those customers yourself. Our guide on checkout problems explains how to find them.

How do you fix the crash without making it worse?

Back up before you fix

If the site still runs partly, take a full backup of files and database now. If you restore an old backup over the current state without saving it first, you can overwrite orders placed since the last backup.

Then work from the cheapest, safest fix to the most invasive:

Clear caches and restart services only if your host allows it from the panel.
Disable the most recently updated plugin, or roll back the last change.
Raise resource limits, or temporarily move to a bigger plan if the cause is load.
Restore a clean backup if code or data is damaged, after saving the current state.
Contact the host's support with the exact error and the time it started.

If a recent update started the crash, the steps for a site broken after an update apply. If strange files or redirects appear, treat it as a possible hack instead.

How do you prepare for the next busy day?

Preparation is mostly boring, and that is the point. Most of it can be done in an afternoon.

Before the campaign

Update everything the evening before
Learn about the crash from a customer
Keep one untested backup on the same server

Better

Update a week early and test the checkout
Get an alert within minutes of a crash
Keep off-site backups and test a restore

A healthy site at a glance: backups, updates, certificate and uptime all in order.

Uptime monitoring that checks the homepage and the checkout and alerts you by email or SMS
Page caching and a CDN for pages that are the same for everyone
A hosting plan sized for peak days, not average days
Daily off-site backups and one real restore test per year
A written one-page plan: who to call, where the host login is, how to switch on a maintenance page

You can also run a quick load check before a big campaign, or ask your developer to do it. It shows where the shop slows down while you still have time to fix it.

How can we help?

We repair web shops remotely and work with a clear process. The first diagnosis is free, you get a fixed price before any work starts (web shop repairs from €450 excl. VAT), we make a backup before every change and you pay after the diagnosis. We cannot fix a hosting outage or a payment provider's own failure, but we can tell you quickly which side the problem is on.

To avoid being surprised, our care plans include uptime checks with alerts, SSL and domain expiry alerts, daily off-site backups and safe updates with rollback. If your shop is down now, contact us and include the error and the time it started.

Frequently asked questions

Also see