BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
95.72.0.0/15
Announced exactly
- 95.72.0.0/15AS25515PJSC RostelecomRPKI Valid95.72.0.0
- Registry
- RIPE NCC · Russia · Nov 28, 2008
- Delegated block
- 95.72.0.0 – 95.73.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 95.72.0.0/21AS12389PJSC RostelecomRPKI Valid95.72.0.0
- 95.72.8.0/21AS12389PJSC RostelecomRPKI Valid95.72.8.0
- 95.72.16.0/21AS12389PJSC RostelecomRPKI Valid95.72.16.0
- 95.72.24.0/21AS12389PJSC RostelecomRPKI Valid95.72.24.0
- 95.72.32.0/21AS12389PJSC RostelecomRPKI Valid95.72.32.0
- 95.72.40.0/21AS12389PJSC RostelecomRPKI Valid95.72.40.0
- 95.72.48.0/21AS12389PJSC RostelecomRPKI Valid95.72.48.0
- 95.72.56.0/21AS12389PJSC RostelecomRPKI Valid95.72.56.0
- 95.72.64.0/21AS12389PJSC RostelecomRPKI Valid95.72.64.0
- 95.72.72.0/21AS12389PJSC RostelecomRPKI Valid95.72.72.0
- 95.72.80.0/21AS12389PJSC RostelecomRPKI Valid95.72.80.0
- 95.72.88.0/21AS12389PJSC RostelecomRPKI Valid95.72.88.0
- 95.72.96.0/21AS12389PJSC RostelecomRPKI Valid95.72.96.0
- 95.72.104.0/21AS12389PJSC RostelecomRPKI Valid95.72.104.0
- 95.72.112.0/21AS12389PJSC RostelecomRPKI Valid95.72.112.0
- 95.72.120.0/21AS12389PJSC RostelecomRPKI Valid95.72.120.0
- 95.72.128.0/21AS12389PJSC RostelecomRPKI Valid95.72.128.0
- 95.72.136.0/21AS12389PJSC RostelecomRPKI Valid95.72.136.0
- 95.72.144.0/21AS12389PJSC RostelecomRPKI Valid95.72.144.0
- 95.72.152.0/21AS12389PJSC RostelecomRPKI Valid95.72.152.0
- 95.72.160.0/21AS12389PJSC RostelecomRPKI Valid95.72.160.0
- 95.72.168.0/21AS12389PJSC RostelecomRPKI Valid95.72.168.0
- 95.72.176.0/21AS12389PJSC RostelecomRPKI Valid95.72.176.0
- 95.72.184.0/21AS12389PJSC RostelecomRPKI Valid95.72.184.0
- 95.72.192.0/21AS12389PJSC RostelecomRPKI Valid95.72.192.0
- 95.72.200.0/21AS12389PJSC RostelecomRPKI Valid95.72.200.0
- 95.72.208.0/21AS12389PJSC RostelecomRPKI Valid95.72.208.0
- 95.72.216.0/21AS12389PJSC RostelecomRPKI Valid95.72.216.0
- 95.72.224.0/21AS12389PJSC RostelecomRPKI Valid95.72.224.0
- 95.72.232.0/21AS12389PJSC RostelecomRPKI Valid95.72.232.0
- 95.72.240.0/21AS12389PJSC RostelecomRPKI Valid95.72.240.0
- 95.72.248.0/21AS12389PJSC RostelecomRPKI Valid95.72.248.0
- 95.73.0.0/21AS12389PJSC RostelecomRPKI Valid95.73.0.0
- 95.73.8.0/21AS12389PJSC RostelecomRPKI Valid95.73.8.0
- 95.73.16.0/21AS12389PJSC RostelecomRPKI Valid95.73.16.0
- 95.73.24.0/21AS12389PJSC RostelecomRPKI Valid95.73.24.0
- 95.73.32.0/21AS12389PJSC RostelecomRPKI Valid95.73.32.0
- 95.73.40.0/21AS12389PJSC RostelecomRPKI Valid95.73.40.0
- 95.73.48.0/21AS12389PJSC RostelecomRPKI Valid95.73.48.0
- 95.73.64.0/21AS12389PJSC RostelecomRPKI Valid95.73.64.0
- 95.73.72.0/21AS12389PJSC RostelecomRPKI Valid95.73.72.0
- 95.73.80.0/21AS12389PJSC RostelecomRPKI Valid95.73.80.0
- 95.73.88.0/21AS12389PJSC RostelecomRPKI Valid95.73.88.0
- 95.73.96.0/21AS12389PJSC RostelecomRPKI Valid95.73.96.0
- 95.73.104.0/21AS12389PJSC RostelecomRPKI Valid95.73.104.0
- 95.73.112.0/21AS12389PJSC RostelecomRPKI Valid95.73.112.0
- 95.73.120.0/21AS12389PJSC RostelecomRPKI Valid95.73.120.0
- 95.73.128.0/21AS12389PJSC RostelecomRPKI Valid95.73.128.0
- 95.73.136.0/21AS12389PJSC RostelecomRPKI Valid95.73.136.0
- 95.73.144.0/21AS12389PJSC RostelecomRPKI Valid95.73.144.0
- 95.73.152.0/21AS12389PJSC RostelecomRPKI Valid95.73.152.0
- 95.73.160.0/21AS12389PJSC RostelecomRPKI Valid95.73.160.0
- 95.73.168.0/21AS12389PJSC RostelecomRPKI Valid95.73.168.0
- 95.73.176.0/21AS12389PJSC RostelecomRPKI Valid95.73.176.0
- 95.73.184.0/21AS12389PJSC RostelecomRPKI Valid95.73.184.0
- 95.73.192.0/21AS12389PJSC RostelecomRPKI Valid95.73.192.0
- 95.73.200.0/21AS12389PJSC RostelecomRPKI Valid95.73.200.0
- 95.73.208.0/21AS12389PJSC RostelecomRPKI Valid95.73.208.0
- 95.73.216.0/21AS12389PJSC RostelecomRPKI Valid95.73.216.0
- 95.73.224.0/21AS12389PJSC RostelecomRPKI Valid95.73.224.0
- 95.73.232.0/21AS12389PJSC RostelecomRPKI Valid95.73.232.0
- 95.73.240.0/21AS12389PJSC RostelecomRPKI Valid95.73.240.0
- 95.73.248.0/21AS12389PJSC RostelecomRPKI Valid95.73.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, 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.