BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
2001:4430:4000::/36
Announced exactly
- 2001:4430:4000::/36AS17853LGTELECOMRPKI Not found2001:4430:4000::
- Registry
- APNIC · South Korea · Jul 6, 2005
- Delegated block
- 2001:4430:: – 2001:4430:ffff:ffff:ffff:ffff:ffff:ffff
Covering routes
No less-specific route covers it.
More-specific routes
- 2001:4430:4020::/44AS17853LGTELECOMRPKI Not found2001:4430:4020::
- 2001:4430:4030::/44AS17853LGTELECOMRPKI Not found2001:4430:4030::
- 2001:4430:4060::/44AS17853LGTELECOMRPKI Not found2001:4430:4060::
- 2001:4430:4070::/44AS17853LGTELECOMRPKI Not found2001:4430:4070::
- 2001:4430:4080::/44AS17853LGTELECOMRPKI Not found2001:4430:4080::
- 2001:4430:4090::/44AS17853LGTELECOMRPKI Not found2001:4430:4090::
- 2001:4430:40a0::/44AS17853LGTELECOMRPKI Not found2001:4430:40a0::
- 2001:4430:40b0::/44AS17853LGTELECOMRPKI Not found2001:4430:40b0::
- 2001:4430:40c0::/44AS17853LGTELECOMRPKI Not found2001:4430:40c0::
- 2001:4430:40d0::/44AS17853LGTELECOMRPKI Not found2001:4430:40d0::
- 2001:4430:40e0::/44AS17853LGTELECOMRPKI Not found2001:4430:40e0::
- 2001:4430:40f0::/45AS17853LGTELECOMRPKI Not found2001:4430:40f0::
- 2001:4430:40f8::/45AS17853LGTELECOMRPKI Not found2001:4430:40f8::
- 2001:4430:4100::/45AS17853LGTELECOMRPKI Not found2001:4430:4100::
- 2001:4430:4108::/45AS17853LGTELECOMRPKI Not found2001:4430:4108::
- 2001:4430:4110::/45AS17853LGTELECOMRPKI Not found2001:4430:4110::
- 2001:4430:4120::/45AS17853LGTELECOMRPKI Not found2001:4430:4120::
- 2001:4430:4130::/45AS17853LGTELECOMRPKI Not found2001:4430:4130::
- 2001:4430:4138::/45AS17853LGTELECOMRPKI Not found2001:4430:4138::
- 2001:4430:4140::/45AS17853LGTELECOMRPKI Not found2001:4430:4140::
- 2001:4430:4148::/45AS17853LGTELECOMRPKI Not found2001:4430:4148::
- 2001:4430:4150::/45AS17853LGTELECOMRPKI Not found2001:4430:4150::
- 2001:4430:4158::/45AS17853LGTELECOMRPKI Not found2001:4430:4158::
- 2001:4430:4160::/44AS17853LGTELECOMRPKI Not found2001:4430:4160::
- 2001:4430:4170::/44AS17853LGTELECOMRPKI Not found2001:4430:4170::
- 2001:4430:4180::/44AS17853LGTELECOMRPKI Not found2001:4430:4180::
- 2001:4430:4190::/44AS17853LGTELECOMRPKI Not found2001:4430:4190::
- 2001:4430:41a0::/44AS17853LGTELECOMRPKI Not found2001:4430:41a0::
- 2001:4430:41b0::/44AS17853LGTELECOMRPKI Not found2001:4430:41b0::
- 2001:4430:41c0::/44AS17853LGTELECOMRPKI Not found2001:4430:41c0::
- 2001:4430:41d0::/45AS17853LGTELECOMRPKI Not found2001:4430:41d0::
- 2001:4430:41d8::/45AS17853LGTELECOMRPKI Not found2001:4430:41d8::
- 2001:4430:41e0::/45AS17853LGTELECOMRPKI Not found2001:4430:41e0::
- 2001:4430:4f00::/45AS17853LGTELECOMRPKI Not found2001:4430:4f00::
On the internet, routes are announced as prefixes: an autonomous system tells its neighbours via BGP that it can deliver traffic for, say, 2.48.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.