BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
94.159.0.0/17
Announced exactly
- 94.159.0.0/17AS49531"NetCom-R" LLCRPKI Valid94.159.0.0
- Registry
- RIPE NCC · Russia · Sep 4, 2008
- Delegated block
- 94.159.0.0 – 94.159.63.255
Covering routes
No less-specific route covers it.
More-specific routes
- 94.159.0.0/18AS49531"NetCom-R" LLCRPKI Valid94.159.0.0
- 94.159.0.0/23AS49531"NetCom-R" LLCRPKI Valid94.159.0.0
- 94.159.2.0/23AS49531"NetCom-R" LLCRPKI Valid94.159.2.0
- 94.159.4.0/23AS49531"NetCom-R" LLCRPKI Valid94.159.4.0
- 94.159.6.0/23AS49531"NetCom-R" LLCRPKI Valid94.159.6.0
- 94.159.8.0/23AS49531"NetCom-R" LLCRPKI Valid94.159.8.0
- 94.159.10.0/23AS49531"NetCom-R" LLCRPKI Valid94.159.10.0
- 94.159.12.0/23AS49531"NetCom-R" LLCRPKI Valid94.159.12.0
- 94.159.14.0/23AS49531"NetCom-R" LLCRPKI Valid94.159.14.0
- 94.159.16.0/23AS49531"NetCom-R" LLCRPKI Valid94.159.16.0
- 94.159.18.0/23AS49531"NetCom-R" LLCRPKI Valid94.159.18.0
- 94.159.20.0/23AS49531"NetCom-R" LLCRPKI Valid94.159.20.0
- 94.159.22.0/23AS49531"NetCom-R" LLCRPKI Valid94.159.22.0
- 94.159.24.0/23AS49531"NetCom-R" LLCRPKI Valid94.159.24.0
- 94.159.26.0/23AS49531"NetCom-R" LLCRPKI Valid94.159.26.0
- 94.159.28.0/23AS49531"NetCom-R" LLCRPKI Valid94.159.28.0
- 94.159.30.0/23AS49531"NetCom-R" LLCRPKI Valid94.159.30.0
- 94.159.32.0/23AS49531"NetCom-R" LLCRPKI Valid94.159.32.0
- 94.159.34.0/23AS49531"NetCom-R" LLCRPKI Valid94.159.34.0
- 94.159.36.0/23AS49531"NetCom-R" LLCRPKI Valid94.159.36.0
- 94.159.38.0/23AS49531"NetCom-R" LLCRPKI Valid94.159.38.0
- 94.159.40.0/23AS49531"NetCom-R" LLCRPKI Valid94.159.40.0
- 94.159.42.0/23AS49531"NetCom-R" LLCRPKI Valid94.159.42.0
- 94.159.44.0/23AS49531"NetCom-R" LLCRPKI Valid94.159.44.0
- 94.159.46.0/23AS49531"NetCom-R" LLCRPKI Valid94.159.46.0
- 94.159.48.0/23AS49531"NetCom-R" LLCRPKI Valid94.159.48.0
- 94.159.50.0/23AS49531"NetCom-R" LLCRPKI Valid94.159.50.0
- 94.159.52.0/23AS49531"NetCom-R" LLCRPKI Valid94.159.52.0
- 94.159.54.0/23AS49531"NetCom-R" LLCRPKI Valid94.159.54.0
- 94.159.56.0/23AS49531"NetCom-R" LLCRPKI Valid94.159.56.0
- 94.159.58.0/23AS49531"NetCom-R" LLCRPKI Valid94.159.58.0
- 94.159.60.0/23AS49531"NetCom-R" LLCRPKI Valid94.159.60.0
- 94.159.62.0/23AS49531"NetCom-R" LLCRPKI Valid94.159.62.0
- 94.159.64.0/19AS49531"NetCom-R" LLCRPKI Valid94.159.64.0
- 94.159.64.0/23AS49531"NetCom-R" LLCRPKI Valid94.159.64.0
- 94.159.66.0/23AS49531"NetCom-R" LLCRPKI Valid94.159.66.0
- 94.159.68.0/23AS49531"NetCom-R" LLCRPKI Valid94.159.68.0
- 94.159.70.0/24AS49531"NetCom-R" LLCRPKI Valid94.159.70.0
- 94.159.71.0/24AS29076Citytelecom LLCRPKI Valid94.159.71.0
- 94.159.72.0/23AS49531"NetCom-R" LLCRPKI Valid94.159.72.0
- 94.159.74.0/23AS49531"NetCom-R" LLCRPKI Valid94.159.74.0
- 94.159.76.0/23AS49531"NetCom-R" LLCRPKI Valid94.159.76.0
- 94.159.78.0/23AS49531"NetCom-R" LLCRPKI Valid94.159.78.0
- 94.159.80.0/23AS49531"NetCom-R" LLCRPKI Valid94.159.80.0
- 94.159.81.0/24AS214356Vyaznikov Maxim NikolaevichRPKI Valid94.159.81.0
- 94.159.82.0/23AS49531"NetCom-R" LLCRPKI Valid94.159.82.0
- 94.159.84.0/24AS29076Citytelecom LLCRPKI Valid94.159.84.0
- 94.159.85.0/24AS49531"NetCom-R" LLCRPKI Valid94.159.85.0
- 94.159.86.0/24AS28762Citytelecom LLCRPKI Valid94.159.86.0
- 94.159.87.0/24AS29076Citytelecom LLCRPKI Valid94.159.87.0
- 94.159.88.0/22AS49531"NetCom-R" LLCRPKI Valid94.159.88.0
- 94.159.92.0/24AS49531"NetCom-R" LLCRPKI Valid94.159.92.0
- 94.159.93.0/24AS51219K2 Integration JSCRPKI Valid94.159.93.0
- 94.159.95.0/24AS29076Citytelecom LLCRPKI Valid94.159.95.0
- 94.159.112.0/24AS216300Closed Joint Stock Company "AbkhazMedia"RPKI Valid94.159.112.0
- 94.159.113.0/24AS216334New Hosting Technologies LLCRPKI Valid94.159.113.0
- 94.159.114.0/24AS216300Closed Joint Stock Company "AbkhazMedia"RPKI Valid94.159.114.0
- 94.159.115.0/24AS216334New Hosting Technologies LLCRPKI Valid94.159.115.0
- 94.159.116.0/24AS216334New Hosting Technologies LLCRPKI Valid94.159.116.0
- 94.159.117.0/24AS216334New Hosting Technologies LLCRPKI Valid94.159.117.0
- 94.159.118.0/24AS49531"NetCom-R" LLCRPKI Valid94.159.118.0
- 94.159.119.0/24AS49531"NetCom-R" LLCRPKI Valid94.159.119.0
- 94.159.120.0/22AS49531"NetCom-R" LLCRPKI Valid94.159.120.0
- 94.159.124.0/22AS49531"NetCom-R" LLCRPKI Valid94.159.124.0
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.