BGP 前缀查询
输入一个前缀(或单个地址)。由我们每日复制的全球路由表回答。
38.55.96.0/19
精确宣告
- 38.55.96.0/19AS932XNNET LLCRPKI 无 ROA38.55.96.0
- 注册机构
- ARIN · 美国 · 1991年4月16日
- 分配的地址块
- 38.0.0.0 – 38.255.255.255
覆盖路由
- 38.0.0.0/8AS174Cogent Communications, LLCRPKI 无 ROA38.0.0.0
更具体的路由
- 38.55.98.0/24AS42960VH Global LimitedRPKI 无 ROA38.55.98.0
- 38.55.99.0/24AS42960VH Global LimitedRPKI 无 ROA38.55.99.0
- 38.55.100.0/24AS967VMISS Inc.RPKI 无 ROA38.55.100.0
- 38.55.101.0/24AS967VMISS Inc.RPKI 无 ROA38.55.101.0
- 38.55.102.0/24AS967VMISS Inc.RPKI 无 ROA38.55.102.0
- 38.55.103.0/24AS967VMISS Inc.RPKI 无 ROA38.55.103.0
- 38.55.104.0/24AS967VMISS Inc.RPKI 无 ROA38.55.104.0
- 38.55.105.0/24AS967VMISS Inc.RPKI 无 ROA38.55.105.0
- 38.55.106.0/24AS967VMISS Inc.RPKI 无 ROA38.55.106.0
- 38.55.107.0/24AS967VMISS Inc.RPKI 无 ROA38.55.107.0
- 38.55.108.0/24AS1054Zont LLCRPKI 无 ROA38.55.108.0
- 38.55.109.0/24AS214111TapHip LimitedRPKI 无 ROA38.55.109.0
- 38.55.110.0/24AS214111TapHip LimitedRPKI 无 ROA38.55.110.0
- 38.55.111.0/24AS1054Zont LLCRPKI 无 ROA38.55.111.0
- 38.55.112.0/24AS6134XNNET LLCRPKI 无 ROA38.55.112.0
- 38.55.113.0/24AS6134XNNET LLCRPKI 无 ROA38.55.113.0
- 38.55.114.0/24AS6134XNNET LLCRPKI 无 ROA38.55.114.0
- 38.55.115.0/24AS6134XNNET LLCRPKI 无 ROA38.55.115.0
- 38.55.116.0/24AS6134XNNET LLCRPKI 无 ROA38.55.116.0
- 38.55.117.0/24AS6134XNNET LLCRPKI 无 ROA38.55.117.0
- 38.55.118.0/24AS6134XNNET LLCRPKI 无 ROA38.55.118.0
- 38.55.119.0/24AS6134XNNET LLCRPKI 无 ROA38.55.119.0
- 38.55.120.0/24AS6134XNNET LLCRPKI 无 ROA38.55.120.0
- 38.55.121.0/24AS6134XNNET LLCRPKI 无 ROA38.55.121.0
- 38.55.122.0/24AS6134XNNET LLCRPKI 无 ROA38.55.122.0
- 38.55.124.0/24AS6134XNNET LLCRPKI 无 ROA38.55.124.0
- 38.55.125.0/24AS6134XNNET LLCRPKI 无 ROA38.55.125.0
- 38.55.126.0/24AS6134XNNET LLCRPKI 无 ROA38.55.126.0
- 38.55.127.0/24AS6134XNNET LLCRPKI 无 ROA38.55.127.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.