BGP 前缀查询
输入一个前缀(或单个地址)。由我们每日复制的全球路由表回答。
206.169.0.0/16
精确宣告
- 206.169.0.0/16AS3549Level 3 Parent, LLCRPKI 无 ROA206.169.0.0
- 注册机构
- ARIN · 美国 · 1995年10月19日
- 分配的地址块
- 206.169.0.0 – 206.169.255.255
覆盖路由
没有较不具体的路由覆盖它。
更具体的路由
- 206.169.6.0/24AS40075Radiology LTDRPKI 无 ROA206.169.6.0
- 206.169.38.0/23AS19881Valley Telecommunications CompanyRPKI 无 ROA206.169.38.0
- 206.169.46.0/23AS19881Valley Telecommunications CompanyRPKI 无 ROA206.169.46.0
- 206.169.63.0/24AS398929Loma Linda Connected Community ProgramRPKI 无 ROA206.169.63.0
- 206.169.64.0/24AS19881Valley Telecommunications CompanyRPKI 无 ROA206.169.64.0
- 206.169.67.0/24AS203Level 3 Parent, LLCRPKI 无 ROA206.169.67.0
- 206.169.74.0/24AS22702RingSquaredRPKI 无 ROA206.169.74.0
- 206.169.77.0/24AS398929Loma Linda Connected Community ProgramRPKI 无 ROA206.169.77.0
- 206.169.82.0/24AS3356Level 3 Parent, LLCRPKI 无 ROA206.169.82.0
- 206.169.89.0/24AS19881Valley Telecommunications CompanyRPKI 无 ROA206.169.89.0
- 206.169.101.0/24AS3356Level 3 Parent, LLCRPKI 无 ROA206.169.101.0
- 206.169.114.0/24AS393510St Francis Healthcare System of HawaiiRPKI 无 ROA206.169.114.0
- 206.169.120.0/23AS398929Loma Linda Connected Community ProgramRPKI 无 ROA206.169.120.0
- 206.169.133.0/24AS55092UNASSIGNEDRPKI 无 ROA206.169.133.0
- 206.169.134.0/23AS3356Level 3 Parent, LLCRPKI 无 ROA206.169.134.0
- 206.169.140.0/22AS25649AYERA TECHNOLOGIES, INC.RPKI 无 ROA206.169.140.0
- 206.169.150.0/23AS3356Level 3 Parent, LLCRPKI 无 ROA206.169.150.0
- 206.169.152.0/24AS395396Alert Alarm HawaiiRPKI 无 ROA206.169.152.0
- 206.169.160.0/24AS18669Bal Seal Engineering Co. Inc.RPKI 无 ROA206.169.160.0
- 206.169.162.0/23AS25649AYERA TECHNOLOGIES, INC.RPKI 无 ROA206.169.162.0
- 206.169.171.0/24AS3356Level 3 Parent, LLCRPKI 无 ROA206.169.171.0
- 206.169.190.0/24AS3356Level 3 Parent, LLCRPKI 无 ROA206.169.190.0
- 206.169.206.0/24AS19881Valley Telecommunications CompanyRPKI 无 ROA206.169.206.0
- 206.169.211.0/24AS29824Appfolio, Inc.RPKI 无 ROA206.169.211.0
- 206.169.212.0/24AS62621UNASSIGNEDRPKI 无 ROA206.169.212.0
- 206.169.217.0/24AS26421Ponderosa CablevisionRPKI 有效206.169.217.0
- 206.169.218.0/23AS26421Ponderosa CablevisionRPKI 有效206.169.218.0
- 206.169.233.0/24AS20168Precor IncorporatedRPKI 无 ROA206.169.233.0
- 206.169.242.0/24AS10753Level 3 Parent, LLCRPKI 无 ROA206.169.242.0
- 206.169.252.0/23AS26729Midwest Internet, Inc.RPKI 无 ROA206.169.252.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.