Metro Atlanta business network check
Ready
—
Mbps
Ready when you are.
Run a same-origin Cloudflare edge test to understand real-world browser performance.
Length
- Latency Ready
- Download Waiting
- Upload Waiting
- Quality Waiting
Starting test…
Measuring download, upload, latency, jitter, bufferbloat, and probe loss.
This connection may need attention — Conquest can help evaluate circuits and QoS.
Takes about 20–40 seconds and transfers about 45 MB on a full test (less in Quick). Keep this tab active for the cleanest latency reading. Results are calculated in your browser. A pseudonymous usage summary (metrics + edge location; optional label you type) may be logged to improve the tool — never a full IP.
- Unloaded
- —
- During download
- —
- During upload
- —
- Download jitter
- —
- Upload jitter
- —
- Sample count
- 0
Estimates from this browser’s path to the nearest Cloudflare edge — a proxy for general internet quality, not a certification of 3CX, cameras, access control, LPR, or life-safety circuits. This site cannot reach your router for a pure LAN test; re-run on Ethernet to reduce Wi‑Fi’s contribution (LAN/router still remain). Power, QoS, and carrier configs are not tested.
Run the test to see how this connection may support Hosted VOIP, cameras, managed IT, and other Conquest services.
— — —
Your location approx. from public IP
Protocol reachability best-effort browser check
IPv4: Checking…
IPv6: Checking…
RPKI: Checking…
DownloadHigher is better. Impacts cloud downloads, large files, streaming, and app updates. Multi-stream on large sizes.
UploadHigher is better. Impacts Teams/Zoom video, backups, VoIP media, and sending large files.
LatencyLower is better. Under 30 ms feels instant; over 100 ms feels laggy for calls and remote apps.
JitterLower is better. Under 10 ms is clean; high jitter causes choppy voice/video.
BufferbloatLoaded latency minus unloaded. Under 20 ms is good; scores drop hard just above 50 ms. Over 100 ms means heavy queuing under load. Shown to 0.1 ms under 100 so cliffs stay visible.
Wi‑Fi vs EthernetWireless adds latency and bufferbloat that this test cannot remove. Re-run on Ethernet to reduce Wi‑Fi’s contribution — browsers cannot force a LAN-only path to your router, and wired still includes LAN/router hops.
Probe loss0% is best. Any repeated loss usually means Wi-Fi, ISP, firewall, or circuit trouble. Not true UDP packet loss.
Need better business connectivity?