BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
188.162.0.0/16
Announced exactly
- 188.162.0.0/16AS31133PJSC MegaFonRPKI Valid188.162.0.0
- Registry
- RIPE NCC · Russia · May 20, 2009
- Delegated block
- 188.162.0.0 – 188.162.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 188.162.0.0/24AS31205PJSC MegaFonRPKI Valid188.162.0.0
- 188.162.1.0/24AS31205PJSC MegaFonRPKI Valid188.162.1.0
- 188.162.2.0/23AS31205PJSC MegaFonRPKI Valid188.162.2.0
- 188.162.4.0/22AS31205PJSC MegaFonRPKI Valid188.162.4.0
- 188.162.8.0/23AS31205PJSC MegaFonRPKI Valid188.162.8.0
- 188.162.10.0/23AS31205PJSC MegaFonRPKI Valid188.162.10.0
- 188.162.12.0/23AS31205PJSC MegaFonRPKI Valid188.162.12.0
- 188.162.14.0/23AS31133PJSC MegaFonRPKI Valid188.162.14.0
- 188.162.32.0/22AS31133PJSC MegaFonRPKI Valid188.162.32.0
- 188.162.36.0/23AS31133PJSC MegaFonRPKI Valid188.162.36.0
- 188.162.38.0/23AS31133PJSC MegaFonRPKI Valid188.162.38.0
- 188.162.40.0/21AS31133PJSC MegaFonRPKI Valid188.162.40.0
- 188.162.48.0/20AS31133PJSC MegaFonRPKI Valid188.162.48.0
- 188.162.55.0/24AS31133PJSC MegaFonRPKI Valid188.162.55.0
- 188.162.61.0/24AS31133PJSC MegaFonRPKI Valid188.162.61.0
- 188.162.62.0/23AS31133PJSC MegaFonRPKI Valid188.162.62.0
- 188.162.64.0/23AS31213PJSC MegaFonRPKI Valid188.162.64.0
- 188.162.72.0/22AS31133PJSC MegaFonRPKI Valid188.162.72.0
- 188.162.76.0/23AS31133PJSC MegaFonRPKI Valid188.162.76.0
- 188.162.78.0/24AS31205PJSC MegaFonRPKI Valid188.162.78.0
- 188.162.79.0/24AS31205PJSC MegaFonRPKI Valid188.162.79.0
- 188.162.80.0/24AS31133PJSC MegaFonRPKI Valid188.162.80.0
- 188.162.81.0/24AS31205PJSC MegaFonRPKI Valid188.162.81.0
- 188.162.82.0/24AS31205PJSC MegaFonRPKI Valid188.162.82.0
- 188.162.83.0/24AS31205PJSC MegaFonRPKI Valid188.162.83.0
- 188.162.84.0/24AS31133PJSC MegaFonRPKI Valid188.162.84.0
- 188.162.85.0/24AS31205PJSC MegaFonRPKI Valid188.162.85.0
- 188.162.87.0/24AS31205PJSC MegaFonRPKI Valid188.162.87.0
- 188.162.88.0/24AS31205PJSC MegaFonRPKI Valid188.162.88.0
- 188.162.89.0/24AS31205PJSC MegaFonRPKI Valid188.162.89.0
- 188.162.90.0/23AS31205PJSC MegaFonRPKI Valid188.162.90.0
- 188.162.92.0/22AS31205PJSC MegaFonRPKI Valid188.162.92.0
- 188.162.128.0/24AS31163PJSC MegaFonRPKI Valid188.162.128.0
- 188.162.129.0/24AS31163PJSC MegaFonRPKI Valid188.162.129.0
- 188.162.130.0/23AS31163PJSC MegaFonRPKI Valid188.162.130.0
- 188.162.132.0/24AS31163PJSC MegaFonRPKI Valid188.162.132.0
- 188.162.133.0/24AS31163PJSC MegaFonRPKI Valid188.162.133.0
- 188.162.134.0/23AS31163PJSC MegaFonRPKI Valid188.162.134.0
- 188.162.136.0/23AS31163PJSC MegaFonRPKI Valid188.162.136.0
- 188.162.138.0/24AS31163PJSC MegaFonRPKI Valid188.162.138.0
- 188.162.139.0/24AS31163PJSC MegaFonRPKI Valid188.162.139.0
- 188.162.140.0/24AS31163PJSC MegaFonRPKI Valid188.162.140.0
- 188.162.141.0/24AS31163PJSC MegaFonRPKI Valid188.162.141.0
- 188.162.142.0/24AS31163PJSC MegaFonRPKI Valid188.162.142.0
- 188.162.143.0/24AS31163PJSC MegaFonRPKI Valid188.162.143.0
- 188.162.144.0/24AS31163PJSC MegaFonRPKI Valid188.162.144.0
- 188.162.145.0/24AS31163PJSC MegaFonRPKI Valid188.162.145.0
- 188.162.146.0/23AS31163PJSC MegaFonRPKI Valid188.162.146.0
- 188.162.148.0/22AS31163PJSC MegaFonRPKI Valid188.162.148.0
- 188.162.152.0/22AS31163PJSC MegaFonRPKI Valid188.162.152.0
- 188.162.156.0/24AS31163PJSC MegaFonRPKI Valid188.162.156.0
- 188.162.161.0/24AS31163PJSC MegaFonRPKI Valid188.162.161.0
- 188.162.162.0/24AS31163PJSC MegaFonRPKI Valid188.162.162.0
- 188.162.163.0/24AS31163PJSC MegaFonRPKI Valid188.162.163.0
- 188.162.164.0/23AS31163PJSC MegaFonRPKI Valid188.162.164.0
- 188.162.166.0/24AS31163PJSC MegaFonRPKI Valid188.162.166.0
- 188.162.167.0/24AS31163PJSC MegaFonRPKI Valid188.162.167.0
- 188.162.168.0/23AS31163PJSC MegaFonRPKI Valid188.162.168.0
- 188.162.170.0/23AS31163PJSC MegaFonRPKI Valid188.162.170.0
- 188.162.172.0/22AS31163PJSC MegaFonRPKI Valid188.162.172.0
- 188.162.176.0/22AS31163PJSC MegaFonRPKI Valid188.162.176.0
- 188.162.180.0/22AS31163PJSC MegaFonRPKI Valid188.162.180.0
- 188.162.184.0/22AS31163PJSC MegaFonRPKI Valid188.162.184.0
- 188.162.188.0/24AS31163PJSC MegaFonRPKI Valid188.162.188.0
- 188.162.191.0/24AS31163PJSC MegaFonRPKI Valid188.162.191.0
- 188.162.192.0/23AS31133PJSC MegaFonRPKI Valid188.162.192.0
- 188.162.194.0/23AS31133PJSC MegaFonRPKI Valid188.162.194.0
- 188.162.196.0/22AS31133PJSC MegaFonRPKI Valid188.162.196.0
- 188.162.200.0/21AS31133PJSC MegaFonRPKI Valid188.162.200.0
- 188.162.207.0/24AS31133PJSC MegaFonRPKI Valid188.162.207.0
- 188.162.220.0/22AS31133PJSC MegaFonRPKI Valid188.162.220.0
- 188.162.224.0/24AS31133PJSC MegaFonRPKI Valid188.162.224.0
- 188.162.225.0/24AS31133PJSC MegaFonRPKI Valid188.162.225.0
- 188.162.226.0/23AS31133PJSC MegaFonRPKI Valid188.162.226.0
- 188.162.228.0/24AS31133PJSC MegaFonRPKI Valid188.162.228.0
- 188.162.229.0/24AS31133PJSC MegaFonRPKI Valid188.162.229.0
- 188.162.230.0/23AS31133PJSC MegaFonRPKI Valid188.162.230.0
- 188.162.231.0/24AS31133PJSC MegaFonRPKI Valid188.162.231.0
- 188.162.232.0/24AS31133PJSC MegaFonRPKI Valid188.162.232.0
- 188.162.233.0/24AS31133PJSC MegaFonRPKI Valid188.162.233.0
- 188.162.234.0/23AS31133PJSC MegaFonRPKI Valid188.162.234.0
- 188.162.236.0/24AS31133PJSC MegaFonRPKI Valid188.162.236.0
- 188.162.237.0/24AS31133PJSC MegaFonRPKI Valid188.162.237.0
- 188.162.238.0/24AS31133PJSC MegaFonRPKI Valid188.162.238.0
- 188.162.239.0/24AS31133PJSC MegaFonRPKI Valid188.162.239.0
- 188.162.240.0/24AS31133PJSC MegaFonRPKI Valid188.162.240.0
- 188.162.241.0/24AS31133PJSC MegaFonRPKI Valid188.162.241.0
- 188.162.242.0/24AS31133PJSC MegaFonRPKI Valid188.162.242.0
- 188.162.243.0/24AS31133PJSC MegaFonRPKI Valid188.162.243.0
- 188.162.244.0/24AS31133PJSC MegaFonRPKI Valid188.162.244.0
- 188.162.245.0/24AS31133PJSC MegaFonRPKI Valid188.162.245.0
- 188.162.246.0/23AS31133PJSC MegaFonRPKI Valid188.162.246.0
- 188.162.248.0/22AS31133PJSC MegaFonRPKI Valid188.162.248.0
- 188.162.252.0/22AS31133PJSC MegaFonRPKI Valid188.162.252.0
On the internet, routes are announced as prefixes: an autonomous system tells its neighbours via BGP that it can deliver traffic for, say, 49.224.0.0/14. 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.