Your monitors tell you when something broke. Status page analytics tell you who noticed. A three-minute blip at night with ten visits is a footnote. The same blip at 10:00 with 4,812 visits from Sweden and Germany in forty minutes is something your support and account teams need to know about.
Analytics are built into every Uptimecheck status page.
What you can see
- Visits per day over the last 30 days, so you can line traffic up with the incident.
- Countries: where your visitors are.
- Referrers: your app, an incident email, a social post or a search engine.
- UTM source: which tagged link brought people in.
- Devices and browsers: what people check the page on.
How teams use it
Support
Compare status page visits to ticket volume. If thousands checked the page and fifty wrote in, the page did its job. If visits are low and tickets are high, customers are not finding the page; link it from your app and help center, or add the status widget to your site.
Agencies
Show a client how many of their customers checked the status page during an outage, and from which markets. It turns a vague “some people noticed” into a number you can discuss.
Product and marketing
Tag the link in your incident emails with a UTM source and see how many people followed it. Plan communication for the countries and devices that actually check your page.
A real picture of the incident
Combine status page analytics with your monitoring data and the incident timeline. You know when it broke, how long it lasted from your uptime checks, and how many people were affected enough to look. The incident review you write afterwards is better for it.
Privacy and data
Visits are counted without cookies and without storing IP addresses. The country is looked up when the page is visited, and each visit is kept only as its time, country, referrer, UTM tags, device and browser. The Uptimecheck app and its database are hosted in Stockholm, Sweden, and backups are kept in Stockholm and in the EU, so the data stays in the EU.
After the incident
When you write the incident review, include the numbers: how long it lasted, how many people checked the status page, and from which markets. It makes the review concrete, helps decide whether customers need a personal follow-up, and shows the value of having the page in the first place. Over time, the visit patterns also tell you which incidents your customers really notice and which go by unseen.
Spot the incidents customers notice
Some incidents pass without a single visit to the status page; others bring thousands. Comparing the two helps you decide where to invest in redundancy, and which components deserve the clearest names and the fastest updates.
Status pages with analytics are included on every plan. Plans start at €9 per month billed yearly or €12 billed monthly, excl. VAT; see the pricing page for status page limits, or start a 14-day free trial without a card. Read how to create a status page to set one up.