BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
83.245.0.0/17
Announced exactly
- 83.245.0.0/17AS3257GTT-BACKBONE GTTRPKI Valid83.245.0.0
- Registry
- RIPE NCC · United Kingdom · Apr 14, 2004
- Delegated block
- 83.245.0.0 – 83.245.127.255
Covering routes
No less-specific route covers it.
More-specific routes
- 83.245.0.0/23AS3257GTT-BACKBONE GTTRPKI Valid83.245.0.0
- 83.245.3.0/24AS199707XINGTONGHUIRPKI Valid83.245.3.0
- 83.245.5.0/24AS25198Unmetered Cloud and Dedicated Servers ProviderRPKI Valid83.245.5.0
- 83.245.8.0/24AS6079RCNRPKI Valid83.245.8.0
- 83.245.13.0/24AS13335Cloudflare, Inc.RPKI Valid83.245.13.0
- 83.245.16.0/21AS2856BT-UK-AS BTnet UK Regional networkRPKI Valid83.245.16.0
- 83.245.24.0/22AS2856BT-UK-AS BTnet UK Regional networkRPKI Valid83.245.24.0
- 83.245.28.0/22AS203410COLOBIXRPKI Valid83.245.28.0
- 83.245.32.0/22AS3356Level 3 Parent, LLCRPKI Valid83.245.32.0
- 83.245.36.0/22AS174Cogent Communications, LLCRPKI Valid83.245.36.0
- 83.245.56.0/23AS3257GTT-BACKBONE GTTRPKI Valid83.245.56.0
- 83.245.56.0/24AS3257GTT-BACKBONE GTTRPKI Valid83.245.56.0
- 83.245.57.0/24AS3257GTT-BACKBONE GTTRPKI Valid83.245.57.0
- 83.245.59.0/24AS62513GoCodeIT IncRPKI Valid83.245.59.0
- 83.245.60.0/24AS62513GoCodeIT IncRPKI Valid83.245.60.0
- 83.245.61.0/24AS215541AS-KRUSESECRPKI Valid83.245.61.0
- 83.245.62.0/23AS3257GTT-BACKBONE GTTRPKI Valid83.245.62.0
- 83.245.64.0/24AS198584PIO-HOSTINGRPKI Valid83.245.64.0
- 83.245.65.0/24AS203156RELAYIFY-LLCRPKI Valid83.245.65.0
- 83.245.66.0/24AS13335Cloudflare, Inc.RPKI Valid83.245.66.0
- 83.245.67.0/24AS13335Cloudflare, Inc.RPKI Valid83.245.67.0
- 83.245.69.0/24AS3356Level 3 Parent, LLCRPKI Valid83.245.69.0
- 83.245.70.0/24AS3356Level 3 Parent, LLCRPKI Valid83.245.70.0
- 83.245.71.0/24AS203156RELAYIFY-LLCRPKI Valid83.245.71.0
- 83.245.79.0/24AS35831VNETRIX-ASRPKI Valid83.245.79.0
- 83.245.80.0/20AS3356Level 3 Parent, LLCRPKI Valid83.245.80.0
- 83.245.104.0/22AS174Cogent Communications, LLCRPKI Valid83.245.104.0
- 83.245.109.0/24AS3257GTT-BACKBONE GTTRPKI Valid83.245.109.0
On the internet, routes are announced as prefixes: an autonomous system tells its neighbours via BGP that it can deliver traffic for, say, 193.166.0.0/15. 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.