BGP 前缀查询
输入一个前缀(或单个地址)。由我们每日复制的全球路由表回答。
57.140.192.0/18
精确宣告
- 57.140.192.0/18AS15169Google LLCRPKI 有效57.140.192.0
- 注册机构
- ARIN · 美国 · 2022年8月23日
- 分配的地址块
- 57.140.0.0 – 57.140.255.255
覆盖路由
没有较不具体的路由覆盖它。
更具体的路由
- 57.140.192.0/24AS15169Google LLCRPKI 有效57.140.192.0
- 57.140.193.0/24AS15169Google LLCRPKI 有效57.140.193.0
- 57.140.194.0/24AS15169Google LLCRPKI 有效57.140.194.0
- 57.140.195.0/24AS15169Google LLCRPKI 有效57.140.195.0
- 57.140.196.0/24AS15169Google LLCRPKI 有效57.140.196.0
- 57.140.197.0/24AS15169Google LLCRPKI 有效57.140.197.0
- 57.140.198.0/24AS15169Google LLCRPKI 有效57.140.198.0
- 57.140.199.0/24AS15169Google LLCRPKI 有效57.140.199.0
- 57.140.200.0/24AS15169Google LLCRPKI 有效57.140.200.0
- 57.140.201.0/24AS15169Google LLCRPKI 有效57.140.201.0
- 57.140.202.0/24AS15169Google LLCRPKI 有效57.140.202.0
- 57.140.203.0/24AS15169Google LLCRPKI 有效57.140.203.0
- 57.140.204.0/24AS15169Google LLCRPKI 有效57.140.204.0
- 57.140.205.0/24AS15169Google LLCRPKI 有效57.140.205.0
- 57.140.206.0/24AS15169Google LLCRPKI 有效57.140.206.0
- 57.140.208.0/24AS15169Google LLCRPKI 有效57.140.208.0
- 57.140.209.0/24AS15169Google LLCRPKI 有效57.140.209.0
- 57.140.210.0/24AS15169Google LLCRPKI 有效57.140.210.0
- 57.140.211.0/24AS15169Google LLCRPKI 有效57.140.211.0
- 57.140.212.0/24AS19527Google LLCRPKI 有效57.140.212.0
- 57.140.213.0/24AS19527Google LLCRPKI 有效57.140.213.0
- 57.140.214.0/24AS19527Google LLCRPKI 有效57.140.214.0
- 57.140.215.0/24AS19527Google LLCRPKI 有效57.140.215.0
- 57.140.216.0/24AS15169Google LLCRPKI 有效57.140.216.0
- 57.140.217.0/24AS15169Google LLCRPKI 有效57.140.217.0
- 57.140.218.0/24AS19527Google LLCRPKI 有效57.140.218.0
- 57.140.224.0/24AS15169Google LLCRPKI 有效57.140.224.0
- 57.140.225.0/24AS15169Google LLCRPKI 有效57.140.225.0
- 57.140.226.0/24AS15169Google LLCRPKI 有效57.140.226.0
- 57.140.227.0/24AS15169Google LLCRPKI 有效57.140.227.0
- 57.140.228.0/24AS15169Google LLCRPKI 有效57.140.228.0
- 57.140.229.0/24AS15169Google LLCRPKI 有效57.140.229.0
- 57.140.230.0/24AS15169Google LLCRPKI 有效57.140.230.0
- 57.140.240.0/24AS19527Google LLCRPKI 有效57.140.240.0
- 57.140.241.0/24AS15169Google LLCRPKI 有效57.140.241.0
- 57.140.242.0/24AS15169Google LLCRPKI 有效57.140.242.0
- 57.140.243.0/24AS19527Google LLCRPKI 有效57.140.243.0
- 57.140.244.0/24AS19527Google LLCRPKI 有效57.140.244.0
- 57.140.245.0/24AS19527Google LLCRPKI 有效57.140.245.0
- 57.140.246.0/24AS15169Google LLCRPKI 有效57.140.246.0
- 57.140.247.0/24AS19527Google LLCRPKI 有效57.140.247.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.