BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
2a02:2668::/32
Announced exactly
- 2a02:2668::/32AS16345PJSC "Vimpelcom"RPKI Not found2a02:2668::
- Registry
- RIPE NCC · Russia · Oct 18, 2010
- Delegated block
- 2a02:2668:: – 2a02:2668:ffff:ffff:ffff:ffff:ffff:ffff
Covering routes
No less-specific route covers it.
More-specific routes
- 2a02:2668:3900::/40AS16345PJSC "Vimpelcom"RPKI Not found2a02:2668:3900::
- 2a02:2668:6100::/40AS16345PJSC "Vimpelcom"RPKI Not found2a02:2668:6100::
- 2a02:2668:6600::/40AS16345PJSC "Vimpelcom"RPKI Not found2a02:2668:6600::
- 2a02:2668:7400::/44AS16345PJSC "Vimpelcom"RPKI Not found2a02:2668:7400::
- 2a02:2668:7410::/44AS16345PJSC "Vimpelcom"RPKI Not found2a02:2668:7410::
- 2a02:2668:7420::/44AS16345PJSC "Vimpelcom"RPKI Not found2a02:2668:7420::
- 2a02:2668:7430::/44AS16345PJSC "Vimpelcom"RPKI Not found2a02:2668:7430::
- 2a02:2668:7440::/44AS16345PJSC "Vimpelcom"RPKI Not found2a02:2668:7440::
- 2a02:2668:7450::/44AS16345PJSC "Vimpelcom"RPKI Not found2a02:2668:7450::
- 2a02:2668:7460::/44AS16345PJSC "Vimpelcom"RPKI Not found2a02:2668:7460::
- 2a02:2668:7470::/44AS16345PJSC "Vimpelcom"RPKI Not found2a02:2668:7470::
- 2a02:2668:7480::/44AS16345PJSC "Vimpelcom"RPKI Not found2a02:2668:7480::
- 2a02:2668:7490::/44AS16345PJSC "Vimpelcom"RPKI Not found2a02:2668:7490::
- 2a02:2668:74a0::/44AS16345PJSC "Vimpelcom"RPKI Not found2a02:2668:74a0::
- 2a02:2668:74b0::/44AS16345PJSC "Vimpelcom"RPKI Not found2a02:2668:74b0::
- 2a02:2668:74c0::/44AS16345PJSC "Vimpelcom"RPKI Not found2a02:2668:74c0::
- 2a02:2668:74d0::/44AS16345PJSC "Vimpelcom"RPKI Not found2a02:2668:74d0::
- 2a02:2668:74e0::/44AS16345PJSC "Vimpelcom"RPKI Not found2a02:2668:74e0::
- 2a02:2668:74f0::/44AS16345PJSC "Vimpelcom"RPKI Not found2a02:2668:74f0::
- 2a02:2668:7500::/40AS16345PJSC "Vimpelcom"RPKI Not found2a02:2668:7500::
- 2a02:2668:7600::/40AS16345PJSC "Vimpelcom"RPKI Not found2a02:2668:7600::
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.