Emergency website support: Website down? Let’s find out why.

• A website or store no longer loads or shows a server error
• The site is infected, redirects to unknown pages or Google flags it as dangerous
• An update broke a critical function
• A form, checkout or admin panel stopped working

• Confirm what happened: symptoms, timing and available accounts
• Close access and change passwords so the attacker cannot come back
• Copy the current, broken state — needed to establish what the attacker did
• Contact the host: is there a backup from before the incident, and from which day

If a backup from the last 24–48 hours exists, restoring it is the fastest route, but changes made after it are lost — that is a business decision we make together. Without a backup I clean the files and database by hand, which takes longer.

Once the site is back I check the critical path (form, checkout, login), request a review in Google if the site was flagged, and describe how the break-in happened. I cannot promise recovery of data that does not exist in a usable backup.

For orientation, using the ranges from my article on website technical support: restoring a backup 0–1000 PLN, cleaning files and the database 1000–3000 PLN, rotating passwords, keys and certificates a few hundred złoty — a typical break-in usually lands at 1500–4500 PLN. I give an exact figure after diagnosis.

Incident type, access to hosting and code, backup condition and how far the infection spread all affect the figure. Sometimes diagnosis shows a rebuild is safer than a local patch — if so, I say so before we start.