Skip to main content

Ubiquiti SLA Monitoring Recommendations

This article explains why you should not use 8.8.8.8 and 1.1.1.1 as reachability probes on UniFi devices. Starting from version 9.x, you can configure custom SLA probes and specify your own targets.

Murray avatar
Written by Murray
Updated over a week ago

Overview

Ubiquiti UniFi gateways use SLA (Internet Verification) probes to determine WAN health and trigger failover events.


By default, UniFi relies on Google DNS (8.8.8.8) and Cloudflare DNS (1.1.1.1) for these checks.

While convenient, these addresses are not ideal for SLA monitoring, particularly 8.8.8.8, which is known to rate-limit or deprioritise ICMP (ping) traffic. This can result in:

  • False packet-loss alerts

  • Unnecessary WAN failovers

  • Apparent “instability” despite a healthy connection

And yet, we’re seeing extreme levels of ICMP traffic to 8.8.8.8 and 1.1.1.1 originating from our network. Why would a DNS server ever be a reliable ICMP probe? Imagine networks all over the world constantly hammering these addresses. We’re fortunate that Ubiquiti is generally considered an advanced platform - many other vendors would likely behave the same way, or worse.

The following UniFi default probes:

  • ping.ui.com (resolves to 1.1.1.1, 8.8.88 and ping2.ui.com)

  • ping2.ui.com (resolves to 8.8.8.8 and 1.1.1.1).

❯ dig ping2.ui.com ping.ui.com +short

8.8.8.8
1.1.1.1

Why 8.8.8.8 and 1.1.1.1 Are Not Reliable Probe Targets

ICMP Throttling

Public DNS services are not designed for continuous ICMP probing:

  • 8.8.8.8 (Google DNS) frequently rate-limits ICMP

  • 1.1.1.1 (Cloudflare DNS) is better, but still not guaranteed

Packet loss to these addresses does not indicate a fault with your connection. If your router marks the WAN unreachable based on the packet loss to these destinations it's incorrect behaviour that may severly affect your experience.

For example, in this thread on the NANOG mailing list a Google engineer responsible for the DNS infrastructure behind 8.8.8.8 and 8.8.4.4 explicitly stated that responding to pings to 8.8.8.8 is not a service they advertise, is not covered by any SLA, and should not be relied upon - it’s simply best-effort and may be dropped or throttled at any time.

Using them for SLA monitoring can cause:

  • False packet-loss alerts

  • Unnecessary WAN failovers

  • Apparent “instability” when the service is healthy

This behaviour can change at any time and is outside your ISP’s control.

Probe Frequency Matters

Even a good target can appear unreliable if probed too aggressively.

We recommend:

  • Low frequency (e.g. once per minute)

  • Small packet counts (3–5 ICMP packets)

High-frequency probing increases the chance of being rate-limited and can create unnecessary noise.

Reducing probe frequency often improves perceived connection stability, especially if your router uses SLA results to make routing decisions.

Use Custom Probes

UniFi Gateway allows custom Internet Verification settings. Please use this article from UniFi to configure custom SLA monitors.

You can use one of our probes to test ICMP.

Neptune POP probes in Australia (IPv4):

  • netbox-mel.neptune.net.au - VIC and TAS.

  • netbox-syd.neptune.net.au - NSW and ACT

  • netbox-bne.neptune.net.au - QLD

  • netbox-per.neptune.net.au - WA

  • netbox-adl.neptune.net.au - SA and NT

Neptune POP probes in Australia (IPv6):

  • netbox-mel.ipv6.neptune.net.au

  • netbox-syd.ipv6.neptune.net.au

  • netbox-bne.ipv6.neptune.net.au

  • netbox-per.ipv6.neptune.net.au

  • netbox-adl.ipv6.neptune.net.au

Overseas Probes that you can use to test international latency.

IPv4 addresses

  • probe1.ams.neptune.net.au

  • probe1.sin.neptune.net.au

  • probe1.hnd.neptune.net.au

  • probe1.jfk.neptune.net.au

  • probe1.lax.neptune.net.au

  • probe1.lhr.neptune.net.au

  • probe1.ord.neptune.net.au

IPv6 addresses

  • probe1.ams.ipv6.neptune.net.au

  • probe1.hnd.ipv6.neptune.net.au

  • probe1.jfk.ipv6.neptune.net.au

  • probe1.lax.ipv6.neptune.net.au

  • probe1.lhr.ipv6.neptune.net.au

  • probe1.ord.ipv6.neptune.net.au

  • probe1.sin.ipv6.neptune.net.au

Did this answer your question?