BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
67.200.0.0/17
Announced exactly
- 67.200.0.0/17AS3257GTT Communications Inc.RPKI Not found67.200.0.0
- Registry
- ARIN · United States · Aug 16, 2007
- Delegated block
- 67.200.0.0 – 67.200.127.255
Covering routes
No less-specific route covers it.
More-specific routes
- 67.200.0.0/19AS6079RCNRPKI Not found67.200.0.0
- 67.200.32.0/20AS7029Windstream Communications LLCRPKI Not found67.200.32.0
- 67.200.48.0/24AS812Rogers Communications Canada Inc.RPKI Not found67.200.48.0
- 67.200.50.0/23AS9304HGC Global Communications LimitedRPKI Not found67.200.50.0
- 67.200.52.0/24AS46401OmniSync NetworksRPKI Valid67.200.52.0
- 67.200.53.0/24AS46401OmniSync NetworksRPKI Valid67.200.53.0
- 67.200.54.0/23AS9304HGC Global Communications LimitedRPKI Not found67.200.54.0
- 67.200.56.0/23AS46401OmniSync NetworksRPKI Valid67.200.56.0
- 67.200.56.0/24AS46401OmniSync NetworksRPKI Valid67.200.56.0
- 67.200.57.0/24AS46401OmniSync NetworksRPKI Valid67.200.57.0
- 67.200.58.0/24AS45217Tora Trading Services Ltd.RPKI Not found67.200.58.0
- 67.200.60.0/22AS7029Windstream Communications LLCRPKI Not found67.200.60.0
- 67.200.64.0/20AS7029Windstream Communications LLCRPKI Not found67.200.64.0
- 67.200.80.0/21AS7029Windstream Communications LLCRPKI Not found67.200.80.0
- 67.200.88.0/23AS7029Windstream Communications LLCRPKI Not found67.200.88.0
- 67.200.88.0/24AS7029Windstream Communications LLCRPKI Not found67.200.88.0
- 67.200.90.0/24AS812Rogers Communications Canada Inc.RPKI Not found67.200.90.0
- 67.200.91.0/24AS15277Hill International, Inc.RPKI Not found67.200.91.0
- 67.200.92.0/22AS7029Windstream Communications LLCRPKI Not found67.200.92.0
- 67.200.96.0/23AS7029Windstream Communications LLCRPKI Not found67.200.96.0
- 67.200.98.0/24AS812Rogers Communications Canada Inc.RPKI Not found67.200.98.0
- 67.200.100.0/23AS54004Cablevision Lightpath LLCRPKI Not found67.200.100.0
- 67.200.102.0/24AS812Rogers Communications Canada Inc.RPKI Not found67.200.102.0
- 67.200.104.0/21AS11404Wave BroadbandRPKI Not found67.200.104.0
- 67.200.112.0/22AS7029Windstream Communications LLCRPKI Not found67.200.112.0
- 67.200.116.0/24AS46401OmniSync NetworksRPKI Valid67.200.116.0
- 67.200.117.0/24AS46401OmniSync NetworksRPKI Valid67.200.117.0
- 67.200.118.0/23AS54004Cablevision Lightpath LLCRPKI Not found67.200.118.0
- 67.200.120.0/21AS11404Wave BroadbandRPKI Not found67.200.120.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.