BGP 前缀查询
输入一个前缀(或单个地址)。由我们每日复制的全球路由表回答。
66.227.0.0/17
精确宣告
- 66.227.0.0/17AS3257GTT Communications Inc.RPKI 无 ROA66.227.0.0
- 注册机构
- ARIN · 美国 · 2002年1月31日
- 分配的地址块
- 66.227.0.0 – 66.227.127.255
覆盖路由
没有较不具体的路由覆盖它。
更具体的路由
- 66.227.4.0/22AS199527UAB "Bite Lietuva"RPKI 无 ROA66.227.4.0
- 66.227.8.0/23AS199527UAB "Bite Lietuva"RPKI 无 ROA66.227.8.0
- 66.227.10.0/24AS23029E StreetRPKI 无 ROA66.227.10.0
- 66.227.11.0/24AS199527UAB "Bite Lietuva"RPKI 无 ROA66.227.11.0
- 66.227.12.0/22AS36916X-DSL Networking SolutionsRPKI 有效66.227.12.0
- 66.227.16.0/24AS199527UAB "Bite Lietuva"RPKI 无 ROA66.227.16.0
- 66.227.18.0/24AS27508TradeLink, LLCRPKI 无 ROA66.227.18.0
- 66.227.19.0/24AS199527UAB "Bite Lietuva"RPKI 无 ROA66.227.19.0
- 66.227.20.0/22AS199527UAB "Bite Lietuva"RPKI 无 ROA66.227.20.0
- 66.227.24.0/24AS199527UAB "Bite Lietuva"RPKI 无 ROA66.227.24.0
- 66.227.26.0/23AS199527UAB "Bite Lietuva"RPKI 无 ROA66.227.26.0
- 66.227.28.0/23AS199527UAB "Bite Lietuva"RPKI 无 ROA66.227.28.0
- 66.227.31.0/24AS199527UAB "Bite Lietuva"RPKI 无 ROA66.227.31.0
- 66.227.32.0/21AS11611Arctic Fox Networks IncRPKI 有效66.227.32.0
- 66.227.40.0/22AS199527UAB "Bite Lietuva"RPKI 无 ROA66.227.40.0
- 66.227.46.0/24AS17352Application XRPKI 无 ROA66.227.46.0
- 66.227.47.0/24AS199527UAB "Bite Lietuva"RPKI 无 ROA66.227.47.0
- 66.227.56.0/23AS199527UAB "Bite Lietuva"RPKI 无 ROA66.227.56.0
- 66.227.58.0/24AS199527UAB "Bite Lietuva"RPKI 无 ROA66.227.58.0
- 66.227.59.0/24AS26694Adm Investor Services, IncRPKI 无 ROA66.227.59.0
- 66.227.60.0/22AS199527UAB "Bite Lietuva"RPKI 无 ROA66.227.60.0
- 66.227.64.0/22AS199527UAB "Bite Lietuva"RPKI 无 ROA66.227.64.0
- 66.227.70.0/23AS21886Netrix LLCRPKI 无 ROA66.227.70.0
- 66.227.72.0/22AS199527UAB "Bite Lietuva"RPKI 无 ROA66.227.72.0
- 66.227.77.0/24AS199527UAB "Bite Lietuva"RPKI 无 ROA66.227.77.0
- 66.227.78.0/23AS199527UAB "Bite Lietuva"RPKI 无 ROA66.227.78.0
- 66.227.80.0/21AS199527UAB "Bite Lietuva"RPKI 无 ROA66.227.80.0
- 66.227.88.0/22AS199527UAB "Bite Lietuva"RPKI 无 ROA66.227.88.0
- 66.227.92.0/23AS199527UAB "Bite Lietuva"RPKI 有效66.227.92.0
- 66.227.94.0/24AS26881IPR International, LLC.RPKI 无 ROA66.227.94.0
- 66.227.95.0/24AS199527UAB "Bite Lietuva"RPKI 无 ROA66.227.95.0
- 66.227.96.0/22AS6079RCNRPKI 有效66.227.96.0
- 66.227.100.0/22AS6079RCNRPKI 有效66.227.100.0
- 66.227.104.0/22AS6079RCNRPKI 有效66.227.104.0
- 66.227.108.0/24AS199527UAB "Bite Lietuva"RPKI 无 ROA66.227.108.0
- 66.227.110.0/24AS33200JabilRPKI 无 ROA66.227.110.0
- 66.227.111.0/24AS23029E StreetRPKI 无 ROA66.227.111.0
- 66.227.112.0/22AS2914NTT America, Inc.RPKI 有效66.227.112.0
- 66.227.116.0/24AS199527UAB "Bite Lietuva"RPKI 有效66.227.116.0
- 66.227.117.0/24AS199527UAB "Bite Lietuva"RPKI 无 ROA66.227.117.0
- 66.227.118.0/24AS13517Baker & McKenzieRPKI 无 ROA66.227.118.0
- 66.227.119.0/24AS3257GTT Communications Inc.RPKI 无效66.227.119.0
- 66.227.120.0/22AS6079RCNRPKI 有效66.227.120.0
- 66.227.124.0/22AS6079RCNRPKI 有效66.227.124.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.