BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
85.87.0.0/16
Announced exactly
- 85.87.0.0/16AS12338Euskaltel S.A.RPKI Valid85.87.0.0
- Registry
- RIPE NCC · Spain · Oct 22, 2004
- Delegated block
- 85.84.0.0 – 85.87.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 85.87.0.0/23AS15704XTRA TELECOM S.A.RPKI Valid85.87.0.0
- 85.87.2.0/23AS15704XTRA TELECOM S.A.RPKI Valid85.87.2.0
- 85.87.4.0/23AS15704XTRA TELECOM S.A.RPKI Valid85.87.4.0
- 85.87.6.0/23AS15704XTRA TELECOM S.A.RPKI Valid85.87.6.0
- 85.87.8.0/22AS15704XTRA TELECOM S.A.RPKI Valid85.87.8.0
- 85.87.12.0/22AS15704XTRA TELECOM S.A.RPKI Valid85.87.12.0
- 85.87.16.0/23AS15704XTRA TELECOM S.A.RPKI Valid85.87.16.0
- 85.87.18.0/23AS15704XTRA TELECOM S.A.RPKI Valid85.87.18.0
- 85.87.20.0/23AS15704XTRA TELECOM S.A.RPKI Valid85.87.20.0
- 85.87.22.0/23AS15704XTRA TELECOM S.A.RPKI Valid85.87.22.0
- 85.87.24.0/24AS12338Euskaltel S.A.RPKI Valid85.87.24.0
- 85.87.25.0/24AS12338Euskaltel S.A.RPKI Valid85.87.25.0
- 85.87.26.0/24AS12338Euskaltel S.A.RPKI Valid85.87.26.0
- 85.87.27.0/24AS12338Euskaltel S.A.RPKI Valid85.87.27.0
- 85.87.40.0/24AS12338Euskaltel S.A.RPKI Valid85.87.40.0
- 85.87.43.0/24AS12338Euskaltel S.A.RPKI Valid85.87.43.0
- 85.87.64.0/22AS12338Euskaltel S.A.RPKI Valid85.87.64.0
- 85.87.68.0/24AS12338Euskaltel S.A.RPKI Valid85.87.68.0
- 85.87.69.0/24AS12338Euskaltel S.A.RPKI Valid85.87.69.0
- 85.87.70.0/24AS12338Euskaltel S.A.RPKI Valid85.87.70.0
- 85.87.71.0/24AS12338Euskaltel S.A.RPKI Valid85.87.71.0
- 85.87.72.0/22AS12338Euskaltel S.A.RPKI Valid85.87.72.0
- 85.87.84.0/22AS12338Euskaltel S.A.RPKI Valid85.87.84.0
- 85.87.96.0/22AS12338Euskaltel S.A.RPKI Valid85.87.96.0
- 85.87.100.0/22AS12338Euskaltel S.A.RPKI Valid85.87.100.0
- 85.87.120.0/22AS15704XTRA TELECOM S.A.RPKI Valid85.87.120.0
- 85.87.124.0/22AS12338Euskaltel S.A.RPKI Valid85.87.124.0
- 85.87.128.0/21AS15704XTRA TELECOM S.A.RPKI Valid85.87.128.0
- 85.87.136.0/21AS15704XTRA TELECOM S.A.RPKI Valid85.87.136.0
- 85.87.144.0/21AS15704XTRA TELECOM S.A.RPKI Valid85.87.144.0
- 85.87.152.0/21AS15704XTRA TELECOM S.A.RPKI Valid85.87.152.0
- 85.87.160.0/22AS15704XTRA TELECOM S.A.RPKI Valid85.87.160.0
- 85.87.164.0/22AS15704XTRA TELECOM S.A.RPKI Valid85.87.164.0
- 85.87.176.0/22AS15704XTRA TELECOM S.A.RPKI Valid85.87.176.0
- 85.87.180.0/22AS15704XTRA TELECOM S.A.RPKI Valid85.87.180.0
- 85.87.184.0/22AS15704XTRA TELECOM S.A.RPKI Valid85.87.184.0
- 85.87.188.0/22AS15704XTRA TELECOM S.A.RPKI Valid85.87.188.0
- 85.87.192.0/24AS12338Euskaltel S.A.RPKI Valid85.87.192.0
- 85.87.193.0/24AS12338Euskaltel S.A.RPKI Valid85.87.193.0
- 85.87.194.0/24AS12338Euskaltel S.A.RPKI Valid85.87.194.0
- 85.87.195.0/24AS12338Euskaltel S.A.RPKI Valid85.87.195.0
- 85.87.196.0/24AS12338Euskaltel S.A.RPKI Valid85.87.196.0
- 85.87.204.0/24AS12338Euskaltel S.A.RPKI Valid85.87.204.0
- 85.87.216.0/23AS15704XTRA TELECOM S.A.RPKI Valid85.87.216.0
- 85.87.220.0/23AS15704XTRA TELECOM S.A.RPKI Valid85.87.220.0
On the internet, routes are announced as prefixes: an autonomous system tells its neighbours via BGP that it can deliver traffic for, say, 128.139.0.0/16. 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.