BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
207.16.0.0/14
Announced exactly
- 207.16.0.0/14AS701Verizon BusinessRPKI Not found207.16.0.0
- Registry
- ARIN · United States · Dec 29, 1995
- Delegated block
- 207.16.0.0 – 207.19.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 207.16.53.0/24AS55052Konica Minolta Business Solutions U.S.A., Inc.RPKI Not found207.16.53.0
- 207.16.160.0/20AS6620AMA Communications, LLCRPKI Not found207.16.160.0
- 207.17.33.0/24AS6195The Goldman Sachs Group, Inc.RPKI Valid207.17.33.0
- 207.17.34.0/24AS6195The Goldman Sachs Group, Inc.RPKI Valid207.17.34.0
- 207.17.45.0/24AS6195The Goldman Sachs Group, Inc.RPKI Valid207.17.45.0
- 207.17.46.0/24AS33598The Goldman Sachs Group, Inc.RPKI Valid207.17.46.0
- 207.17.137.0/24AS14203Juniper Networks, Inc.RPKI Not found207.17.137.0
- 207.17.190.0/23AS28502Axtel, S.A.B. de C.V.RPKI Not found207.17.190.0
- 207.17.190.0/24AS28502Axtel, S.A.B. de C.V.RPKI Not found207.17.190.0
- 207.18.56.0/22AS55052Konica Minolta Business Solutions U.S.A., Inc.RPKI Not found207.18.56.0
- 207.18.68.0/23AS6620AMA Communications, LLCRPKI Not found207.18.68.0
- 207.19.0.0/21AS6620AMA Communications, LLCRPKI Not found207.19.0.0
- 207.19.96.0/21AS7381BroadbandONE, LLCRPKI Not found207.19.96.0
- 207.19.252.0/22AS6648Bayan Telecommunications, Inc.RPKI Not found207.19.252.0
On the internet, routes are announced as prefixes: an autonomous system tells its neighbours via BGP that it can deliver traffic for, say, 62.103.0.0/16. 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.