BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
64.31.0.0/18
Announced exactly
- 64.31.0.0/18AS46475Limestone Networks, Inc.RPKI Valid64.31.0.0
- Registry
- ARIN · United States · Dec 27, 2010
- Delegated block
- 64.31.0.0 – 64.31.63.255
Covering routes
No less-specific route covers it.
More-specific routes
- 64.31.2.0/24AS46475Limestone Networks, Inc.RPKI Valid64.31.2.0
- 64.31.3.0/24AS46475Limestone Networks, Inc.RPKI Valid64.31.3.0
- 64.31.4.0/24AS46475Limestone Networks, Inc.RPKI Valid64.31.4.0
- 64.31.5.0/24AS46475Limestone Networks, Inc.RPKI Valid64.31.5.0
- 64.31.6.0/23AS46475Limestone Networks, Inc.RPKI Valid64.31.6.0
- 64.31.8.0/24AS46475Limestone Networks, Inc.RPKI Valid64.31.8.0
- 64.31.10.0/24AS46475Limestone Networks, Inc.RPKI Valid64.31.10.0
- 64.31.11.0/24AS46475Limestone Networks, Inc.RPKI Valid64.31.11.0
- 64.31.13.0/24AS46475Limestone Networks, Inc.RPKI Valid64.31.13.0
- 64.31.14.0/24AS46475Limestone Networks, Inc.RPKI Valid64.31.14.0
- 64.31.16.0/24AS46475Limestone Networks, Inc.RPKI Valid64.31.16.0
- 64.31.17.0/24AS46475Limestone Networks, Inc.RPKI Valid64.31.17.0
- 64.31.18.0/24AS46475Limestone Networks, Inc.RPKI Valid64.31.18.0
- 64.31.19.0/24AS46475Limestone Networks, Inc.RPKI Valid64.31.19.0
- 64.31.20.0/24AS46475Limestone Networks, Inc.RPKI Valid64.31.20.0
- 64.31.22.0/24AS46475Limestone Networks, Inc.RPKI Valid64.31.22.0
- 64.31.23.0/24AS46475Limestone Networks, Inc.RPKI Valid64.31.23.0
- 64.31.24.0/24AS46475Limestone Networks, Inc.RPKI Valid64.31.24.0
- 64.31.25.0/24AS46475Limestone Networks, Inc.RPKI Valid64.31.25.0
- 64.31.27.0/24AS46475Limestone Networks, Inc.RPKI Valid64.31.27.0
- 64.31.28.0/24AS46475Limestone Networks, Inc.RPKI Valid64.31.28.0
- 64.31.29.0/24AS46475Limestone Networks, Inc.RPKI Valid64.31.29.0
- 64.31.30.0/24AS46475Limestone Networks, Inc.RPKI Valid64.31.30.0
- 64.31.31.0/24AS46475Limestone Networks, Inc.RPKI Valid64.31.31.0
- 64.31.32.0/24AS46475Limestone Networks, Inc.RPKI Valid64.31.32.0
- 64.31.33.0/24AS46475Limestone Networks, Inc.RPKI Valid64.31.33.0
- 64.31.34.0/24AS46475Limestone Networks, Inc.RPKI Valid64.31.34.0
- 64.31.35.0/24AS46475Limestone Networks, Inc.RPKI Valid64.31.35.0
- 64.31.36.0/24AS46475Limestone Networks, Inc.RPKI Valid64.31.36.0
- 64.31.37.0/24AS46475Limestone Networks, Inc.RPKI Valid64.31.37.0
- 64.31.38.0/24AS46475Limestone Networks, Inc.RPKI Valid64.31.38.0
- 64.31.39.0/24AS46475Limestone Networks, Inc.RPKI Valid64.31.39.0
- 64.31.40.0/24AS46475Limestone Networks, Inc.RPKI Valid64.31.40.0
- 64.31.42.0/24AS46475Limestone Networks, Inc.RPKI Valid64.31.42.0
- 64.31.43.0/24AS46475Limestone Networks, Inc.RPKI Valid64.31.43.0
- 64.31.44.0/24AS46475Limestone Networks, Inc.RPKI Valid64.31.44.0
- 64.31.47.0/24AS46475Limestone Networks, Inc.RPKI Valid64.31.47.0
- 64.31.48.0/24AS46475Limestone Networks, Inc.RPKI Valid64.31.48.0
- 64.31.49.0/24AS46475Limestone Networks, Inc.RPKI Valid64.31.49.0
- 64.31.51.0/24AS46475Limestone Networks, Inc.RPKI Valid64.31.51.0
- 64.31.52.0/24AS46475Limestone Networks, Inc.RPKI Valid64.31.52.0
- 64.31.53.0/24AS46475Limestone Networks, Inc.RPKI Valid64.31.53.0
- 64.31.54.0/24AS46475Limestone Networks, Inc.RPKI Valid64.31.54.0
- 64.31.55.0/24AS46475Limestone Networks, Inc.RPKI Valid64.31.55.0
- 64.31.56.0/24AS46475Limestone Networks, Inc.RPKI Valid64.31.56.0
- 64.31.57.0/24AS46475Limestone Networks, Inc.RPKI Valid64.31.57.0
- 64.31.58.0/24AS46475Limestone Networks, Inc.RPKI Valid64.31.58.0
- 64.31.59.0/24AS46475Limestone Networks, Inc.RPKI Valid64.31.59.0
- 64.31.60.0/24AS46475Limestone Networks, Inc.RPKI Valid64.31.60.0
- 64.31.61.0/24AS46475Limestone Networks, Inc.RPKI Valid64.31.61.0
- 64.31.62.0/24AS46475Limestone Networks, Inc.RPKI Valid64.31.62.0
- 64.31.63.0/24AS136258BrainStorm Network, IncRPKI Valid64.31.63.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.