How to Set Up Separate IPv4 and IPv6 Uptime Checks (Step-by-Step Guide)

Setting up dual-stack monitoring — for both IPv4 and IPv6 — helps you detect issues invisible to traditional checks. In this quick guide, we’ll show you how to configure separate uptime monitors in UptyBots to make sure both protocols stay healthy.

1. Why Separate Monitors?

IPv4 and IPv6 use different network paths, DNS records, and in some cases — even separate SSL bindings. A single issue (like a missing AAAA record or IPv6 routing problem) can make your site unreachable for part of your audience without you realizing it.

That’s why UptyBots allows separate checks per protocol — you’ll instantly know if one path fails while the other stays up.

2. Verify Your DNS Setup

Before creating monitors, ensure your domain has both A and AAAA records:

example.com.   IN   A     192.0.2.45
example.com.   IN   AAAA  2001:db8::45
  

If you’re missing the AAAA record, your domain isn’t reachable via IPv6. You can check this using:

• dig example.com A and dig example.com AAAA
• Online tools like DNSChecker

3. Create an IPv4 Monitor

1. In your UptyBots dashboard, click “New Monitor”.
2. Enter your target domain, e.g. example.com.
3. Under Network Type, select IPv4.
4. Choose your protocol (HTTP, Ping, TCP, etc.).
5. Set your check interval and regions.
6. Click Save.

The system will immediately start sending uptime checks over IPv4 and display your first results in seconds.

4. Duplicate for IPv6

Instead of creating a new one from scratch, you can duplicate your IPv4 monitor:

1. Open your IPv4 monitor settings.
2. Click “Duplicate Monitor”.
3. Change the Network Type to IPv6.
4. Save changes — done!

Now UptyBots will test both network stacks independently, recording uptime, latency, and alerts for each.

5. Compare Results

You can view both monitors side by side in your dashboard. In many cases, IPv6 may show slightly higher latency or different response behavior — especially if routed via another provider or CDN node.

For quick insights, use tags like ipv4 and ipv6 to group related monitors or build custom views.

6. Set Alerts for Each Protocol

Alerts are sent separately for each monitor, so if IPv6 fails but IPv4 remains up, you’ll know exactly which one caused the issue.

Notifications can be delivered via Email, Telegram, or Webhooks — configure them under your Notification Channels settings.

7. Best Practice Summary

• ✅ Always monitor both IPv4 and IPv6 individually
• ✅ Use clear naming (e.g. “Main Site – IPv4”, “Main Site – IPv6”)
• ✅ Keep both in the same project for unified reporting
• ✅ Review latency graphs to detect routing differences

With dual-stack monitoring, you’ll never miss hidden outages that only affect part of your audience.

See more setup tutorials or get started with dual monitoring today.