BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
2404:8d02:2000::/36
Announced exactly
- 2404:8d02:2000::/36AS958726th Floor 333/3 Moo 14 Chai BuildingRPKI Valid2404:8d02:2000::
- Registry
- APNIC · Thailand · Dec 29, 2015
- Delegated block
- 2404:8d02:: – 2404:8d03:ffff:ffff:ffff:ffff:ffff:ffff
Covering routes
- 2404:8d02::/32AS958726th Floor 333/3 Moo 14 Chai BuildingRPKI Valid2404:8d02::
More-specific routes
- 2404:8d02:2020::/48AS958726th Floor 333/3 Moo 14 Chai BuildingRPKI Valid2404:8d02:2020::
- 2404:8d02:2021::/48AS958726th Floor 333/3 Moo 14 Chai BuildingRPKI Valid2404:8d02:2021::
- 2404:8d02:2040::/48AS958726th Floor 333/3 Moo 14 Chai BuildingRPKI Valid2404:8d02:2040::
- 2404:8d02:20a6::/48AS958726th Floor 333/3 Moo 14 Chai BuildingRPKI Valid2404:8d02:20a6::
- 2404:8d02:2641::/48AS958726th Floor 333/3 Moo 14 Chai BuildingRPKI Valid2404:8d02:2641::
- 2404:8d02:2801::/48AS958726th Floor 333/3 Moo 14 Chai BuildingRPKI Valid2404:8d02:2801::
- 2404:8d02:28c5::/48AS958726th Floor 333/3 Moo 14 Chai BuildingRPKI Valid2404:8d02:28c5::
- 2404:8d02:28c8::/48AS24429Zhejiang Taobao Network Co.,LtdRPKI Valid2404:8d02:28c8::
- 2404:8d02:2982::/48AS958726th Floor 333/3 Moo 14 Chai BuildingRPKI Valid2404:8d02:2982::
- 2404:8d02:29c0::/48AS958726th Floor 333/3 Moo 14 Chai BuildingRPKI Valid2404:8d02:29c0::
- 2404:8d02:29c1::/48AS958726th Floor 333/3 Moo 14 Chai BuildingRPKI Valid2404:8d02:29c1::
- 2404:8d02:29c2::/48AS958726th Floor 333/3 Moo 14 Chai BuildingRPKI Valid2404:8d02:29c2::
- 2404:8d02:29c3::/48AS958726th Floor 333/3 Moo 14 Chai BuildingRPKI Valid2404:8d02:29c3::
- 2404:8d02:29c5::/48AS958726th Floor 333/3 Moo 14 Chai BuildingRPKI Valid2404:8d02:29c5::
- 2404:8d02:29c6::/48AS958726th Floor 333/3 Moo 14 Chai BuildingRPKI Valid2404:8d02:29c6::
- 2404:8d02:29c7::/48AS958726th Floor 333/3 Moo 14 Chai BuildingRPKI Valid2404:8d02:29c7::
On the internet, routes are announced as prefixes: an autonomous system tells its neighbours via BGP that it can deliver traffic for, say, 49.224.0.0/14. 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.