BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
81.168.0.0/17
Announced exactly
- 81.168.0.0/17AS8851EDGE ta GCI ComRPKI Valid81.168.0.0
- Registry
- RIPE NCC · United Kingdom · Apr 4, 2003
- Delegated block
- 81.168.0.0 – 81.168.127.255
Covering routes
No less-specific route covers it.
More-specific routes
- 81.168.7.0/24AS12200Rackspace HostingRPKI Valid81.168.7.0
- 81.168.8.0/24AS213607WORLD-FIRST-COMMUNICATION-LTDRPKI Valid81.168.8.0
- 81.168.9.0/24AS213607WORLD-FIRST-COMMUNICATION-LTDRPKI Valid81.168.9.0
- 81.168.11.0/24AS213607WORLD-FIRST-COMMUNICATION-LTDRPKI Valid81.168.11.0
- 81.168.16.0/24AS213607WORLD-FIRST-COMMUNICATION-LTDRPKI Valid81.168.16.0
- 81.168.18.0/24AS213476LITLINKRPKI Valid81.168.18.0
- 81.168.20.0/24AS25369BANDWIDTH-ASRPKI Valid81.168.20.0
- 81.168.29.0/24AS213607WORLD-FIRST-COMMUNICATION-LTDRPKI Valid81.168.29.0
- 81.168.32.0/24AS16276OVHRPKI Valid81.168.32.0
- 81.168.35.0/24AS212783FR-FEREZ-ASRPKI Valid81.168.35.0
- 81.168.38.0/24AS206766PROXYWINGRPKI Valid81.168.38.0
- 81.168.41.0/24AS396356Latitude.shRPKI Valid81.168.41.0
- 81.168.42.0/24AS56264TOMATOWEB-BD Tomato Web Pvt LimitedRPKI Valid81.168.42.0
- 81.168.43.0/24AS56264TOMATOWEB-BD Tomato Web Pvt LimitedRPKI Valid81.168.43.0
- 81.168.50.0/24AS212384INTERNET-3RPKI Valid81.168.50.0
- 81.168.60.0/24AS56264TOMATOWEB-BD Tomato Web Pvt LimitedRPKI Valid81.168.60.0
- 81.168.62.0/24AS39948612651980 CANADA INC.RPKI Valid81.168.62.0
- 81.168.63.0/24AS210476MOON-NETRPKI Valid81.168.63.0
- 81.168.67.0/24AS211826ISTQSERVERS-ASRPKI Valid81.168.67.0
- 81.168.68.0/24AS150670WLXLIMITED-AS-AP WLX LimitedRPKI Valid81.168.68.0
- 81.168.70.0/24AS207267BIRSUNUCUM-ASNRPKI Valid81.168.70.0
- 81.168.76.0/24AS63902SHINETEL-AS-TW SHINE TELECOM CO., LTD.RPKI Valid81.168.76.0
- 81.168.78.0/24AS56264TOMATOWEB-BD Tomato Web Pvt LimitedRPKI Valid81.168.78.0
- 81.168.79.0/24AS63902SHINETEL-AS-TW SHINE TELECOM CO., LTD.RPKI Valid81.168.79.0
- 81.168.80.0/24AS16276OVHRPKI Valid81.168.80.0
- 81.168.83.0/24AS20860IOMART-ASRPKI Valid81.168.83.0
- 81.168.85.0/24AS213607WORLD-FIRST-COMMUNICATION-LTDRPKI Valid81.168.85.0
- 81.168.87.0/24AS219121CLOUFINITYRPKI Valid81.168.87.0
- 81.168.100.0/24AS215968DATACOM-JVRPKI Valid81.168.100.0
- 81.168.101.0/24AS213607WORLD-FIRST-COMMUNICATION-LTDRPKI Valid81.168.101.0
- 81.168.104.0/24AS25369BANDWIDTH-ASRPKI Valid81.168.104.0
- 81.168.105.0/24AS200074ASSWHRPKI Valid81.168.105.0
- 81.168.109.0/24AS9304HUTCHISON-AS-AP HGC Global Communications LimitedRPKI Valid81.168.109.0
- 81.168.111.0/24AS212895ROUTE64_ORGRPKI Valid81.168.111.0
- 81.168.112.0/24AS25369BANDWIDTH-ASRPKI Valid81.168.112.0
- 81.168.116.0/24AS9294GNETINC-AS-AP GNET INC.RPKI Valid81.168.116.0
- 81.168.117.0/24AS211373INTERNET-1RPKI Valid81.168.117.0
- 81.168.119.0/24AS20860IOMART-ASRPKI Valid81.168.119.0
- 81.168.120.0/24AS25369BANDWIDTH-ASRPKI Valid81.168.120.0
- 81.168.123.0/24AS9009M247RPKI Valid81.168.123.0
- 81.168.125.0/24AS197246BELGRAVIA-ASRPKI Valid81.168.125.0
- 81.168.126.0/24AS399073BUNNY TECHNOLOGY LLCRPKI Valid81.168.126.0
- 81.168.127.0/24AS3257GTT-BACKBONE GTTRPKI Valid81.168.127.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.