BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
179.51.64.0/20
Announced exactly
- 179.51.64.0/20AS52471COLUMBUS NETWORKS DOMINICANA, S.A.RPKI Valid179.51.64.0
- Registry
- LACNIC · Dominican Republic · Jan 20, 2014
- Delegated block
- 179.51.64.0 – 179.51.79.255
Covering routes
No less-specific route covers it.
More-specific routes
- 179.51.65.0/24AS52471COLUMBUS NETWORKS DOMINICANA, S.A.RPKI Valid179.51.65.0
- 179.51.66.0/24AS52471COLUMBUS NETWORKS DOMINICANA, S.A.RPKI Valid179.51.66.0
- 179.51.67.0/24AS52471COLUMBUS NETWORKS DOMINICANA, S.A.RPKI Valid179.51.67.0
- 179.51.68.0/24AS52471COLUMBUS NETWORKS DOMINICANA, S.A.RPKI Valid179.51.68.0
- 179.51.69.0/24AS52471COLUMBUS NETWORKS DOMINICANA, S.A.RPKI Valid179.51.69.0
- 179.51.70.0/24AS52471COLUMBUS NETWORKS DOMINICANA, S.A.RPKI Valid179.51.70.0
- 179.51.71.0/24AS52471COLUMBUS NETWORKS DOMINICANA, S.A.RPKI Valid179.51.71.0
- 179.51.72.0/24AS52471COLUMBUS NETWORKS DOMINICANA, S.A.RPKI Valid179.51.72.0
- 179.51.73.0/24AS52471COLUMBUS NETWORKS DOMINICANA, S.A.RPKI Valid179.51.73.0
- 179.51.74.0/24AS52471COLUMBUS NETWORKS DOMINICANA, S.A.RPKI Valid179.51.74.0
- 179.51.75.0/24AS52471COLUMBUS NETWORKS DOMINICANA, S.A.RPKI Valid179.51.75.0
- 179.51.76.0/24AS52471COLUMBUS NETWORKS DOMINICANA, S.A.RPKI Valid179.51.76.0
- 179.51.77.0/24AS52471COLUMBUS NETWORKS DOMINICANA, S.A.RPKI Valid179.51.77.0
- 179.51.78.0/24AS52471COLUMBUS NETWORKS DOMINICANA, S.A.RPKI Valid179.51.78.0
- 179.51.79.0/24AS52471COLUMBUS NETWORKS DOMINICANA, S.A.RPKI Valid179.51.79.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.