BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
67.207.160.0/19
Announced exactly
- 67.207.160.0/19AS21769Colocation America CorporationRPKI Not found67.207.160.0
- Registry
- ARIN · United States · Jul 2, 2007
- Delegated block
- 67.207.160.0 – 67.207.191.255
Covering routes
No less-specific route covers it.
More-specific routes
- 67.207.167.0/24AS47007Colocation America CorporationRPKI Valid67.207.167.0
- 67.207.168.0/21AS17252Colocation America CorporationRPKI Not found67.207.168.0
- 67.207.169.0/24AS9009M247RPKI Valid67.207.169.0
- 67.207.171.0/24AS54103MOD Mission Critical, LLCRPKI Valid67.207.171.0
- 67.207.172.0/24AS9009M247RPKI Valid67.207.172.0
- 67.207.173.0/24AS47007Colocation America CorporationRPKI Valid67.207.173.0
- 67.207.174.0/24AS47007Colocation America CorporationRPKI Valid67.207.174.0
- 67.207.175.0/24AS47007Colocation America CorporationRPKI Valid67.207.175.0
- 67.207.176.0/21AS17252Colocation America CorporationRPKI Not found67.207.176.0
- 67.207.176.0/24AS47007Colocation America CorporationRPKI Valid67.207.176.0
- 67.207.181.0/24AS9009M247RPKI Valid67.207.181.0
- 67.207.182.0/24AS212633EE-MOBILERPKI Valid67.207.182.0
- 67.207.183.0/24AS47007Colocation America CorporationRPKI Valid67.207.183.0
- 67.207.184.0/21AS17252Colocation America CorporationRPKI Not found67.207.184.0
- 67.207.184.0/22AS47007Colocation America CorporationRPKI Valid67.207.184.0
- 67.207.188.0/24AS212335INTERNET-2RPKI Valid67.207.188.0
- 67.207.190.0/24AS47007Colocation America CorporationRPKI Valid67.207.190.0
- 67.207.191.0/24AS47007Colocation America CorporationRPKI Valid67.207.191.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.