BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
77.67.0.0/17
Announced exactly
- 77.67.0.0/17AS3257GTT-BACKBONE GTTRPKI Valid77.67.0.0
- Registry
- RIPE NCC · United States · Jan 30, 2007
- Delegated block
- 77.67.0.0 – 77.67.127.255
Covering routes
No less-specific route covers it.
More-specific routes
- 77.67.1.0/24AS215030ASPIREHOSTINGRPKI Valid77.67.1.0
- 77.67.5.0/25AS394977TAKE-TWO INTERACTIVE SOFTWARE, INC.RPKI Invalid77.67.5.0
- 77.67.6.0/24AS49453GLOBALLAYERRPKI Valid77.67.6.0
- 77.67.7.0/24AS148982BQIT-AS-AP Bijie Qiulin Information TechnologyRPKI Valid77.67.7.0
- 77.67.8.0/24AS208450MEGAHOST_RPKI Valid77.67.8.0
- 77.67.9.0/24AS35661VIRTUASYS-EU Lift weight. Push bytes. Never drop. Repeat.RPKI Valid77.67.9.0
- 77.67.11.0/24AS198566MAMUTRAHALRPKI Valid77.67.11.0
- 77.67.15.0/24AS142146SANDHILL-AS-AP SANDHILL SOLUTION PTE. LTD.RPKI Valid77.67.15.0
- 77.67.16.0/24AS152368IDNIC-JEJARINGBERSAMA-AS-ID PT Perwira Pedjoeang NusantaraRPKI Valid77.67.16.0
- 77.67.17.0/24AS21859Zenlayer IncRPKI Valid77.67.17.0
- 77.67.18.0/24AS206069CORNSEEDRPKI Valid77.67.18.0
- 77.67.22.0/24AS402456BjerkerudRPKI Valid77.67.22.0
- 77.67.23.0/24AS57043HOSTKEY-ASRPKI Valid77.67.23.0
- 77.67.26.0/24AS25369BANDWIDTH-ASRPKI Valid77.67.26.0
- 77.67.28.0/24AS16276OVHRPKI Valid77.67.28.0
- 77.67.29.0/24AS213570ROWENIXRPKI Valid77.67.29.0
- 77.67.33.0/24AS3257GTT-BACKBONE GTTRPKI Valid77.67.33.0
- 77.67.35.0/24AS3257GTT-BACKBONE GTTRPKI Valid77.67.35.0
- 77.67.36.0/22AS54004Cablevision Lightpath LLCRPKI Valid77.67.36.0
- 77.67.49.0/24AS29802HIVELOCITY, Inc.RPKI Valid77.67.49.0
- 77.67.58.0/24AS395954Leaseweb USA, Inc.RPKI Valid77.67.58.0
- 77.67.59.0/24AS44803WEBDOCK-ASRPKI Valid77.67.59.0
- 77.67.88.0/24AS143151GSERVERS, LLCRPKI Valid77.67.88.0
- 77.67.89.0/24AS57043HOSTKEY-ASRPKI Valid77.67.89.0
- 77.67.92.0/24AS9304HUTCHISON-AS-AP HGC Global Communications LimitedRPKI Valid77.67.92.0
- 77.67.100.0/24AS21859Zenlayer IncRPKI Valid77.67.100.0
- 77.67.101.0/24AS8001Cologix, IncRPKI Invalid77.67.101.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.