What should you record first?
Record the target IP, matching prefix, ASN, organization field, sources, and query time. For a domain, also keep the A and AAAA answers returned by that query.
NETWORK GUIDE
The site helps identify the prefix and ASN for an address, then exposes peers, upstreams, and downstreams. It does not run traceroute, MTR, latency, or packet-loss tests from the browser.
This guide explains public network concepts. Routes, ownership records, and Geo data can change; verify time-sensitive decisions with the source or network operator.
Guide category
Understand ASNs, BGP prefixes, network relationships, route observations, and troubleshooting methods.
Record the target IP, matching prefix, ASN, organization field, sources, and query time. For a domain, also keep the A and AAAA answers returned by that query.
Prefixes and ASN relationships describe public control-plane context. Forward and return paths still vary with location, carrier policy, and time.
Run traceroute or MTR from an affected network, check forward and return paths across several time windows, and compare the observed ASNs with the prefix data shown here.
View Geo, ISP, ASN, BGP prefix, source labels, and query time for 8.8.8.8 · Google Public DNS.
View the address's Geo estimate, ISP, ASN, BGP prefix, sources, and query time.
View the resolver address's Geo estimate, ISP, ASN, BGP prefix, sources, and query time.
View the resolver address's Geo estimate, ISP, ASN, BGP prefix, sources, and query time.
View prefixes, peers, upstreams, and downstreams for AS15169 · Google.
Review Cloudflare network organization fields, prefixes, peers, upstreams, and downstreams.
Review Microsoft network organization fields, prefixes, peers, upstreams, and downstreams.
Review Amazon network organization fields, prefixes, peers, upstreams, and downstreams.
Compare common public resolvers by IP, Geo estimate, ISP, ASN, and BGP prefix, with clear limits for each public field.
Explain why CDN and Anycast addresses can receive different Geo labels and use ASN plus BGP prefixes to interpret edge networks.
Explain why IP Geo databases can disagree on a city or country and how ASN, BGP prefix, source, and query time frame the estimate.
Compare representative cloud and edge networks by ASN, announced prefixes, peers, upstreams, and downstreams without inferring a specific host or customer workload.
Record the relevant IP, ASN, BGP prefix, source labels, and query time first. Verify claims about DNS behavior, network operators, or product capabilities against current operator documentation or the relevant registry.
No. Geolocation, organization labels, and a single route observation all have source and time limits. They cannot independently prove a precise physical location, final provider, security status, or long-term performance.
Repeat the check from another network or time window, compare the related IP and ASN pages, and confirm service-level claims against the operator's current documentation.