BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
213.87.0.0/16
Announced exactly
- 213.87.0.0/16AS8359MTS PJSCRPKI Valid213.87.0.0
- Registry
- RIPE NCC · Russia · Apr 10, 2000
- Delegated block
- 213.87.0.0 – 213.87.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 213.87.0.0/21AS13174MTS PJSCRPKI Valid213.87.0.0
- 213.87.16.0/21AS13174MTS PJSCRPKI Valid213.87.16.0
- 213.87.24.0/21AS13174MTS PJSCRPKI Valid213.87.24.0
- 213.87.32.0/23AS13174MTS PJSCRPKI Valid213.87.32.0
- 213.87.36.0/22AS13174MTS PJSCRPKI Valid213.87.36.0
- 213.87.42.0/23AS15640MTS PJSCRPKI Valid213.87.42.0
- 213.87.44.0/22AS13174MTS PJSCRPKI Valid213.87.44.0
- 213.87.48.0/22AS13174MTS PJSCRPKI Valid213.87.48.0
- 213.87.50.0/23AS13174MTS PJSCRPKI Valid213.87.50.0
- 213.87.52.0/24AS13174MTS PJSCRPKI Valid213.87.52.0
- 213.87.64.0/22AS8359MTS PJSCRPKI Valid213.87.64.0
- 213.87.70.0/23AS8359MTS PJSCRPKI Valid213.87.70.0
- 213.87.72.0/22AS35473MTS PJSCRPKI Valid213.87.72.0
- 213.87.76.0/23AS8359MTS PJSCRPKI Valid213.87.76.0
- 213.87.80.0/20AS8359MTS PJSCRPKI Valid213.87.80.0
- 213.87.80.0/22AS8359MTS PJSCRPKI Valid213.87.80.0
- 213.87.94.0/23AS8359MTS PJSCRPKI Valid213.87.94.0
- 213.87.96.0/24AS39811MTS PJSCRPKI Valid213.87.96.0
- 213.87.97.0/24AS39811MTS PJSCRPKI Valid213.87.97.0
- 213.87.98.0/23AS8359MTS PJSCRPKI Valid213.87.98.0
- 213.87.100.0/24AS8359MTS PJSCRPKI Valid213.87.100.0
- 213.87.101.0/24AS8359MTS PJSCRPKI Valid213.87.101.0
- 213.87.102.0/24AS39811MTS PJSCRPKI Valid213.87.102.0
- 213.87.103.0/24AS39811MTS PJSCRPKI Valid213.87.103.0
- 213.87.104.0/24AS8359MTS PJSCRPKI Valid213.87.104.0
- 213.87.105.0/24AS8359MTS PJSCRPKI Valid213.87.105.0
- 213.87.106.0/23AS8359MTS PJSCRPKI Valid213.87.106.0
- 213.87.116.0/23AS28884MTS PJSCRPKI Valid213.87.116.0
- 213.87.124.0/23AS28884MTS PJSCRPKI Valid213.87.124.0
- 213.87.128.0/19AS8359MTS PJSCRPKI Valid213.87.128.0
- 213.87.160.0/22AS8359MTS PJSCRPKI Valid213.87.160.0
- 213.87.192.0/21AS8359MTS PJSCRPKI Valid213.87.192.0
- 213.87.200.0/22AS8359MTS PJSCRPKI Valid213.87.200.0
- 213.87.208.0/23AS8359MTS PJSCRPKI Valid213.87.208.0
- 213.87.210.0/23AS8359MTS PJSCRPKI Valid213.87.210.0
- 213.87.240.0/22AS8359MTS PJSCRPKI Valid213.87.240.0
- 213.87.244.0/23AS8359MTS PJSCRPKI Valid213.87.244.0
- 213.87.246.0/24AS8359MTS PJSCRPKI Valid213.87.246.0
- 213.87.248.0/22AS8359MTS PJSCRPKI Valid213.87.248.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.