BGPプレフィックス検索
プレフィックス(または単一のアドレス)を入力してください。世界のルーティングテーブルを毎日複製したデータから回答します。
2400:4e80::/32
完全一致で広報
- 2400:4e80::/32AS131584Taiwan Intelligent Fiber Optic Network Co.,Ltd.RPKI 有効2400:4e80::
- レジストリ
- APNIC · 台湾 · 2013/11/05
- 割り振りブロック
- 2400:4e80:: – 2400:4e80:ffff:ffff:ffff:ffff:ffff:ffff
包含する経路
包含する集約経路はありません。
より詳細な経路
- 2400:4e80::/64AS131584Taiwan Intelligent Fiber Optic Network Co.,Ltd.RPKI 有効2400:4e80::
- 2400:4e80:0:1::/64AS131584Taiwan Intelligent Fiber Optic Network Co.,Ltd.RPKI 有効2400:4e80:0:1::
- 2400:4e80:1::/64AS131584Taiwan Intelligent Fiber Optic Network Co.,Ltd.RPKI 有効2400:4e80:1::
- 2400:4e80:1000::/48AS131584Taiwan Intelligent Fiber Optic Network Co.,Ltd.RPKI 有効2400:4e80:1000::
- 2400:4e80:79fa::/48AS131584Taiwan Intelligent Fiber Optic Network Co.,Ltd.RPKI 有効2400:4e80:79fa::
- 2400:4e80:79fb::/48AS131584Taiwan Intelligent Fiber Optic Network Co.,Ltd.RPKI 有効2400:4e80:79fb::
- 2400:4e80:79fc::/48AS131584Taiwan Intelligent Fiber Optic Network Co.,Ltd.RPKI 有効2400:4e80:79fc::
- 2400:4e80:79fd::/56AS131584Taiwan Intelligent Fiber Optic Network Co.,Ltd.RPKI 有効2400:4e80:79fd::
- 2400:4e80:79fd:100::/56AS131584Taiwan Intelligent Fiber Optic Network Co.,Ltd.RPKI 有効2400:4e80:79fd:100::
- 2400:4e80:79fd:200::/64AS131584Taiwan Intelligent Fiber Optic Network Co.,Ltd.RPKI 有効2400:4e80:79fd:200::
- 2400:4e80:79fd:400::/64AS131584Taiwan Intelligent Fiber Optic Network Co.,Ltd.RPKI 有効2400:4e80:79fd:400::
- 2400:4e80:79fd:500::/64AS131584Taiwan Intelligent Fiber Optic Network Co.,Ltd.RPKI 有効2400:4e80:79fd:500::
- 2400:4e80:79fd:700::/64AS131584Taiwan Intelligent Fiber Optic Network Co.,Ltd.RPKI 有効2400:4e80:79fd:700::
- 2400:4e80:79fd:800::/64AS131584Taiwan Intelligent Fiber Optic Network Co.,Ltd.RPKI 有効2400:4e80:79fd:800::
- 2400:4e80:79fd:1100::/64AS131584Taiwan Intelligent Fiber Optic Network Co.,Ltd.RPKI 有効2400:4e80:79fd:1100::
- 2400:4e80:79fd:1200::/64AS131584Taiwan Intelligent Fiber Optic Network Co.,Ltd.RPKI 有効2400:4e80:79fd:1200::
- 2400:4e80:79fd:1300::/64AS131584Taiwan Intelligent Fiber Optic Network Co.,Ltd.RPKI 有効2400:4e80:79fd:1300::
- 2400:4e80:79fd:1400::/64AS131584Taiwan Intelligent Fiber Optic Network Co.,Ltd.RPKI 有効2400:4e80:79fd:1400::
- 2400:4e80:79fe::/64AS131584Taiwan Intelligent Fiber Optic Network Co.,Ltd.RPKI 有効2400:4e80:79fe::
- 2400:4e80:79ff::/48AS131584Taiwan Intelligent Fiber Optic Network Co.,Ltd.RPKI 有効2400:4e80:79ff::
- 2400:4e80:a104::/48AS131584Taiwan Intelligent Fiber Optic Network Co.,Ltd.RPKI 有効2400:4e80:a104::
- 2400:4e80:a105::/48AS131584Taiwan Intelligent Fiber Optic Network Co.,Ltd.RPKI 有効2400:4e80:a105::
- 2400:4e80:fffe:fd00::/56AS131584Taiwan Intelligent Fiber Optic Network Co.,Ltd.RPKI 有効2400:4e80:fffe:fd00::
このテキストはまだ日本語で提供されていません。翻訳が公開されるまで英語で表示しています。
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.