BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
195.72.160.0/19
Announced exactly
- 195.72.160.0/19AS3257GTT Communications Inc.RPKI Not found195.72.160.0
- Registry
- RIPE NCC · United Kingdom · Sep 30, 1997
- Delegated block
- 195.72.160.0 – 195.72.191.255
Covering routes
No less-specific route covers it.
More-specific routes
- 195.72.160.0/22AS54004Cablevision Lightpath LLCRPKI Valid195.72.160.0
- 195.72.165.0/24AS5065Bunny CommunicationsRPKI Valid195.72.165.0
- 195.72.166.0/24AS203758EUGAMEHOST LTDRPKI Valid195.72.166.0
- 195.72.167.0/24AS215120Evolus IT Solutions GmbHRPKI Valid195.72.167.0
- 195.72.168.0/24AS219105AppFabric LLCRPKI Valid195.72.168.0
- 195.72.169.0/24AS13537Mega Colocation, Inc.RPKI Valid195.72.169.0
- 195.72.170.0/24AS5065Bunny CommunicationsRPKI Valid195.72.170.0
- 195.72.172.0/24AS275064MAC677RPKI Valid195.72.172.0
- 195.72.173.0/24AS147281Luckynet9 Private LimitedRPKI Valid195.72.173.0
- 195.72.175.0/24AS5065Bunny CommunicationsRPKI Valid195.72.175.0
- 195.72.176.0/22AS8447A1 Telekom Austria AGRPKI Valid195.72.176.0
- 195.72.184.0/24AS8796FASTNET DATA INCRPKI Valid195.72.184.0
- 195.72.185.0/24AS8796FASTNET DATA INCRPKI Valid195.72.185.0
- 195.72.186.0/24AS8796FASTNET DATA INCRPKI Valid195.72.186.0
- 195.72.187.0/24AS8796FASTNET DATA INCRPKI Valid195.72.187.0
- 195.72.188.0/24AS8796FASTNET DATA INCRPKI Valid195.72.188.0
- 195.72.189.0/24AS8796FASTNET DATA INCRPKI Valid195.72.189.0
- 195.72.190.0/24AS8796FASTNET DATA INCRPKI Valid195.72.190.0
- 195.72.191.0/24AS8796FASTNET DATA INCRPKI Valid195.72.191.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.