A BGPView alternative for AS and prefix lookups
BGPView.io shut down on 26 November 2025. If you used it to find out who announces a prefix or what an AS announces, you can look both up here, and each answer comes with a map of the AS paths.
What carries over
| BGPView had | On BGP Map |
|---|---|
| AS page with the IPv4 and IPv6 prefixes it announces | Yes, for example AS13335. The 200 largest of each family are listed, with a map of the largest one. |
| Prefix page with the origin AS | Yes, for example 1.1.1.0/24, with every AS path the RIS peers use and the upstream and transit networks on them. |
| IP address lookup | Yes. Search for 8.8.8.8 and you get the map of the prefix that covers it. |
| Upstreams | Yes, per prefix, with the share of peers whose path goes through each one. |
| Downstreams and peers | No. bgp.tools lists both. |
| Internet exchange presence | No. PeeringDB has it. |
| Whois and registration data | No. RIPEstat shows it for any address or AS. |
| Search by network name | No. The search box takes a prefix, an IP address, an AS number or a hostname. |
| API | In part. /json/<prefix> returns the paths and the graph for one prefix. For more, the RIPEstat Data API is open to everyone. |
Old BGPView links
Change the domain and keep the rest of the address. bgpmap.top/asn/13335, bgpmap.top/prefix/1.1.1.0/24 and bgpmap.top/ip/1.1.1.1 each lead to the matching page here, so bookmarks, scripts that open a browser and links on wiki pages need a one-word edit.
If you called the BGPView API
BGPView's API is gone along with the site, and BGP Map has no equivalent for most of it. The RIPEstat Data API, which BGP Map itself reads, covers the same questions and needs no key. The closest matches are these.
| You asked BGPView for | Closest RIPEstat call |
|---|---|
| An AS: name, holder, contacts | as-overview |
| The prefixes an AS announces | announced-prefixes |
| Upstreams, downstreams and peers of an AS | asn-neighbours (what the collectors see, so incomplete for peers) |
| An IP address or a prefix: origin and holder | prefix-overview |
| Whether a prefix is visible and from how many places | routing-status |
| RPKI status of a route | rpki-validation |
Each one is called as https://stat.ripe.net/data/<name>/data.json?resource=<AS or prefix>. The documentation lists the parameters. For one prefix with its paths already drawn, /json/<prefix> on this site is shorter.
Other tools worth knowing
- bgp.tools for peers, downstreams and a searchable list of networks.
- Hurricane Electric's BGP Toolkit for a long-standing AS and prefix lookup with peer graphs.
- RIPEstat for registration data, RPKI status and the BGPlay history widget.
- PeeringDB for exchange points, facilities and how a network peers.
What this site adds is the picture: every AS path to one prefix in a single drawing, with the best path marked. If a lookup is all you need, any of the tools above will do. If the question is who the traffic goes through, the map answers it faster than a table. The guides explain how to read it, how to spot a hijack and how a map differs from a looking glass or a traceroute.
Why the numbers can differ
Every route here comes from RIPE RIS through RIPEstat, so prefix and upstream counts will not always match what BGPView showed for the same network. A route appears once it reaches at least one RIS collector, and an AS page lists what the AS announced in the last two weeks. More about the data.