BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
2620:119:5000::/42
Announced exactly
- 2620:119:5000::/42AS13443LinkedIn CorporationRPKI Not found2620:119:5000::
- Registry
- ARIN · United States · May 5, 2014
- Delegated block
- 2620:119:5000:: – 2620:119:50ff:ffff:ffff:ffff:ffff:ffff
Covering routes
No less-specific route covers it.
More-specific routes
- 2620:119:5000::/48AS13443LinkedIn CorporationRPKI Not found2620:119:5000::
- 2620:119:5001::/48AS13443LinkedIn CorporationRPKI Not found2620:119:5001::
- 2620:119:5002::/48AS13443LinkedIn CorporationRPKI Not found2620:119:5002::
- 2620:119:5005::/48AS13443LinkedIn CorporationRPKI Not found2620:119:5005::
- 2620:119:5008::/48AS13443LinkedIn CorporationRPKI Not found2620:119:5008::
- 2620:119:500a::/48AS13443LinkedIn CorporationRPKI Not found2620:119:500a::
- 2620:119:500d::/48AS13443LinkedIn CorporationRPKI Not found2620:119:500d::
- 2620:119:500e::/48AS13443LinkedIn CorporationRPKI Not found2620:119:500e::
- 2620:119:500f::/48AS13443LinkedIn CorporationRPKI Not found2620:119:500f::
- 2620:119:5011::/48AS13443LinkedIn CorporationRPKI Not found2620:119:5011::
- 2620:119:5014::/48AS13443LinkedIn CorporationRPKI Not found2620:119:5014::
- 2620:119:501a::/48AS13443LinkedIn CorporationRPKI Not found2620:119:501a::
- 2620:119:501b::/48AS13443LinkedIn CorporationRPKI Not found2620:119:501b::
- 2620:119:501d::/48AS13443LinkedIn CorporationRPKI Not found2620:119:501d::
- 2620:119:501e::/48AS13443LinkedIn CorporationRPKI Not found2620:119:501e::
- 2620:119:501f::/48AS13443LinkedIn CorporationRPKI Not found2620:119:501f::
- 2620:119:5020::/48AS13443LinkedIn CorporationRPKI Not found2620:119:5020::
- 2620:119:5021::/48AS13443LinkedIn CorporationRPKI Not found2620:119:5021::
- 2620:119:5023::/48AS13443LinkedIn CorporationRPKI Not found2620:119:5023::
- 2620:119:5024::/48AS13443LinkedIn CorporationRPKI Not found2620:119:5024::
- 2620:119:5025::/48AS13443LinkedIn CorporationRPKI Not found2620:119:5025::
- 2620:119:5026::/48AS13443LinkedIn CorporationRPKI Not found2620:119:5026::
On the internet, routes are announced as prefixes: an autonomous system tells its neighbours via BGP that it can deliver traffic for, say, 90.190.0.0/15 (Telia Eesti, AS3249). 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.