BGPプレフィックス検索
プレフィックス(または単一のアドレス)を入力してください。世界のルーティングテーブルを毎日複製したデータから回答します。
2405:4800::/30
完全一致で広報
- 2405:4800::/30AS18403FPT Telecom CompanyRPKI 有効2405:4800::
- レジストリ
- APNIC · ベトナム · 2008/10/20
- 割り振りブロック
- 2405:4800:: – 2405:4800:ffff:ffff:ffff:ffff:ffff:ffff
包含する経路
包含する集約経路はありません。
より詳細な経路
- 2405:4800::/32AS18403FPT Telecom CompanyRPKI 有効2405:4800::
- 2405:4800:10c::/48AS18403FPT Telecom CompanyRPKI 有効2405:4800:10c::
- 2405:4800:10d::/48AS18403FPT Telecom CompanyRPKI 有効2405:4800:10d::
- 2405:4800:206::/48AS18403FPT Telecom CompanyRPKI 有効2405:4800:206::
- 2405:4800:2fe::/48AS18403FPT Telecom CompanyRPKI 有効2405:4800:2fe::
- 2405:4800:18c2::/48AS18403FPT Telecom CompanyRPKI 有効2405:4800:18c2::
- 2405:4800:5cc2::/48AS18403FPT Telecom CompanyRPKI 有効2405:4800:5cc2::
- 2405:4800:a403::/48AS18403FPT Telecom CompanyRPKI 有効2405:4800:a403::
- 2405:4800:a601::/48AS18403FPT Telecom CompanyRPKI 有効2405:4800:a601::
- 2405:4801::/32AS18403FPT Telecom CompanyRPKI 有効2405:4801::
- 2405:4802::/32AS18403FPT Telecom CompanyRPKI 有効2405:4802::
- 2405:4803::/32AS18403FPT Telecom CompanyRPKI 有効2405:4803::
- 2405:4803:a000::/36AS18403FPT Telecom CompanyRPKI 有効2405:4803:a000::
- 2405:4803:b000::/36AS18403FPT Telecom CompanyRPKI 有効2405:4803:b000::
- 2405:4803:c000::/36AS18403FPT Telecom CompanyRPKI 有効2405:4803:c000::
- 2405:4803:d000::/36AS18403FPT Telecom CompanyRPKI 有効2405:4803:d000::
- 2405:4803:e000::/36AS18403FPT Telecom CompanyRPKI 有効2405:4803:e000::
- 2405:4803:f000::/36AS18403FPT Telecom CompanyRPKI 有効2405:4803:f000::
このテキストはまだ日本語で提供されていません。翻訳が公開されるまで英語で表示しています。
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.