BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
64.139.0.0/18
Announced exactly
- 64.139.0.0/18AS3257GTT-BACKBONE GTTRPKI Valid64.139.0.0
- Registry
- ARIN · United States · Aug 3, 2000
- Delegated block
- 64.139.0.0 – 64.139.63.255
Covering routes
No less-specific route covers it.
More-specific routes
- 64.139.0.0/22AS2914NTT America, Inc.RPKI Valid64.139.0.0
- 64.139.4.0/22AS8053IFX Networks Venezuela C.A.RPKI Valid64.139.4.0
- 64.139.8.0/24AS401783TOKALA COMMUNICATIONS INC.RPKI Valid64.139.8.0
- 64.139.9.0/24AS2914NTT America, Inc.RPKI Valid64.139.9.0
- 64.139.11.0/24AS5065Bunny CommunicationsRPKI Valid64.139.11.0
- 64.139.12.0/24AS2914NTT America, Inc.RPKI Valid64.139.12.0
- 64.139.13.0/24AS2914NTT America, Inc.RPKI Valid64.139.13.0
- 64.139.14.0/24AS401783TOKALA COMMUNICATIONS INC.RPKI Valid64.139.14.0
- 64.139.15.0/24AS2914NTT America, Inc.RPKI Valid64.139.15.0
- 64.139.16.0/24AS7459Grande Communications Networks, LLCRPKI Valid64.139.16.0
- 64.139.17.0/24AS7459Grande Communications Networks, LLCRPKI Valid64.139.17.0
- 64.139.18.0/24AS7459Grande Communications Networks, LLCRPKI Valid64.139.18.0
- 64.139.19.0/24AS7459Grande Communications Networks, LLCRPKI Valid64.139.19.0
- 64.139.20.0/24AS7459Grande Communications Networks, LLCRPKI Valid64.139.20.0
- 64.139.21.0/24AS7459Grande Communications Networks, LLCRPKI Valid64.139.21.0
- 64.139.22.0/24AS7459Grande Communications Networks, LLCRPKI Valid64.139.22.0
- 64.139.23.0/24AS7459Grande Communications Networks, LLCRPKI Valid64.139.23.0
- 64.139.24.0/24AS7459Grande Communications Networks, LLCRPKI Valid64.139.24.0
- 64.139.25.0/24AS7459Grande Communications Networks, LLCRPKI Valid64.139.25.0
- 64.139.26.0/24AS7459Grande Communications Networks, LLCRPKI Valid64.139.26.0
- 64.139.27.0/24AS7459Grande Communications Networks, LLCRPKI Valid64.139.27.0
- 64.139.28.0/24AS7459Grande Communications Networks, LLCRPKI Valid64.139.28.0
- 64.139.29.0/24AS7459Grande Communications Networks, LLCRPKI Valid64.139.29.0
- 64.139.30.0/24AS7459Grande Communications Networks, LLCRPKI Valid64.139.30.0
- 64.139.31.0/24AS7459Grande Communications Networks, LLCRPKI Valid64.139.31.0
- 64.139.32.0/23AS3320DTAG Internet service provider operationsRPKI Valid64.139.32.0
- 64.139.34.0/23AS3320DTAG Internet service provider operationsRPKI Valid64.139.34.0
- 64.139.36.0/23AS9304HUTCHISON-AS-AP HGC Global Communications LimitedRPKI Valid64.139.36.0
- 64.139.38.0/23AS9304HUTCHISON-AS-AP HGC Global Communications LimitedRPKI Valid64.139.38.0
- 64.139.40.0/23AS30058FDCservers.netRPKI Valid64.139.40.0
- 64.139.42.0/23AS10753Level 3 Parent, LLCRPKI Valid64.139.42.0
- 64.139.44.0/23AS212238CDNEXTRPKI Valid64.139.44.0
- 64.139.46.0/23AS10753Level 3 Parent, LLCRPKI Valid64.139.46.0
- 64.139.48.0/23AS10753Level 3 Parent, LLCRPKI Valid64.139.48.0
- 64.139.50.0/23AS30058FDCservers.netRPKI Valid64.139.50.0
- 64.139.52.0/23AS30058FDCservers.netRPKI Valid64.139.52.0
- 64.139.54.0/23AS30058FDCservers.netRPKI Valid64.139.54.0
- 64.139.56.0/23AS212238CDNEXTRPKI Valid64.139.56.0
- 64.139.58.0/23AS30058FDCservers.netRPKI Valid64.139.58.0
- 64.139.60.0/23AS10753Level 3 Parent, LLCRPKI Valid64.139.60.0
- 64.139.62.0/23AS1257TELE2RPKI Valid64.139.62.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.