BGP 前缀查询
输入一个前缀(或单个地址)。由我们每日复制的全球路由表回答。
66.62.0.0/16
精确宣告
- 66.62.0.0/16AS19092Zayo BandwidthRPKI 有效66.62.0.0
- 注册机构
- ARIN · 美国 · 2001年1月3日
- 分配的地址块
- 66.62.0.0 – 66.62.255.255
覆盖路由
没有较不具体的路由覆盖它。
更具体的路由
- 66.62.61.0/24AS36222WindWave CommunicationsRPKI 有效66.62.61.0
- 66.62.70.0/23AS10947Mountain West Technologies CorporationRPKI 有效66.62.70.0
- 66.62.75.0/24AS10947Mountain West Technologies CorporationRPKI 有效66.62.75.0
- 66.62.76.0/24AS53607Synergy Data Center & ServicesRPKI 有效66.62.76.0
- 66.62.88.0/21AS19092Zayo BandwidthRPKI 有效66.62.88.0
- 66.62.89.0/24AS21632Cybernet1RPKI 有效66.62.89.0
- 66.62.91.0/24AS32203Thornton Labs Inc.RPKI 有效66.62.91.0
- 66.62.92.0/24AS32203Thornton Labs Inc.RPKI 有效66.62.92.0
- 66.62.93.0/24AS21632Cybernet1RPKI 有效66.62.93.0
- 66.62.95.0/24AS21632Cybernet1RPKI 有效66.62.95.0
- 66.62.113.0/24AS21632Cybernet1RPKI 有效66.62.113.0
- 66.62.121.0/24AS21632Cybernet1RPKI 有效66.62.121.0
- 66.62.122.0/24AS21632Cybernet1RPKI 有效66.62.122.0
- 66.62.123.0/24AS21632Cybernet1RPKI 有效66.62.123.0
- 66.62.124.0/24AS21632Cybernet1RPKI 有效66.62.124.0
- 66.62.125.0/24AS32203Thornton Labs Inc.RPKI 有效66.62.125.0
- 66.62.126.0/24AS21632Cybernet1RPKI 有效66.62.126.0
- 66.62.128.0/24AS19092Zayo BandwidthRPKI 有效66.62.128.0
- 66.62.132.0/24AS6461Zayo BandwidthRPKI 有效66.62.132.0
- 66.62.146.0/24AS54650Pathwayz Communications, Inc.RPKI 有效66.62.146.0
- 66.62.151.0/24AS23492Nez Perce TribeRPKI 有效66.62.151.0
- 66.62.160.0/21AS19092Zayo BandwidthRPKI 有效66.62.160.0
- 66.62.161.0/24AS6461Zayo BandwidthRPKI 有效66.62.161.0
- 66.62.166.0/24AS21632Cybernet1RPKI 有效66.62.166.0
- 66.62.168.0/21AS19092Zayo BandwidthRPKI 有效66.62.168.0
- 66.62.176.0/21AS19092Zayo BandwidthRPKI 有效66.62.176.0
- 66.62.180.0/23AS399033VARCOMM BROADBAND, INC.RPKI 有效66.62.180.0
- 66.62.182.0/23AS6461Zayo BandwidthRPKI 有效66.62.182.0
- 66.62.200.0/21AS19092Zayo BandwidthRPKI 有效66.62.200.0
- 66.62.205.0/24AS398035SkyNet Communications LLCRPKI 有效66.62.205.0
- 66.62.227.0/24AS19092Zayo BandwidthRPKI 有效66.62.227.0
- 66.62.228.0/22AS19092Zayo BandwidthRPKI 有效66.62.228.0
- 66.62.230.0/24AS6461Zayo BandwidthRPKI 有效66.62.230.0
- 66.62.238.0/24AS6461Zayo BandwidthRPKI 有效66.62.238.0
- 66.62.239.0/24AS6461Zayo BandwidthRPKI 有效66.62.239.0
- 66.62.240.0/22AS6461Zayo BandwidthRPKI 有效66.62.240.0
- 66.62.244.0/23AS6461Zayo BandwidthRPKI 有效66.62.244.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.