BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
95.104.128.0/17
Announced exactly
- 95.104.128.0/17AS8359MTS PJSCRPKI Not found95.104.128.0
- Registry
- RIPE NCC · Russia · Nov 28, 2008
- Delegated block
- 95.104.128.0 – 95.104.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 95.104.128.0/19AS29190MTS PJSCRPKI Not found95.104.128.0
- 95.104.160.0/20AS29190MTS PJSCRPKI Not found95.104.160.0
- 95.104.160.0/22AS29190MTS PJSCRPKI Not found95.104.160.0
- 95.104.164.0/22AS29190MTS PJSCRPKI Not found95.104.164.0
- 95.104.168.0/22AS29190MTS PJSCRPKI Not found95.104.168.0
- 95.104.172.0/22AS29190MTS PJSCRPKI Not found95.104.172.0
- 95.104.176.0/21AS8359MTS PJSCRPKI Not found95.104.176.0
- 95.104.176.0/24AS29190MTS PJSCRPKI Not found95.104.176.0
- 95.104.177.0/24AS29190MTS PJSCRPKI Not found95.104.177.0
- 95.104.178.0/24AS29190MTS PJSCRPKI Not found95.104.178.0
- 95.104.179.0/24AS29190MTS PJSCRPKI Not found95.104.179.0
- 95.104.180.0/24AS29190MTS PJSCRPKI Not found95.104.180.0
- 95.104.181.0/24AS29190MTS PJSCRPKI Not found95.104.181.0
- 95.104.182.0/24AS29190MTS PJSCRPKI Not found95.104.182.0
- 95.104.183.0/24AS29190MTS PJSCRPKI Not found95.104.183.0
- 95.104.184.0/21AS30922MTS PJSCRPKI Not found95.104.184.0
- 95.104.192.0/19AS49816MTS PJSCRPKI Not found95.104.192.0
- 95.104.194.0/24AS49816MTS PJSCRPKI Not found95.104.194.0
- 95.104.196.0/23AS49816MTS PJSCRPKI Not found95.104.196.0
- 95.104.198.0/23AS49816MTS PJSCRPKI Not found95.104.198.0
- 95.104.224.0/24AS8359MTS PJSCRPKI Not found95.104.224.0
- 95.104.225.0/24AS8359MTS PJSCRPKI Not found95.104.225.0
- 95.104.226.0/24AS8359MTS PJSCRPKI Not found95.104.226.0
- 95.104.227.0/24AS8359MTS PJSCRPKI Not found95.104.227.0
- 95.104.228.0/24AS8359MTS PJSCRPKI Not found95.104.228.0
- 95.104.229.0/24AS8359MTS PJSCRPKI Not found95.104.229.0
- 95.104.231.0/24AS8359MTS PJSCRPKI Not found95.104.231.0
- 95.104.232.0/24AS8359MTS PJSCRPKI Not found95.104.232.0
- 95.104.233.0/24AS8359MTS PJSCRPKI Not found95.104.233.0
- 95.104.234.0/24AS8359MTS PJSCRPKI Not found95.104.234.0
- 95.104.235.0/24AS8359MTS PJSCRPKI Not found95.104.235.0
- 95.104.236.0/24AS8359MTS PJSCRPKI Not found95.104.236.0
- 95.104.237.0/24AS8359MTS PJSCRPKI Not found95.104.237.0
- 95.104.238.0/24AS8359MTS PJSCRPKI Not found95.104.238.0
- 95.104.239.0/24AS8359MTS PJSCRPKI Not found95.104.239.0
- 95.104.240.0/24AS8359MTS PJSCRPKI Not found95.104.240.0
- 95.104.241.0/24AS8359MTS PJSCRPKI Not found95.104.241.0
- 95.104.242.0/23AS8359MTS PJSCRPKI Not found95.104.242.0
- 95.104.244.0/24AS8359MTS PJSCRPKI Not found95.104.244.0
- 95.104.245.0/24AS8359MTS PJSCRPKI Not found95.104.245.0
- 95.104.246.0/24AS8359MTS PJSCRPKI Not found95.104.246.0
- 95.104.247.0/24AS8359MTS PJSCRPKI Not found95.104.247.0
- 95.104.248.0/24AS8359MTS PJSCRPKI Not found95.104.248.0
- 95.104.249.0/24AS8359MTS PJSCRPKI Not found95.104.249.0
- 95.104.250.0/24AS8359MTS PJSCRPKI Not found95.104.250.0
- 95.104.251.0/24AS8359MTS PJSCRPKI Not found95.104.251.0
- 95.104.252.0/24AS8359MTS PJSCRPKI Not found95.104.252.0
- 95.104.253.0/24AS8359MTS PJSCRPKI Not found95.104.253.0
- 95.104.254.0/24AS8359MTS PJSCRPKI Not found95.104.254.0
- 95.104.255.0/24AS8359MTS PJSCRPKI Not found95.104.255.0
On the internet, routes are announced as prefixes: an autonomous system tells its neighbours via BGP that it can deliver traffic for, say, 85.240.0.0/13. 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.