Try free

Actually online

Connected
isn't always working.

Five quiet checks every three seconds — two DNS resolvers, two public APIs, one round-trip here. When most pass, you're really online. When they don't, the wifi is lying.

Right now Grade F

DEAD

No probes responding. Captive portal, no peering, or no network.

Effectively offline. Reload + reconnect to wifi.

Session

Collecting first samples…

Recent

ms
median latency
Last 60s 0 / 20
Last 5m 0 / 100

Probes

  • DNS · Cloudflare (1.1.1.1)
    https://1.1.1.1/dns-query?name=example.com&type=A
  • DNS · Google (8.8.8.8)
    https://dns.google/resolve?name=example.com&type=A
  • HTTPS · Wikipedia
    https://en.wikipedia.org/api/rest_v1/page/summary/Internet
  • HTTPS · GitHub
    https://api.github.com/zen
  • Edge · this site
    /api/ping
Paused

Two DNS-over-HTTPS resolvers (Cloudflare 1.1.1.1 and Google 8.8.8.8), two public HTTPS endpoints, and a round-trip to this site. DNS probes pass when the resolver returns a valid address; HTTPS probes pass when the endpoint replies 200. Captive portals usually fail both — they break DNS resolution, and TLS-protected HTTPS handshakes can't be spoofed without trust warnings your browser would already have flagged.

A free tool by ComputeSphere — production PaaS for web apps and APIs.