Is Hostinger down, or is it just your site? A quick way to tell

A site that won't load feels like a host outage. Usually it isn't. The cause is more often nearer to you: your connection, DNS, a cache, or the site's own code. Run these in order and you'll know which side of the line the problem is on.

1. 1Open Hostinger's status page. An active incident means it's Hostinger, and your job is to wait.
2. 2Load the site from a different network, such as mobile data instead of Wi-Fi, or a free "is it down" checker. If it loads there, the issue is on your side.
3. 3Open hPanel at hpanel.hostinger.com. If hPanel works and the site doesn't, the platform is fine and the problem is your site or domain.

Hostinger publishes live status at statuspage.hostinger.com, also linked from its help center. It lists each part of the platform separately (websites, hPanel, email, VPS, DNS) with current and recent incidents and timestamps.

If your component shows an incident, there's nothing for you to fix. Subscribe to updates on that page and wait for the resolution notice. If it's all green, look at your own site or network.

Match what you see to the row below.

When hPanel is fine but the website errors, something changed recently. Start there. (For slowness rather than errors, see the speed fixes.)

• Undo the last change. A plugin or theme update, an edit to .htaccess or wp-config.php, or a newly pasted snippet is the usual trigger. Revert it first.
• Switch off all plugins at once. Rename the plugins folder via SFTP or File Manager. If the site returns, rename it back and reactivate plugins one at a time until it breaks again.
• Restore a backup. In hPanel, Files, then Backups, restore the last working copy. Business and Cloud plans keep daily backups.
• Read the logs. hPanel's error logs name the failing file and line. That turns guessing into a fix.

A VPS is your machine. When it's "down", the usual story is a stopped service, a firewall rule that locked you out, or a server that needs a reboot. A Hostinger outage is the less likely explanation.

• SSH not answering: reboot the VPS from hPanel. It clears stuck processes and leaves your data alone.
• SSH refused: use the browser terminal in hPanel. A firewall rule or a changed SSH port is often the blocker.
• Site down, server up: check the web server and app are running, and restart them if not.
• Everything sluggish or dead: a full disk or an out-of-memory process takes a server down quietly. Check both.

Open a chat when the status page is green, you've ruled out your network, and your own checks haven't solved it. Also open one if there is an incident and you want updates on it.

Live chat is inside hPanel, 24/7. Have four things ready: the domain, the exact error text, when it started, and the last change you made. That gets you past the opening questions and onto the actual problem faster.

You can't stop a platform incident. You can make your own site less likely to fall over, and quicker to bring back when it does.

• Keep automatic backups on, and download one before any significant change.
• Test WordPress, theme and plugin updates on a staging copy, not on the live site.
• Stay inside your plan's resource limits; upgrade before you're hitting them every day.
• On a VPS, set up a firewall and automatic security updates so one bad night doesn't lock you out.