How to Check Website Downtime With Hourly Traffic Stats (2026)

Want to know if your website was down while you were asleep? Your own traffic statistics can tell you. When a site goes offline, visits drop to zero for that hour and then bounce back once the server recovers, so an hourly traffic chart is a simple way to check website downtime after the fact. This guide shows how to spot outages in Google Analytics 4 and Search Console, and how to add a free uptime monitor so you hear about the next one in minutes, not the next morning.

Quick answer: To check website downtime after it happened, open an hourly view of your traffic (in GA4, an Exploration with the Date + hour dimension) and look for hours that suddenly drop to zero. Confirm with Search Console’s Crawl stats host status and your host’s status page. To catch the next outage live, set up a free uptime monitor such as UptimeRobot or Jetpack’s downtime monitoring.

Why hourly traffic reveals downtime

Daily totals hide short outages: a site that was down for three hours at night may only show a slightly lower day. Hourly data doesn’t. A normal site has a smooth daily curve, rising in the morning and falling at night. An outage shows up as a hole in that curve: one or more hours at or near zero, followed by a jump back to normal levels. A partial drop, where traffic halves rather than vanishes, usually points to slow pages, errors on some URLs or a problem in one region.

It also explains other odd numbers. If your ad impressions or earnings dipped on a day, an hour of downtime is one of the first things to rule out.

How to check website downtime in Google Analytics 4

1. Open Google Analytics and go to Explore, then start a Free form exploration.
2. Add the dimension Date + hour (YYYYMMDDHH) and the metric Sessions or Views.
3. Pick the date range you’re worried about and switch the visualisation to a line chart.
4. Look for hours that fall to zero and then recover. Note the times and compare them with your host’s status page or support tickets.

For a live check, the Realtime report shows activity in the last 30 minutes. If it is empty at a time you normally have visitors, open your site in a private window to see if it loads.

Two cautions. Analytics only records visits from pages that load the tracking code, so it can’t tell an outage apart from a broken tag or a consent banner that blocks tracking. And a quiet small site may have genuine zero-visit hours at night, so compare with the same hour on other days.

Other places to confirm an outage

• Google Search Console: Settings > Crawl stats shows host status. Problems with server connectivity, DNS or robots.txt fetching are flagged there, which tells you Googlebot also had trouble reaching the site.
• Server logs: your hosting control panel’s access and error logs show exactly when requests stopped or returned 500/503 errors.
• Your host’s status page: most hosts publish planned maintenance and incidents.
• Other stats tools: StatCounter and similar tools also offer hourly views if you run them alongside GA4.

Set up a free uptime monitor

Traffic charts tell you what already happened. An uptime monitor checks your site every few minutes from outside and alerts you by email or app the moment it stops responding.

• UptimeRobot: a popular monitor with a free plan for basic HTTP checks and email alerts (check its terms if your site is a business).
• Jetpack: WordPress sites can switch on downtime monitoring from the Jetpack settings and get an email when the site goes down and comes back.
• Better Stack: uptime monitoring with a free tier and public status pages.

We compare more tools, and share what three years of monitoring showed us, in our website uptime monitoring guide. If you are judging a host, see how to check hosting uptime yourself.

What to do when you spot downtime

1. Write down the start and end times from your charts or monitor.
2. Check the host’s status page, then open a support ticket with those times and ask for the cause.
3. Look for a pattern: the same hour every night may be a backup or cron job; outages during traffic spikes mean the server is running out of resources.
4. Turn on page caching and a CDN so pages can still be served during traffic spikes.
5. If outages keep happening, compare your real uptime with the host’s guarantee and consider moving.

What changed since 2006

When we wrote this in 2006, we spotted outages in Sitemeter’s hourly charts: one showed the site going offline at 3 AM and returning around 7 AM, another a power outage at the host, and a third the day our shared server crashed under a wave of Digg traffic. Sitemeter has since shut down, and analytics moved to GA4, but the idea still works. The big change is that free uptime monitors now alert you in minutes, so hourly charts are best used to confirm and measure an outage rather than to discover it.

FAQ

How can I tell if my website was down yesterday?

Look at an hourly traffic chart for that day in GA4 and compare it with a normal day. Hours at zero followed by a quick recovery suggest downtime. Confirm with your host’s logs or status page.

Does Google Analytics show downtime directly?

No. It only shows missing visits. A gap can also come from a broken tracking tag, so use server logs, Search Console or an uptime monitor to confirm.

How often should an uptime monitor check my site?

Every 5 minutes is fine for most blogs and small business sites. Online shops and busy services often pay for 1-minute checks.

Does short downtime hurt SEO?

Brief outages are normal and Google retries later. Long or frequent downtime can slow crawling and, if pages keep failing, may cause them to drop from results, so fix repeated outages quickly.