BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
213.146.160.0/19
Announced exactly
- 213.146.160.0/19AS174Cogent Communications, LLCRPKI Not found213.146.160.0
- Registry
- RIPE NCC · United States · Mar 27, 2001
- Delegated block
- 213.146.160.0 – 213.146.191.255
Covering routes
No less-specific route covers it.
More-specific routes
- 213.146.161.0/24AS213671Vision Fibre Media Ltd.RPKI Valid213.146.161.0
- 213.146.162.0/24AS56718Redshelf LtdRPKI Not found213.146.162.0
- 213.146.165.0/24AS214041Dokunmatik Ekran Teknolojileri Bilisim Insaat Tic. Ltd. Sti.RPKI Valid213.146.165.0
- 213.146.167.0/24AS209765ASPIRE MEDIA GROUP LIMITEDRPKI Not found213.146.167.0
- 213.146.169.0/24AS208905Exelera Telecom LtdRPKI Valid213.146.169.0
- 213.146.170.0/24AS208905Exelera Telecom LtdRPKI Valid213.146.170.0
- 213.146.171.0/24AS209765ASPIRE MEDIA GROUP LIMITEDRPKI Not found213.146.171.0
- 213.146.175.0/24AS62163IP River LimitedRPKI Valid213.146.175.0
- 213.146.176.0/22AS48945OPEN FIBRE NETWORKS (WHOLESALE) LIMITEDRPKI Not found213.146.176.0
- 213.146.181.0/24AS27377FTI CONSULTINGRPKI Not found213.146.181.0
- 213.146.184.0/24AS214041Dokunmatik Ekran Teknolojileri Bilisim Insaat Tic. Ltd. Sti.RPKI Valid213.146.184.0
- 213.146.186.0/23AS60981Triangle Networks LtdRPKI Valid213.146.186.0
- 213.146.190.0/24AS68233C1B Telekomunikasyon ve Internet Hiz. San. ve Tic. A.S.RPKI Valid213.146.190.0
On the internet, routes are announced as prefixes: an autonomous system tells its neighbours via BGP that it can deliver traffic for, say, 2.48.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.