If your Hostinger site just went down, the fastest honest answer is one URL: statuspage.hostinger.com. It lists live incidents, emergency maintenance and scheduled maintenance for every Hostinger service, with each update timestamped in UTC. If nothing is listed there, the problem is almost certainly on your side of the connection, not the server’s, and the checks below will tell you which.
What the Hostinger status page actually shows
The status page is Hostinger’s own incident board. It has three things worth knowing about before you rely on it during an outage:
| What you see | What it means |
|---|---|
| Current service status | The headline state of Hostinger’s services, separate from your individual account. |
| Ongoing incidents | An active problem. Each incident page lists every update in order, with the time each update was posted. |
| Upcoming maintenance | Scheduled windows with a planned start and end time, shown in UTC. |
Two practical consequences follow from that design. First, everything is timestamped in UTC, so convert before you conclude “this has been going on for hours” — a 09:00 UTC update is 14:30 in India and 04:00 in New York. Second, the page covers all Hostinger services, not just the ones in your account, so a red banner does not automatically mean your specific plan is affected.
Subscribe with RSS or Atom — there is no email or SMS option
Hostinger’s status page does not offer email or text message subscriptions. The supported way to get pushed updates is a feed reader, and both feed formats are published:
| Feed | URL |
|---|---|
| RSS | https://statuspage.hostinger.com/history.rss |
| Atom | https://statuspage.hostinger.com/history.atom |
To subscribe, open the status page, click Subscribe to Updates, and select the RSS icon to copy either feed link. Paste it into any app that reads RSS — a feed reader or a browser extension. Opening a feed URL directly in a browser shows raw XML, which looks broken but is not; it needs a feed reader to render.
The feed carries incidents, emergency maintenance and scheduled maintenance for all Hostinger services. Entry titles name what is affected — a region, a server, a domain registry or a specific service — so “Scheduled maintenance in Europe” is a different event from a registry-side problem at Verisign. That distinction matters when you are deciding whether to email a client.
If you would rather not run a feed reader: Hostinger’s hosting plans come with 24/7 support — on the current promotion Premium is $1.99/mo on a 48-month term, and every hosting plan is inside a 30-day money-back guarantee, so a plan that does not work out is refundable rather than a loss. If you are still deciding between tiers, the Hostinger plan comparison lays out what each tier actually includes.
Five checks that tell you whether it is Hostinger or you
Work down this list in order. Each step removes one possible cause, and most outages are resolved by step three.
- Read the status page. An open incident that names your region or service is your answer. Wait for the next update rather than opening a ticket, because support will tell you the same thing the incident page already says.
- Try a second site on the same hosting plan. If both are down, the problem is the plan or the server. If only one is down, it is that site — a plugin, a PHP fatal error, or a database problem.
- Test the domain instead of the site. A DNS lookup of your domain tells you whether the domain still resolves. If DNS resolves but the site does not load, hosting is the suspect. If DNS does not resolve, the problem may be the registrar or an expired domain, and no amount of server-side debugging will fix it.
- Load the site from a different network. A phone on mobile data is enough. If it loads there and not on your office Wi-Fi, the issue is your local network, router or ISP — not Hostinger.
- Check whether you can reach the dashboard. If hPanel loads and the site does not, you have a per-site problem and can start looking at error logs and plugins. If the dashboard itself rejects you, that is a different failure — the steps in Hostinger login troubleshooting cover it. If nothing Hostinger-related loads, stop debugging the site.
What to do when the status page is green but your site is down
A green status page is information, not a denial. It tells you Hostinger’s platform has no known incident; it cannot know that one of your plugins pushed a fatal error. On a shared plan the most common causes are, in rough order of frequency:
| Symptom | Usual cause | Where to look |
|---|---|---|
| White screen or HTTP 500 | A PHP fatal error from a plugin or theme update | Error log for the site, then deactivate the most recently updated plugin |
| “Error establishing a database connection” | Wrong database credentials or a database service problem | wp-config.php credentials, then support if they are unchanged |
| Site loads for some visitors only | DNS propagation after a nameserver or record change | Propagation can take up to 24 hours after a DNS change |
| Login page redirects or 404s | A security plugin changed the wp-admin URL | Plugin settings, or the WordPress login URL guide |
If the site returns a database error and you have not touched wp-config.php, that is the point to contact support rather than keep editing. Changing credentials to “try something” turns a five-minute fix into a longer outage. If the failure turns out to be a login problem rather than a server problem, finding your WordPress login URL on Hostinger is the shorter path than reinstalling anything.
What to put in a support ticket so it gets solved in one reply
Hostinger’s support is advertised as 24/7, and the difference between a one-reply fix and a five-reply thread is the information you include up front. Send:
- The exact URL that fails, and the HTTP status it returns.
- When it started, with a timezone — not “this morning”.
- The exact error text, copied, not paraphrased. “500 Internal Server Error” and “Error establishing a database connection” are different incidents.
- The last thing that changed on your side: a plugin update, a theme switch, a DNS record edit, a PHP version change.
- What you already ruled out — other sites on the plan, a different network, the status page.
That last item is why the five checks above are worth doing before you write the ticket. It also makes the ticket harder to close with “please clear your cache”.
Building the site that has to stay up? Hostinger’s current hosting plans start at $1.99/mo for Premium on a 48-month term ($95.52 up front, renewing at $10.99/mo), and the 30-day money-back guarantee applies to the hosting plans and to the KVM VPS line.
Frequently asked questions
Where is the official Hostinger status page?
At statuspage.hostinger.com. It is linked from Hostinger’s own site under System status, and it lists live incidents, emergency maintenance and scheduled maintenance with UTC timestamps for all Hostinger services rather than only the ones attached to your account.
Can I get an email when Hostinger has an outage?
No. Hostinger’s status page supports RSS and Atom feeds only — there is no email or SMS subscription. To get pushed updates you need a feed reader or a browser extension that reads feeds, subscribed to https://statuspage.hostinger.com/history.rss or the Atom equivalent.
My site is down but the status page shows no incident. What now?
Assume it is site-specific. Check a second site on the same plan, look up your domain’s DNS, then read the site’s error log. A fatal error from a plugin update is the single most common cause of a site-only outage, and it will never appear on an infrastructure status page.
How long do Hostinger maintenance windows last?
Each scheduled maintenance entry states its own planned start and end time in UTC, so read the specific entry rather than assuming a standard window. During a maintenance window the status page is the authoritative source for what is expected to be unavailable.
Do incidents stay on the status page after they are fixed?
Yes — the feed carries incident history as well as live events, which is useful when a client asks what happened last week. Each entry keeps its full update log rather than being deleted once resolved.
Save the status page bookmark next to your dashboard login, because the two questions you will actually ask during an outage are “is it them?” and “can I still get in?” — and a feed subscription answers the first one before you think to check.
