BGP 前缀查询
输入一个前缀(或单个地址)。由我们每日复制的全球路由表回答。
210.181.128.0/18
精确宣告
- 210.181.128.0/18AS4766Korea TelecomRPKI 无 ROA210.181.128.0
- 注册机构
- APNIC · 韩国 · 1998年11月24日
- 分配的地址块
- 210.181.128.0 – 210.181.191.255
覆盖路由
没有较不具体的路由覆盖它。
更具体的路由
- 210.181.128.0/21AS4766Korea TelecomRPKI 无 ROA210.181.128.0
- 210.181.128.0/22AS4766Korea TelecomRPKI 无 ROA210.181.128.0
- 210.181.132.0/22AS4766Korea TelecomRPKI 无 ROA210.181.132.0
- 210.181.136.0/22AS4766Korea TelecomRPKI 无 ROA210.181.136.0
- 210.181.140.0/23AS4766Korea TelecomRPKI 无 ROA210.181.140.0
- 210.181.142.0/23AS9970Korea University of Technology and EducationRPKI 无 ROA210.181.142.0
- 210.181.144.0/22AS9970Korea University of Technology and EducationRPKI 无 ROA210.181.144.0
- 210.181.148.0/24AS9970Korea University of Technology and EducationRPKI 无 ROA210.181.148.0
- 210.181.149.0/24AS9970Korea University of Technology and EducationRPKI 无 ROA210.181.149.0
- 210.181.151.0/24AS9970Korea University of Technology and EducationRPKI 无 ROA210.181.151.0
- 210.181.152.0/22AS4766Korea TelecomRPKI 无 ROA210.181.152.0
- 210.181.156.0/23AS4766Korea TelecomRPKI 无 ROA210.181.156.0
- 210.181.158.0/24AS4766Korea TelecomRPKI 无 ROA210.181.158.0
- 210.181.159.0/24AS4766Korea TelecomRPKI 无 ROA210.181.159.0
- 210.181.160.0/24AS4766Korea TelecomRPKI 无 ROA210.181.160.0
- 210.181.161.0/24AS4766Korea TelecomRPKI 无 ROA210.181.161.0
- 210.181.162.0/24AS4766Korea TelecomRPKI 无 ROA210.181.162.0
- 210.181.163.0/24AS4766Korea TelecomRPKI 无 ROA210.181.163.0
- 210.181.164.0/24AS10053yeonsung UniversityRPKI 无 ROA210.181.164.0
- 210.181.165.0/24AS10053yeonsung UniversityRPKI 无 ROA210.181.165.0
- 210.181.166.0/24AS10053yeonsung UniversityRPKI 无 ROA210.181.166.0
- 210.181.168.0/22AS4766Korea TelecomRPKI 无 ROA210.181.168.0
- 210.181.172.0/24AS9859ChungCheong UniversityRPKI 无 ROA210.181.172.0
- 210.181.173.0/24AS9859ChungCheong UniversityRPKI 无 ROA210.181.173.0
- 210.181.174.0/24AS9859ChungCheong UniversityRPKI 无 ROA210.181.174.0
- 210.181.175.0/24AS9859ChungCheong UniversityRPKI 无 ROA210.181.175.0
- 210.181.176.0/24AS9859ChungCheong UniversityRPKI 无 ROA210.181.176.0
- 210.181.177.0/24AS9859ChungCheong UniversityRPKI 无 ROA210.181.177.0
- 210.181.178.0/24AS9859ChungCheong UniversityRPKI 无 ROA210.181.178.0
- 210.181.181.0/24AS4766Korea TelecomRPKI 无 ROA210.181.181.0
- 210.181.182.0/24AS4766Korea TelecomRPKI 无 ROA210.181.182.0
- 210.181.183.0/24AS4766Korea TelecomRPKI 无 ROA210.181.183.0
- 210.181.184.0/24AS4766Korea TelecomRPKI 无 ROA210.181.184.0
- 210.181.185.0/24AS3786LG DACOM CorporationRPKI 无 ROA210.181.185.0
- 210.181.186.0/24AS3786LG DACOM CorporationRPKI 无 ROA210.181.186.0
- 210.181.187.0/24AS3786LG DACOM CorporationRPKI 无 ROA210.181.187.0
- 210.181.188.0/23AS4766Korea TelecomRPKI 无 ROA210.181.188.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.