BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
86.53.0.0/16
Announced exactly
- 86.53.0.0/16AS3257GTT Communications Inc.RPKI Not found86.53.0.0
- Registry
- RIPE NCC · United Kingdom · May 10, 2005
- Delegated block
- 86.53.0.0 – 86.53.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 86.53.0.0/23AS3257GTT Communications Inc.RPKI Not found86.53.0.0
- 86.53.5.0/24AS30058FDCservers.netRPKI Valid86.53.5.0
- 86.53.9.0/24AS3257GTT Communications Inc.RPKI Not found86.53.9.0
- 86.53.10.0/23AS3257GTT Communications Inc.RPKI Not found86.53.10.0
- 86.53.22.0/24AS30058FDCservers.netRPKI Valid86.53.22.0
- 86.53.25.0/24AS30058FDCservers.netRPKI Valid86.53.25.0
- 86.53.26.0/24AS30058FDCservers.netRPKI Valid86.53.26.0
- 86.53.28.0/24AS3257GTT Communications Inc.RPKI Not found86.53.28.0
- 86.53.44.0/24AS401783TOKALA COMMUNICATIONS INC.RPKI Valid86.53.44.0
- 86.53.45.0/24AS401783TOKALA COMMUNICATIONS INC.RPKI Valid86.53.45.0
- 86.53.72.0/24AS401783TOKALA COMMUNICATIONS INC.RPKI Valid86.53.72.0
- 86.53.75.0/24AS401783TOKALA COMMUNICATIONS INC.RPKI Valid86.53.75.0
- 86.53.96.0/22AS3257GTT Communications Inc.RPKI Not found86.53.96.0
- 86.53.100.0/24AS3257GTT Communications Inc.RPKI Not found86.53.100.0
- 86.53.104.0/21AS3257GTT Communications Inc.RPKI Not found86.53.104.0
- 86.53.132.0/24AS3257GTT Communications Inc.RPKI Not found86.53.132.0
- 86.53.134.0/23AS3257GTT Communications Inc.RPKI Not found86.53.134.0
- 86.53.140.0/24AS3257GTT Communications Inc.RPKI Not found86.53.140.0
- 86.53.144.0/24AS5065Bunny CommunicationsRPKI Valid86.53.144.0
- 86.53.145.0/24AS5065Bunny CommunicationsRPKI Valid86.53.145.0
- 86.53.147.0/24AS212755ExaCloud Factory, S.L.RPKI Valid86.53.147.0
- 86.53.148.0/22AS3257GTT Communications Inc.RPKI Not found86.53.148.0
- 86.53.152.0/22AS8447A1 Telekom Austria AGRPKI Valid86.53.152.0
- 86.53.160.0/22AS3257GTT Communications Inc.RPKI Valid86.53.160.0
- 86.53.164.0/24AS50118Caribbean Telecom S.ARPKI Valid86.53.164.0
- 86.53.165.0/24AS50118Caribbean Telecom S.ARPKI Valid86.53.165.0
- 86.53.166.0/24AS30058FDCservers.netRPKI Valid86.53.166.0
- 86.53.180.0/22AS3257GTT Communications Inc.RPKI Valid86.53.180.0
- 86.53.184.0/21AS3257GTT Communications Inc.RPKI Valid86.53.184.0
- 86.53.204.0/22AS3257GTT Communications Inc.RPKI Not found86.53.204.0
- 86.53.252.0/24AS3257GTT Communications Inc.RPKI Not found86.53.252.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.