BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
85.96.0.0/12
Announced exactly
- 85.96.0.0/12AS9121Turk Telekomunikasyon Anonim SirketiRPKI Valid85.96.0.0
- Registry
- RIPE NCC · Türkiye · Sep 20, 2004
- Delegated block
- 85.96.0.0 – 85.111.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 85.96.0.0/17AS9121Turk Telekomunikasyon Anonim SirketiRPKI Valid85.96.0.0
- 85.96.128.0/17AS9121Turk Telekomunikasyon Anonim SirketiRPKI Valid85.96.128.0
- 85.97.0.0/17AS9121Turk Telekomunikasyon Anonim SirketiRPKI Valid85.97.0.0
- 85.97.128.0/17AS9121Turk Telekomunikasyon Anonim SirketiRPKI Valid85.97.128.0
- 85.98.0.0/17AS9121Turk Telekomunikasyon Anonim SirketiRPKI Valid85.98.0.0
- 85.98.128.0/17AS9121Turk Telekomunikasyon Anonim SirketiRPKI Valid85.98.128.0
- 85.99.0.0/17AS9121Turk Telekomunikasyon Anonim SirketiRPKI Valid85.99.0.0
- 85.99.128.0/17AS9121Turk Telekomunikasyon Anonim SirketiRPKI Valid85.99.128.0
- 85.100.0.0/17AS9121Turk Telekomunikasyon Anonim SirketiRPKI Valid85.100.0.0
- 85.100.128.0/17AS9121Turk Telekomunikasyon Anonim SirketiRPKI Valid85.100.128.0
- 85.100.196.0/22AS47331TTNet A.S.RPKI Valid85.100.196.0
- 85.101.0.0/17AS9121Turk Telekomunikasyon Anonim SirketiRPKI Valid85.101.0.0
- 85.101.128.0/17AS9121Turk Telekomunikasyon Anonim SirketiRPKI Valid85.101.128.0
- 85.102.0.0/17AS9121Turk Telekomunikasyon Anonim SirketiRPKI Valid85.102.0.0
- 85.102.128.0/17AS9121Turk Telekomunikasyon Anonim SirketiRPKI Valid85.102.128.0
- 85.103.0.0/17AS9121Turk Telekomunikasyon Anonim SirketiRPKI Valid85.103.0.0
- 85.103.128.0/17AS9121Turk Telekomunikasyon Anonim SirketiRPKI Valid85.103.128.0
- 85.104.0.0/17AS9121Turk Telekomunikasyon Anonim SirketiRPKI Valid85.104.0.0
- 85.104.128.0/17AS9121Turk Telekomunikasyon Anonim SirketiRPKI Valid85.104.128.0
- 85.105.0.0/17AS9121Turk Telekomunikasyon Anonim SirketiRPKI Valid85.105.0.0
- 85.105.128.0/17AS9121Turk Telekomunikasyon Anonim SirketiRPKI Valid85.105.128.0
- 85.106.0.0/17AS9121Turk Telekomunikasyon Anonim SirketiRPKI Valid85.106.0.0
- 85.106.128.0/17AS9121Turk Telekomunikasyon Anonim SirketiRPKI Valid85.106.128.0
- 85.106.188.0/22AS47331TTNet A.S.RPKI Valid85.106.188.0
- 85.107.0.0/17AS9121Turk Telekomunikasyon Anonim SirketiRPKI Valid85.107.0.0
- 85.107.128.0/17AS9121Turk Telekomunikasyon Anonim SirketiRPKI Valid85.107.128.0
- 85.108.0.0/17AS9121Turk Telekomunikasyon Anonim SirketiRPKI Valid85.108.0.0
- 85.108.128.0/17AS9121Turk Telekomunikasyon Anonim SirketiRPKI Valid85.108.128.0
- 85.109.0.0/17AS9121Turk Telekomunikasyon Anonim SirketiRPKI Valid85.109.0.0
- 85.109.128.0/17AS9121Turk Telekomunikasyon Anonim SirketiRPKI Valid85.109.128.0
- 85.110.0.0/17AS9121Turk Telekomunikasyon Anonim SirketiRPKI Valid85.110.0.0
- 85.110.0.0/18AS47331TTNet A.S.RPKI Valid85.110.0.0
- 85.110.128.0/17AS9121Turk Telekomunikasyon Anonim SirketiRPKI Valid85.110.128.0
- 85.111.0.0/17AS9121Turk Telekomunikasyon Anonim SirketiRPKI Valid85.111.0.0
- 85.111.31.0/24AS9121Turk Telekomunikasyon Anonim SirketiRPKI Valid85.111.31.0
- 85.111.33.0/24AS9121Turk Telekomunikasyon Anonim SirketiRPKI Valid85.111.33.0
- 85.111.39.0/24AS9121Turk Telekomunikasyon Anonim SirketiRPKI Valid85.111.39.0
- 85.111.47.0/24AS9121Turk Telekomunikasyon Anonim SirketiRPKI Valid85.111.47.0
- 85.111.57.0/24AS9121Turk Telekomunikasyon Anonim SirketiRPKI Valid85.111.57.0
- 85.111.70.0/24AS9121Turk Telekomunikasyon Anonim SirketiRPKI Valid85.111.70.0
- 85.111.71.0/24AS9121Turk Telekomunikasyon Anonim SirketiRPKI Valid85.111.71.0
- 85.111.72.0/24AS9121Turk Telekomunikasyon Anonim SirketiRPKI Valid85.111.72.0
- 85.111.85.0/24AS9121Turk Telekomunikasyon Anonim SirketiRPKI Valid85.111.85.0
- 85.111.128.0/17AS9121Turk Telekomunikasyon Anonim SirketiRPKI Valid85.111.128.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.