Status checks spike.
You get a heads-up.

StatusGuard watches for unusual traffic through your status link and emails your team. Visitors continue to your existing status page. You get another signal that something may need attention.

Same visits. Different signal. Illustration
STATUS LINK TRAFFIC5-minute window
Illustrative traffic: 72 visits over five minutes, increasing toward the end of the window.
Total visits
72
Distinct IPs
31
Source networks
14

Example thresholds met

A broader wave of status checks qualifies for an email alert.

Example rule 48+ visits 10+ IPs 4+ networks

A small change to the link you already share

Keep your status page.
Give the link a new job.

No tracking script to install.
No status-page migration.

  1. 01 / CONNECT

    Set your destination.

    Add your existing public status-page URL in FraudGuard. Customers will still land on that page.

    Keep your provider and content
  2. 02 / CONFIGURE

    Choose when to hear about it.

    Set your traffic thresholds and email recipients, then enable StatusGuard to watch for qualifying surges.

    A heads-up for the people who respond
  3. 03 / SHARE

    Publish your StatusGuard link.

    Use your permanent redirect URL in your app, footer, or help center, wherever customers look for status.

    Each visit continues to your status page

Use your public URL from Statuspage, Better Stack, UptimeRobot, or your own status site.

See an example status page

Make the notification worth opening

A signal that fits
your audience.

Combine a recent traffic baseline with minimum visits, distinct IPs, and source networks. Use a cooldown to limit repeat notifications.

Give operations, support, or engineering another reason to check what customers may be experiencing.

Set up your alert rules

YOU CHOOSE THE SIGNAL

01

How much activity is unusual?

Choose a detection window, baseline multiplier, and minimum visit count.

02

How broad is the interest?

Require multiple source IPs and network groups so repeat refreshes alone do not tell the whole story.

03

Who needs the heads-up?

Pick email recipients and the minimum time between notifications.

Visit, IP, and network thresholds must all be met.

A few useful details

Before you change
your status link.

Open StatusGuard settings
Do we need to replace our status provider?

No. Point StatusGuard at your existing public status-page URL and share the redirect link. Only visits through that link are measured; direct visits to your status page are not counted.

Does a surge mean our service is down?

It means more activity is reaching your status link and your thresholds have been met. That is a reason to investigate, not proof of an outage. StatusGuard complements your uptime and application monitoring.

Does it count people or page refreshes?

StatusGuard counts visits, distinct IPs, and source-network groups. Those are traffic signals, not verified people. Refreshes increase visits, and automated requests can also count. IP and network minimums help distinguish a broader surge.

Where can notifications go?

Send email alerts to up to ten recipients, including shared operations or support inboxes. A Slack channel can receive them through its inbound email address, where that feature is available.

What visitor information is recorded?

StatusGuard records IP addresses, network groups, timestamps, and request details such as user agent and referrer. Review retention settings and your privacy requirements when configuring it.

Which plans include StatusGuard?

StatusGuard is included on Starter, Professional, Business, and Enterprise, and is available during an active trial. Compare plans or configure StatusGuard in your account.

Listen to the link customers already use

Make status checks
part of your signal.

Keep your page. Share your StatusGuard link.
Give your team a heads-up when interest surges.