BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
94.103.160.0/20
Announced exactly
- 94.103.160.0/20AS12586GHOSTnet GmbHRPKI Valid94.103.160.0
- Registry
- RIPE NCC · Germany · Sep 15, 2008
- Delegated block
- 94.103.160.0 – 94.103.175.255
Covering routes
No less-specific route covers it.
More-specific routes
- 94.103.160.0/24AS12586GHOSTnet GmbHRPKI Valid94.103.160.0
- 94.103.161.0/24AS12586GHOSTnet GmbHRPKI Valid94.103.161.0
- 94.103.162.0/24AS12586GHOSTnet GmbHRPKI Valid94.103.162.0
- 94.103.163.0/24AS146943Tier 4 Cloud ServicesRPKI Valid94.103.163.0
- 94.103.164.0/24AS214971Jann MietznerRPKI Valid94.103.164.0
- 94.103.165.0/24AS32132Fiber Optic Cable Network LLCRPKI Valid94.103.165.0
- 94.103.166.0/24AS212353Crelativity LimitedRPKI Valid94.103.166.0
- 94.103.167.0/24AS209874Tech Tide Portugal Unipessoal LDARPKI Valid94.103.167.0
- 94.103.168.0/24AS214919Kabat OURPKI Valid94.103.168.0
- 94.103.169.0/24AS215439PLAY2GO INTERNATIONAL LIMITEDRPKI Valid94.103.169.0
- 94.103.170.0/24AS44486Oliver Horscht trading as "SYNLINQ"RPKI Valid94.103.170.0
- 94.103.172.0/24AS44486Oliver Horscht trading as "SYNLINQ"RPKI Valid94.103.172.0
- 94.103.173.0/24AS44486Oliver Horscht trading as "SYNLINQ"RPKI Valid94.103.173.0
- 94.103.174.0/24AS215224NovoServe B.V.RPKI Valid94.103.174.0
- 94.103.175.0/24AS12586GHOSTnet GmbHRPKI Valid94.103.175.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.