What to do when your website goes down
When the site is down, the main thing is not to start changing things at random. Half of long outages are inflated by attempts to fix quickly.
Confirm the problem first
Check from mobile data and through an external availability checker. 'The site is down' often means one ISP, a stale DNS cache or one employee's machine.
Record exactly what you see: white screen, 500 error, connection failure, certificate warning, endless loading. Each points somewhere different.
Reading the symptoms
A 500 or white screen is application-side: a recent update, a plugin, a full disk or a database problem — server logs usually name the cause outright.
No resolution or a registrar placeholder means domain or DNS. A certificate warning means expired SSL. Slow with timeouts usually means a load spike or exhausted plan limits.
Order of actions and prevention
If it started right after a change, roll the change back rather than debugging on production. Contact support with specifics: start time, symptom, log excerpt.
Meanwhile put up a holding page with a phone number and Telegram contact — a visitor who sees 'maintenance in progress, message us' is still a lead; one who sees a browser error is not.