BGP 前缀查询
输入一个前缀(或单个地址)。由我们每日复制的全球路由表回答。
74.2.0.0/16
精确宣告
- 74.2.0.0/16AS3257GTT Communications Inc.RPKI 无 ROA74.2.0.0
- 注册机构
- ARIN · 美国 · 2005年12月20日
- 分配的地址块
- 74.2.0.0 – 74.2.255.255
覆盖路由
没有较不具体的路由覆盖它。
更具体的路由
- 74.2.0.0/22AS3257GTT Communications Inc.RPKI 有效74.2.0.0
- 74.2.4.0/24AS197860Haruka Network LimitedRPKI 有效74.2.4.0
- 74.2.5.0/24AS212669Karolio IT paslaugos, UABRPKI 有效74.2.5.0
- 74.2.6.0/24AS6079RCNRPKI 有效74.2.6.0
- 74.2.7.0/24AS6079RCNRPKI 有效74.2.7.0
- 74.2.8.0/21AS3257GTT Communications Inc.RPKI 有效74.2.8.0
- 74.2.20.0/22AS20115Charter Communications LLCRPKI 有效74.2.20.0
- 74.2.28.0/22AS11427Charter Communications IncRPKI 有效74.2.28.0
- 74.2.32.0/22AS137830Wire IT ServicesRPKI 有效74.2.32.0
- 74.2.36.0/22AS20115Charter Communications LLCRPKI 有效74.2.36.0
- 74.2.40.0/22AS137830Wire IT ServicesRPKI 有效74.2.40.0
- 74.2.44.0/22AS3257GTT Communications Inc.RPKI 有效74.2.44.0
- 74.2.48.0/22AS137830Wire IT ServicesRPKI 有效74.2.48.0
- 74.2.52.0/24AS14618Amazon.com, Inc.RPKI 有效74.2.52.0
- 74.2.53.0/24AS14618Amazon.com, Inc.RPKI 有效74.2.53.0
- 74.2.54.0/24AS16509Amazon.com, Inc.RPKI 有效74.2.54.0
- 74.2.55.0/24AS14618Amazon.com, Inc.RPKI 有效74.2.55.0
- 74.2.56.0/22AS3257GTT Communications Inc.RPKI 有效74.2.56.0
- 74.2.60.0/22AS137830Wire IT ServicesRPKI 有效74.2.60.0
- 74.2.64.0/19AS11427Charter Communications IncRPKI 有效74.2.64.0
- 74.2.96.0/24AS393446AlphaCore Network LLCRPKI 有效74.2.96.0
- 74.2.98.0/23AS402732SMITH'SRPKI 有效74.2.98.0
- 74.2.102.0/23AS174Cogent Communications, LLCRPKI 有效74.2.102.0
- 74.2.116.0/22AS3257GTT Communications Inc.RPKI 有效74.2.116.0
- 74.2.120.0/21AS20115Charter Communications LLCRPKI 有效74.2.120.0
- 74.2.128.0/19AS6079RCNRPKI 有效74.2.128.0
- 74.2.160.0/24AS396073Majestic Hosting Solutions, LLCRPKI 有效74.2.160.0
- 74.2.161.0/24AS3257GTT Communications Inc.RPKI 有效74.2.161.0
- 74.2.164.0/24AS3257GTT Communications Inc.RPKI 有效74.2.164.0
- 74.2.165.0/24AS7029Windstream Communications LLCRPKI 有效74.2.165.0
- 74.2.166.0/24AS3257GTT Communications Inc.RPKI 有效74.2.166.0
- 74.2.176.0/22AS3257GTT Communications Inc.RPKI 有效74.2.176.0
- 74.2.180.0/22AS399989ULTRA ONERPKI 有效74.2.180.0
- 74.2.184.0/23AS174Cogent Communications, LLCRPKI 有效74.2.184.0
- 74.2.188.0/22AS3257GTT Communications Inc.RPKI 有效74.2.188.0
- 74.2.208.0/22AS137830Wire IT ServicesRPKI 有效74.2.208.0
- 74.2.212.0/22AS137830Wire IT ServicesRPKI 有效74.2.212.0
- 74.2.216.0/24AS6079RCNRPKI 有效74.2.216.0
- 74.2.218.0/23AS5650Frontier Communications of America, Inc.RPKI 有效74.2.218.0
- 74.2.221.0/24AS174Cogent Communications, LLCRPKI 有效74.2.221.0
- 74.2.223.0/24AS397423Tier.Net Technologies LLCRPKI 有效74.2.223.0
- 74.2.224.0/24AS3257GTT Communications Inc.RPKI 有效74.2.224.0
- 74.2.226.0/23AS3257GTT Communications Inc.RPKI 有效74.2.226.0
- 74.2.230.0/23AS2914NTT America, Inc.RPKI 有效74.2.230.0
- 74.2.240.0/22AS3257GTT Communications Inc.RPKI 有效74.2.240.0
- 74.2.244.0/22AS5650Frontier Communications of America, Inc.RPKI 有效74.2.244.0
- 74.2.248.0/21AS20115Charter Communications LLCRPKI 有效74.2.248.0
此内容尚无中文(中国)版本。在发布译文之前以英语显示。
On the internet, routes are announced as prefixes: an autonomous system tells its neighbours via BGP that it can deliver traffic for, say, 144.122.0.0/16 (Middle East Technical University, AS1967). 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.
常见问题
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.