BGPプレフィックス検索
プレフィックス(または単一のアドレス)を入力してください。世界のルーティングテーブルを毎日複製したデータから回答します。
2a13:a5c6:4000::/36
完全一致で広報
- 2a13:a5c6:4000::/36AS201217RADISHCLOUD TECHNOLOGY LLCRPKI 有効2a13:a5c6:4000::
- レジストリ
- RIPE NCC · イギリス · 2023/08/08
- 割り振りブロック
- 2a13:a5c0:: – 2a13:a5c7:ffff:ffff:ffff:ffff:ffff:ffff
包含する経路
- 2a13:a5c6::/32AS201217RADISHCLOUD TECHNOLOGY LLCRPKI 有効2a13:a5c6::
より詳細な経路
- 2a13:a5c6:40b1::/48AS201217RADISHCLOUD TECHNOLOGY LLCRPKI 有効2a13:a5c6:40b1::
- 2a13:a5c6:4100::/40AS201217RADISHCLOUD TECHNOLOGY LLCRPKI 有効2a13:a5c6:4100::
- 2a13:a5c6:4101::/48AS201217RADISHCLOUD TECHNOLOGY LLCRPKI 有効2a13:a5c6:4101::
- 2a13:a5c6:4102::/48AS201217RADISHCLOUD TECHNOLOGY LLCRPKI 有効2a13:a5c6:4102::
- 2a13:a5c6:4103::/48AS201217RADISHCLOUD TECHNOLOGY LLCRPKI 有効2a13:a5c6:4103::
- 2a13:a5c6:4a09::/48AS201217RADISHCLOUD TECHNOLOGY LLCRPKI 有効2a13:a5c6:4a09::
- 2a13:a5c6:4aa1::/48AS201217RADISHCLOUD TECHNOLOGY LLCRPKI 有効2a13:a5c6:4aa1::
- 2a13:a5c6:4aa2::/48AS201217RADISHCLOUD TECHNOLOGY LLCRPKI 有効2a13:a5c6:4aa2::
- 2a13:a5c6:4aa3::/48AS201217RADISHCLOUD TECHNOLOGY LLCRPKI 有効2a13:a5c6:4aa3::
- 2a13:a5c6:4aa4::/48AS201217RADISHCLOUD TECHNOLOGY LLCRPKI 有効2a13:a5c6:4aa4::
- 2a13:a5c6:4aa5::/48AS201217RADISHCLOUD TECHNOLOGY LLCRPKI 有効2a13:a5c6:4aa5::
このテキストはまだ日本語で提供されていません。翻訳が公開されるまで英語で表示しています。
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.