BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
85.26.128.0/17
Announced exactly
- 85.26.128.0/17AS31133PJSC MegaFonRPKI Valid85.26.128.0
- Registry
- RIPE NCC · Russia · Mar 10, 2005
- Delegated block
- 85.26.128.0 – 85.26.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 85.26.128.0/20AS31213PJSC MegaFonRPKI Valid85.26.128.0
- 85.26.144.0/20AS25159PJSC MegaFonRPKI Valid85.26.144.0
- 85.26.160.0/22AS31133PJSC MegaFonRPKI Valid85.26.160.0
- 85.26.164.0/22AS31133PJSC MegaFonRPKI Valid85.26.164.0
- 85.26.164.0/23AS31133PJSC MegaFonRPKI Valid85.26.164.0
- 85.26.167.0/24AS31133PJSC MegaFonRPKI Valid85.26.167.0
- 85.26.168.0/22AS31133PJSC MegaFonRPKI Valid85.26.168.0
- 85.26.172.0/22AS31133PJSC MegaFonRPKI Valid85.26.172.0
- 85.26.173.0/24AS31133PJSC MegaFonRPKI Valid85.26.173.0
- 85.26.174.0/24AS31133PJSC MegaFonRPKI Valid85.26.174.0
- 85.26.176.0/23AS31163PJSC MegaFonRPKI Valid85.26.176.0
- 85.26.178.0/24AS31163PJSC MegaFonRPKI Valid85.26.178.0
- 85.26.181.0/24AS31163PJSC MegaFonRPKI Valid85.26.181.0
- 85.26.182.0/24AS31163PJSC MegaFonRPKI Valid85.26.182.0
- 85.26.183.0/24AS31163PJSC MegaFonRPKI Valid85.26.183.0
- 85.26.184.0/24AS31163PJSC MegaFonRPKI Valid85.26.184.0
- 85.26.185.0/24AS31163PJSC MegaFonRPKI Valid85.26.185.0
- 85.26.186.0/24AS31163PJSC MegaFonRPKI Valid85.26.186.0
- 85.26.187.0/24AS31163PJSC MegaFonRPKI Valid85.26.187.0
- 85.26.188.0/24AS31163PJSC MegaFonRPKI Valid85.26.188.0
- 85.26.189.0/24AS31163PJSC MegaFonRPKI Valid85.26.189.0
- 85.26.191.0/24AS31163PJSC MegaFonRPKI Valid85.26.191.0
- 85.26.192.0/22AS31224PJSC MegaFonRPKI Valid85.26.192.0
- 85.26.196.0/22AS31133PJSC MegaFonRPKI Valid85.26.196.0
- 85.26.200.0/24AS31133PJSC MegaFonRPKI Valid85.26.200.0
- 85.26.201.0/24AS31133PJSC MegaFonRPKI Valid85.26.201.0
- 85.26.202.0/24AS31133PJSC MegaFonRPKI Valid85.26.202.0
- 85.26.203.0/24AS31133PJSC MegaFonRPKI Valid85.26.203.0
- 85.26.204.0/24AS31133PJSC MegaFonRPKI Valid85.26.204.0
- 85.26.205.0/24AS31133PJSC MegaFonRPKI Valid85.26.205.0
- 85.26.206.0/24AS31133PJSC MegaFonRPKI Valid85.26.206.0
- 85.26.207.0/24AS31133PJSC MegaFonRPKI Valid85.26.207.0
- 85.26.208.0/22AS31213PJSC MegaFonRPKI Valid85.26.208.0
- 85.26.212.0/22AS31213PJSC MegaFonRPKI Valid85.26.212.0
- 85.26.216.0/22AS31213PJSC MegaFonRPKI Valid85.26.216.0
- 85.26.220.0/22AS31213PJSC MegaFonRPKI Valid85.26.220.0
- 85.26.224.0/24AS31133PJSC MegaFonRPKI Valid85.26.224.0
- 85.26.227.0/24AS31205PJSC MegaFonRPKI Valid85.26.227.0
- 85.26.228.0/24AS31205PJSC MegaFonRPKI Valid85.26.228.0
- 85.26.229.0/24AS31205PJSC MegaFonRPKI Valid85.26.229.0
- 85.26.230.0/24AS31205PJSC MegaFonRPKI Valid85.26.230.0
- 85.26.231.0/24AS31133PJSC MegaFonRPKI Valid85.26.231.0
- 85.26.232.0/21AS31133PJSC MegaFonRPKI Valid85.26.232.0
- 85.26.232.0/23AS31133PJSC MegaFonRPKI Valid85.26.232.0
- 85.26.234.0/23AS31133PJSC MegaFonRPKI Valid85.26.234.0
- 85.26.236.0/22AS31133PJSC MegaFonRPKI Valid85.26.236.0
- 85.26.240.0/22AS31195PJSC MegaFonRPKI Valid85.26.240.0
- 85.26.241.0/24AS31133PJSC MegaFonRPKI Valid85.26.241.0
- 85.26.242.0/24AS31133PJSC MegaFonRPKI Valid85.26.242.0
- 85.26.243.0/24AS31133PJSC MegaFonRPKI Valid85.26.243.0
- 85.26.244.0/22AS31195PJSC MegaFonRPKI Valid85.26.244.0
- 85.26.244.0/24AS31133PJSC MegaFonRPKI Valid85.26.244.0
- 85.26.245.0/24AS31133PJSC MegaFonRPKI Valid85.26.245.0
- 85.26.247.0/24AS31195PJSC MegaFonRPKI Valid85.26.247.0
- 85.26.248.0/22AS31213PJSC MegaFonRPKI Valid85.26.248.0
- 85.26.252.0/22AS31213PJSC MegaFonRPKI Valid85.26.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.