Website Down? First Checks to Make Before You Panic

Open the site on a second device and switch from Wi-Fi to cellular data. If it works there, the problem may be your local network, browser cache, or DNS resolver rather than the website itself.

Write down the exact error message and the time it started. Screenshots, status codes, and recent changes shorten the diagnosis considerably.

Expired domains, incomplete DNS changes, and SSL certificate failures are common causes of sudden outages. Confirm that the domain registration is active and that the DNS records still point to the intended hosting provider.

Avoid repeatedly changing records while troubleshooting. DNS updates can take time to propagate, and multiple edits make the original problem harder to isolate.

If the outage followed a code or configuration change, inspect the deployment status and build logs. A successful upload does not always mean the application started correctly.

Environment variables, database migrations, and third-party API keys often differ between preview and production. Verify their presence without copying secrets into screenshots or support messages.

• Record the last known working deployment.
• Capture the first meaningful build or runtime error.
• Roll back only when you understand which production state will be restored.

When you request help, include the affected URL, the exact error, when it began, what changed beforehand, and which checks you completed. Do not send passwords or API keys.

A focused repair session can then move directly from diagnosis to the safest recovery path.