BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
2402:6020::/32
Announced exactly
- 2402:6020::/32AS212259Astrix Co., Ltd.RPKI Valid2402:6020::
- Registry
- APNIC · Japan · May 27, 2026
- Delegated block
- 2402:6020:: – 2402:6020:ffff:ffff:ffff:ffff:ffff:ffff
Covering routes
No less-specific route covers it.
More-specific routes
- 2402:6020::/36AS212259Astrix Co., Ltd.RPKI Valid2402:6020::
- 2402:6020:e0::/48AS212259Astrix Co., Ltd.RPKI Valid2402:6020:e0::
- 2402:6020:e1::/48AS212259Astrix Co., Ltd.RPKI Valid2402:6020:e1::
- 2402:6020:e2::/48AS36530IDC CubeRPKI Valid2402:6020:e2::
- 2402:6020:f0::/44AS212259Astrix Co., Ltd.RPKI Valid2402:6020:f0::
- 2402:6020:1000::/36AS212259Astrix Co., Ltd.RPKI Valid2402:6020:1000::
- 2402:6020:2000::/36AS212259Astrix Co., Ltd.RPKI Valid2402:6020:2000::
- 2402:6020:3000::/36AS212259Astrix Co., Ltd.RPKI Valid2402:6020:3000::
- 2402:6020:4000::/36AS212259Astrix Co., Ltd.RPKI Valid2402:6020:4000::
- 2402:6020:5000::/36AS212259Astrix Co., Ltd.RPKI Valid2402:6020:5000::
- 2402:6020:6000::/36AS212259Astrix Co., Ltd.RPKI Valid2402:6020:6000::
- 2402:6020:7000::/36AS212259Astrix Co., Ltd.RPKI Valid2402:6020:7000::
- 2402:6020:8000::/36AS212259Astrix Co., Ltd.RPKI Valid2402:6020:8000::
- 2402:6020:9000::/36AS212259Astrix Co., Ltd.RPKI Valid2402:6020:9000::
- 2402:6020:a000::/36AS212259Astrix Co., Ltd.RPKI Valid2402:6020:a000::
- 2402:6020:b000::/36AS212259Astrix Co., Ltd.RPKI Valid2402:6020:b000::
- 2402:6020:c000::/36AS212259Astrix Co., Ltd.RPKI Valid2402:6020:c000::
- 2402:6020:d000::/36AS212259Astrix Co., Ltd.RPKI Valid2402:6020:d000::
- 2402:6020:e000::/36AS212259Astrix Co., Ltd.RPKI Valid2402:6020:e000::
- 2402:6020:f000::/36AS212259Astrix Co., Ltd.RPKI Valid2402:6020:f000::
On the internet, routes are announced as prefixes: an autonomous system tells its neighbours via BGP that it can deliver traffic for, say, 62.103.0.0/16. This tool looks a prefix up in our daily copy of the global routing table and shows three things:
- Exact announcements: which AS originates exactly this prefix. More than one origin (a MOAS) is normal for anycast services and some multihomed networks, and suspicious otherwise.
- Covering routes: less-specific announcements that contain it. Traffic follows the most specific route, so a covering route matters if the more-specific one disappears.
- More-specifics: announcements inside it, which may belong to other networks (customers, or a hijack).
Each announced route is also checked against the RPKI: whether a ROA authorises its origin AS.
The table is the view from APNIC’s route collector. Most of the global table is the same from everywhere, but a route that is filtered before it reaches that collector will not appear.
Frequently asked questions
Why is my /24 not listed but a /16 is?
Your addresses are announced as part of the larger block, and no one announces the /24 separately. That is the normal case for most customers of a provider.
What is a more-specific hijack?
Someone announces a longer prefix inside your space. Because routers prefer the most specific route, traffic goes to them. RPKI with a strict max length makes such announcements invalid.
Can I enter a single address?
Yes. The tool then shows the most specific announced route that contains it.