BGP 前缀查询
输入一个前缀(或单个地址)。由我们每日复制的全球路由表回答。
2406:3000::/32
精确宣告
- 2406:3000::/32AS4657StarHub LtdRPKI 有效2406:3000::
- 注册机构
- APNIC · 新加坡 · 2008年2月19日
- 分配的地址块
- 2406:3000:: – 2406:3000:ffff:ffff:ffff:ffff:ffff:ffff
覆盖路由
- 2406:3000::/30AS4657StarHub LtdRPKI 有效2406:3000::
更具体的路由
- 2406:3000::/48AS4657StarHub LtdRPKI 有效2406:3000::
- 2406:3000:2::/48AS4657StarHub LtdRPKI 有效2406:3000:2::
- 2406:3000:3::/48AS4657StarHub LtdRPKI 有效2406:3000:3::
- 2406:3000:6::/48AS4657StarHub LtdRPKI 有效2406:3000:6::
- 2406:3000:b::/48AS4657StarHub LtdRPKI 有效2406:3000:b::
- 2406:3000:d::/48AS140928T20025RPKI 有效2406:3000:d::
- 2406:3000:e::/48AS140929T20025RPKI 有效2406:3000:e::
- 2406:3000:f::/48AS4657StarHub LtdRPKI 有效2406:3000:f::
- 2406:3000:10::/48AS4657StarHub LtdRPKI 有效2406:3000:10::
- 2406:3000:16::/48AS4657StarHub LtdRPKI 有效2406:3000:16::
- 2406:3000:2a::/48AS4657StarHub LtdRPKI 有效2406:3000:2a::
- 2406:3000:31::/48AS4657StarHub LtdRPKI 有效2406:3000:31::
- 2406:3000:33::/48AS4657StarHub LtdRPKI 有效2406:3000:33::
- 2406:3000:34::/48AS4657StarHub LtdRPKI 有效2406:3000:34::
- 2406:3000:35::/48AS16625Akamai Technologies, Inc.RPKI 有效2406:3000:35::
- 2406:3000:42::/48AS4657StarHub LtdRPKI 有效2406:3000:42::
- 2406:3000:4c::/48AS4657StarHub LtdRPKI 有效2406:3000:4c::
- 2406:3000:50::/48AS4657StarHub LtdRPKI 有效2406:3000:50::
- 2406:3000:53::/48AS4657StarHub LtdRPKI 有效2406:3000:53::
- 2406:3000:202::/47AS138345StarHub LtdRPKI 有效2406:3000:202::
- 2406:3000:202::/48AS138345StarHub LtdRPKI 有效2406:3000:202::
- 2406:3000:203::/48AS138345StarHub LtdRPKI 有效2406:3000:203::
- 2406:3000:204::/46AS138345StarHub LtdRPKI 有效2406:3000:204::
- 2406:3000:204::/48AS138345StarHub LtdRPKI 有效2406:3000:204::
- 2406:3000:205::/48AS138345StarHub LtdRPKI 有效2406:3000:205::
- 2406:3000:206::/48AS138345StarHub LtdRPKI 有效2406:3000:206::
- 2406:3000:207::/48AS138345StarHub LtdRPKI 有效2406:3000:207::
- 2406:3000:208::/47AS138345StarHub LtdRPKI 有效2406:3000:208::
- 2406:3000:208::/48AS138345StarHub LtdRPKI 有效2406:3000:208::
- 2406:3000:209::/48AS138345StarHub LtdRPKI 有效2406:3000:209::
- 2406:3000:20a::/47AS138345StarHub LtdRPKI 有效2406:3000:20a::
- 2406:3000:20a::/48AS138345StarHub LtdRPKI 有效2406:3000:20a::
- 2406:3000:20b::/48AS138345StarHub LtdRPKI 有效2406:3000:20b::
- 2406:3000:20c::/46AS138345StarHub LtdRPKI 有效2406:3000:20c::
- 2406:3000:20c::/48AS138345StarHub LtdRPKI 有效2406:3000:20c::
- 2406:3000:20d::/48AS138345StarHub LtdRPKI 有效2406:3000:20d::
- 2406:3000:20e::/48AS138345StarHub LtdRPKI 有效2406:3000:20e::
- 2406:3000:20f::/48AS138345StarHub LtdRPKI 有效2406:3000:20f::
- 2406:3000:210::/47AS138345StarHub LtdRPKI 有效2406:3000:210::
- 2406:3000:210::/48AS138345StarHub LtdRPKI 有效2406:3000:210::
- 2406:3000:211::/48AS138345StarHub LtdRPKI 有效2406:3000:211::
- 2406:3000:212::/48AS138345StarHub LtdRPKI 有效2406:3000:212::
- 2406:3000:213::/48AS138345StarHub LtdRPKI 有效2406:3000:213::
- 2406:3000:214::/48AS138345StarHub LtdRPKI 有效2406:3000:214::
此内容尚无中文(中国)版本。在发布译文之前以英语显示。
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.