Silent hours: when tracking or your site may have gone down
A run of silent hours usually means the site was down, the tracking snippet was removed or a deploy broke it.
Hours with no visits at all when 5 or more were expected, joined into runs, with runs of three hours or more flagged.
Why quietstats: you get this without cookies, a consent banner or storing IP addresses, in every plan including Free.
In every plan, including Free. Data in and out.
📘 Step-by-step guide, with screenshots and diagrams →
Start free, no cardSee live demo
- No cookies or consent banner
- No IP addresses stored
- Groups under 5 visitors hidden
- 845-byte script
- Free plan, no card


What it is
quietstats works out the average visits for each weekday and hour across the range, then lists past hours with none when 5 or more were expected. Neighbouring silent hours are joined into runs.
Why it matters
A run of silent hours usually means the site was down, the tracking snippet was removed or a deploy broke it. Spotting it quickly limits the gap in your data.
How it works
- Open your dashboard, go to Deep dives (or Reports on a phone) and open Analysis lab.
- Under Tools, tap Silent hours. You can also search for it on the All reports screen.
- Pick a date range (and any options at the top), read the “How to read this” notes, and download any table as CSV.
Privacy: what is and isn’t collected
Collected
- Nothing new: it reads the pageviews, events, goals or daily totals you already have
Never collected
- Anything about a single visitor
- Links between days: visitor ids still reset at midnight
- Cookies, localStorage or anything else stored on the visitor’s device
- IP addresses or user agents (used in memory, then discarded)
- Anything that links a visitor across days (the visitor ID resets daily)
Rows and limits
- Hours need 5 or more expected visits
- Today is left out
- Up to 92 days and 200,000 pageviews per screen
- Read from the database only when you open it, then kept for 10 minutes
“Rows” are database rows written, which is what our hosting is billed on. Reads are not rows written. Methodology →
Questions
Could a silent hour be real?
Yes, rarely: with 5 expected, a silent hour happens by chance less than 1 time in 100. Three in a row is very unlikely to be chance.
Does it store anything new?
No. It is worked out from the pageviews and events you already have when you open the screen, and only the totals are kept for 10 minutes.
Related features
Data in and outSite health: uptime, speed and Core Web Vitals in one card
See your trafficExcluded days: leave bad days out without deleting them
Data in and outSaved filters and segments
Data in and outExclusion preview: your numbers without one page or referrer
Data in and outCSV and Excel downloads
Data in and outBounce rate, three ways: one site, three definitions
Data in and outActive hours: how many hours a day you are busy
See your traffic
All data in and out features → · All features → · Docs: Silent hours guide → · Compare features with other tools →
Guides on this topic
Set it up
Nothing to set up: it works with the standard one-line script.
<script data-host="https://quietstats.co.uk" data-dnt="true" src="https://quietstats.co.uk/js/script.js" id="YOUR_SITE_ID" async defer></script>Try it on your own site
Free during launch: one site and 5,000 pageviews a month, no card needed. After launch, paid plans start at £5 a month.