BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
85.140.0.0/15
Announced exactly
- 85.140.0.0/15AS8359MTS PJSCRPKI Valid85.140.0.0
- Registry
- RIPE NCC · Russia · Dec 13, 2004
- Delegated block
- 85.140.0.0 – 85.141.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 85.140.30.0/24AS8359MTS PJSCRPKI Valid85.140.30.0
- 85.140.31.0/24AS8359MTS PJSCRPKI Valid85.140.31.0
- 85.140.32.0/21AS39001MTS PJSCRPKI Valid85.140.32.0
- 85.140.40.0/22AS8359MTS PJSCRPKI Valid85.140.40.0
- 85.140.43.0/24AS8359MTS PJSCRPKI Valid85.140.43.0
- 85.140.44.0/22AS35728MTS PJSCRPKI Valid85.140.44.0
- 85.140.56.0/24AS48123MTS PJSCRPKI Valid85.140.56.0
- 85.140.57.0/24AS48123MTS PJSCRPKI Valid85.140.57.0
- 85.140.58.0/24AS48123MTS PJSCRPKI Valid85.140.58.0
- 85.140.59.0/24AS48123MTS PJSCRPKI Valid85.140.59.0
- 85.140.60.0/22AS41209MTS PJSCRPKI Valid85.140.60.0
- 85.140.60.0/24AS41209MTS PJSCRPKI Valid85.140.60.0
- 85.140.61.0/24AS41209MTS PJSCRPKI Valid85.140.61.0
- 85.140.62.0/24AS41209MTS PJSCRPKI Valid85.140.62.0
- 85.140.63.0/24AS41209MTS PJSCRPKI Valid85.140.63.0
- 85.140.64.0/21AS39001MTS PJSCRPKI Valid85.140.64.0
- 85.140.72.0/24AS48123MTS PJSCRPKI Valid85.140.72.0
- 85.140.73.0/24AS48123MTS PJSCRPKI Valid85.140.73.0
- 85.140.80.0/21AS39001MTS PJSCRPKI Valid85.140.80.0
- 85.140.92.0/23AS8359MTS PJSCRPKI Valid85.140.92.0
- 85.140.94.0/24AS8359MTS PJSCRPKI Valid85.140.94.0
- 85.140.96.0/20AS28884MTS PJSCRPKI Valid85.140.96.0
- 85.140.96.0/21AS28884MTS PJSCRPKI Valid85.140.96.0
- 85.140.104.0/21AS28884MTS PJSCRPKI Valid85.140.104.0
- 85.140.112.0/22AS48124MTS PJSCRPKI Valid85.140.112.0
- 85.140.112.0/23AS48124MTS PJSCRPKI Valid85.140.112.0
- 85.140.113.0/24AS8359MTS PJSCRPKI Valid85.140.113.0
- 85.140.114.0/23AS48124MTS PJSCRPKI Valid85.140.114.0
- 85.140.124.0/23AS8359MTS PJSCRPKI Valid85.140.124.0
- 85.140.126.0/24AS48612MTS PJSCRPKI Valid85.140.126.0
- 85.140.127.0/24AS39811MTS PJSCRPKI Valid85.140.127.0
- 85.140.160.0/22AS8359MTS PJSCRPKI Valid85.140.160.0
- 85.140.164.0/22AS8359MTS PJSCRPKI Valid85.140.164.0
- 85.140.164.0/23AS8359MTS PJSCRPKI Valid85.140.164.0
- 85.141.16.0/21AS8359MTS PJSCRPKI Valid85.141.16.0
- 85.141.24.0/21AS8359MTS PJSCRPKI Valid85.141.24.0
- 85.141.32.0/21AS8359MTS PJSCRPKI Valid85.141.32.0
- 85.141.48.0/21AS8359MTS PJSCRPKI Valid85.141.48.0
- 85.141.56.0/22AS8359MTS PJSCRPKI Valid85.141.56.0
- 85.141.60.0/22AS8359MTS PJSCRPKI Valid85.141.60.0
- 85.141.68.0/22AS8359MTS PJSCRPKI Valid85.141.68.0
- 85.141.80.0/21AS8359MTS PJSCRPKI Valid85.141.80.0
- 85.141.92.0/22AS8359MTS PJSCRPKI Valid85.141.92.0
- 85.141.96.0/21AS8359MTS PJSCRPKI Valid85.141.96.0
- 85.141.104.0/21AS8359MTS PJSCRPKI Valid85.141.104.0
- 85.141.112.0/21AS8359MTS PJSCRPKI Valid85.141.112.0
On the internet, routes are announced as prefixes: an autonomous system tells its neighbours via BGP that it can deliver traffic for, say, 193.166.0.0/15. 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.