BGP 前缀查询
输入一个前缀（或单个地址）。由我们每日复制的全球路由表回答。
200.57.32.0/20
精确宣告
- 200.57.32.0/20AS22011Sixsigma Networks Mexico, S.A. de C.V.RPKI 有效200.57.32.0
- 注册机构
- LACNIC · 墨西哥 · 2000年12月27日
- 分配的地址块
- 200.57.32.0 – 200.57.47.255
覆盖路由
没有较不具体的路由覆盖它。
更具体的路由
- 200.57.32.0/24AS22011Sixsigma Networks Mexico, S.A. de C.V.RPKI 有效200.57.32.0
- 200.57.33.0/24AS22011Sixsigma Networks Mexico, S.A. de C.V.RPKI 有效200.57.33.0
- 200.57.34.0/24AS22011Sixsigma Networks Mexico, S.A. de C.V.RPKI 有效200.57.34.0
- 200.57.35.0/24AS22011Sixsigma Networks Mexico, S.A. de C.V.RPKI 有效200.57.35.0
- 200.57.36.0/24AS22011Sixsigma Networks Mexico, S.A. de C.V.RPKI 有效200.57.36.0
- 200.57.37.0/24AS22011Sixsigma Networks Mexico, S.A. de C.V.RPKI 有效200.57.37.0
- 200.57.38.0/24AS22011Sixsigma Networks Mexico, S.A. de C.V.RPKI 有效200.57.38.0
- 200.57.39.0/24AS22011Sixsigma Networks Mexico, S.A. de C.V.RPKI 有效200.57.39.0
- 200.57.40.0/24AS22011Sixsigma Networks Mexico, S.A. de C.V.RPKI 有效200.57.40.0
- 200.57.41.0/24AS22011Sixsigma Networks Mexico, S.A. de C.V.RPKI 有效200.57.41.0
- 200.57.42.0/24AS22011Sixsigma Networks Mexico, S.A. de C.V.RPKI 有效200.57.42.0
- 200.57.43.0/24AS22011Sixsigma Networks Mexico, S.A. de C.V.RPKI 有效200.57.43.0
- 200.57.44.0/24AS22011Sixsigma Networks Mexico, S.A. de C.V.RPKI 有效200.57.44.0
- 200.57.45.0/24AS22011Sixsigma Networks Mexico, S.A. de C.V.RPKI 有效200.57.45.0
- 200.57.46.0/24AS22011Sixsigma Networks Mexico, S.A. de C.V.RPKI 有效200.57.46.0
- 200.57.47.0/24AS22011Sixsigma Networks Mexico, S.A. de C.V.RPKI 有效200.57.47.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.