BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
82.110.0.0/16
Announced exactly
- 82.110.0.0/16AS3257GTT Communications Inc.RPKI Not found82.110.0.0
- Registry
- RIPE NCC · United Kingdom · Oct 31, 2003
- Delegated block
- 82.110.0.0 – 82.110.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 82.110.0.0/19AS3491PCCW Global (HK) Ltd.RPKI Valid82.110.0.0
- 82.110.32.0/20AS3257GTT Communications Inc.RPKI Valid82.110.32.0
- 82.110.48.0/24AS212477RoyaleHosting BVRPKI Valid82.110.48.0
- 82.110.49.0/24AS212477RoyaleHosting BVRPKI Valid82.110.49.0
- 82.110.50.0/24AS9304HGC Global Communications LimitedRPKI Valid82.110.50.0
- 82.110.52.0/24AS218829Digital IT Creations LtdRPKI Valid82.110.52.0
- 82.110.53.0/24AS152606LINK4 COMMUNICATIONRPKI Valid82.110.53.0
- 82.110.54.0/24AS152606LINK4 COMMUNICATIONRPKI Valid82.110.54.0
- 82.110.60.0/24AS212238Datacamp LimitedRPKI Valid82.110.60.0
- 82.110.64.0/19AS3491PCCW Global (HK) Ltd.RPKI Valid82.110.64.0
- 82.110.98.0/24AS198566MAMUT RAHAL SOFTWARE - FZCORPKI Valid82.110.98.0
- 82.110.105.0/24AS198566MAMUT RAHAL SOFTWARE - FZCORPKI Valid82.110.105.0
- 82.110.106.0/23AS206766Travchis LLCRPKI Valid82.110.106.0
- 82.110.108.0/22AS197752Asia Core LimitedRPKI Valid82.110.108.0
- 82.110.110.0/23AS197752Asia Core LimitedRPKI Valid82.110.110.0
- 82.110.110.0/24AS197752Asia Core LimitedRPKI Valid82.110.110.0
- 82.110.112.0/24AS219185NARWHAL NETTECH LIMITEDRPKI Valid82.110.112.0
- 82.110.114.0/23AS206916Southwest Network CorporationRPKI Valid82.110.114.0
- 82.110.115.0/24AS206916Southwest Network CorporationRPKI Valid82.110.115.0
- 82.110.120.0/22AS174Cogent Communications, LLCRPKI Valid82.110.120.0
- 82.110.124.0/22AS16509Amazon.com, Inc.RPKI Valid82.110.124.0
- 82.110.128.0/22AS402309AuroraNetworks LLCRPKI Valid82.110.128.0
- 82.110.128.0/24AS402309AuroraNetworks LLCRPKI Valid82.110.128.0
- 82.110.132.0/22AS200260Debugged LtdRPKI Valid82.110.132.0
- 82.110.132.0/24AS200260Debugged LtdRPKI Valid82.110.132.0
- 82.110.133.0/24AS200260Debugged LtdRPKI Valid82.110.133.0
- 82.110.134.0/24AS200260Debugged LtdRPKI Valid82.110.134.0
- 82.110.135.0/24AS200260Debugged LtdRPKI Valid82.110.135.0
- 82.110.146.0/24AS210809UniFlex Systems LimitedRPKI Valid82.110.146.0
- 82.110.157.0/24AS199741TransitX LtdRPKI Valid82.110.157.0
- 82.110.160.0/19AS3491PCCW Global (HK) Ltd.RPKI Valid82.110.160.0
- 82.110.192.0/19AS3491PCCW Global (HK) Ltd.RPKI Valid82.110.192.0
- 82.110.224.0/24AS13537Mega Colocation, Inc.RPKI Valid82.110.224.0
- 82.110.225.0/24AS9304HGC Global Communications LimitedRPKI Valid82.110.225.0
- 82.110.228.0/24AS9304HGC Global Communications LimitedRPKI Valid82.110.228.0
- 82.110.232.0/24AS198566MAMUT RAHAL SOFTWARE - FZCORPKI Valid82.110.232.0
- 82.110.234.0/23AS142433DATAWAVE GLOBAL LLCRPKI Valid82.110.234.0
- 82.110.234.0/24AS142433DATAWAVE GLOBAL LLCRPKI Valid82.110.234.0
- 82.110.235.0/24AS142433DATAWAVE GLOBAL LLCRPKI Valid82.110.235.0
- 82.110.240.0/20AS54004Cablevision Lightpath LLCRPKI Valid82.110.240.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.