BGPプレフィックス検索
プレフィックス(または単一のアドレス)を入力してください。世界のルーティングテーブルを毎日複製したデータから回答します。
2402:d400::/32
完全一致で広報
- 2402:d400::/32AS17762Tata Teleservices Maharashtra LtdRPKI 有効2402:d400::
- レジストリ
- APNIC · インド · 2009/11/10
- 割り振りブロック
- 2402:d400:: – 2402:d400:ffff:ffff:ffff:ffff:ffff:ffff
包含する経路
包含する集約経路はありません。
より詳細な経路
- 2402:d400::/48AS17762Tata Teleservices Maharashtra LtdRPKI 有効2402:d400::
- 2402:d400:3::/48AS17762Tata Teleservices Maharashtra LtdRPKI 有効2402:d400:3::
- 2402:d400:4::/48AS17762Tata Teleservices Maharashtra LtdRPKI 有効2402:d400:4::
- 2402:d400:5::/48AS17762Tata Teleservices Maharashtra LtdRPKI 有効2402:d400:5::
- 2402:d400:c::/48AS17762Tata Teleservices Maharashtra LtdRPKI 有効2402:d400:c::
- 2402:d400:40::/48AS17762Tata Teleservices Maharashtra LtdRPKI 有効2402:d400:40::
- 2402:d400:41::/48AS17762Tata Teleservices Maharashtra LtdRPKI 有効2402:d400:41::
- 2402:d400:43::/48AS17762Tata Teleservices Maharashtra LtdRPKI 有効2402:d400:43::
- 2402:d400:44::/48AS17762Tata Teleservices Maharashtra LtdRPKI 有効2402:d400:44::
- 2402:d400:a2::/48AS134540Tata Teleservices (Maharashtra) LtdRPKI 有効2402:d400:a2::
- 2402:d400:3e0::/48AS17762Tata Teleservices Maharashtra LtdRPKI 有効2402:d400:3e0::
- 2402:d400:3e1::/48AS17762Tata Teleservices Maharashtra LtdRPKI 有効2402:d400:3e1::
- 2402:d400:3e2::/48AS17762Tata Teleservices Maharashtra LtdRPKI 有効2402:d400:3e2::
- 2402:d400:3e3::/48AS17762Tata Teleservices Maharashtra LtdRPKI 有効2402:d400:3e3::
- 2402:d400:3e4::/48AS17762Tata Teleservices Maharashtra LtdRPKI 有効2402:d400:3e4::
- 2402:d400:3e6::/48AS17762Tata Teleservices Maharashtra LtdRPKI 有効2402:d400:3e6::
- 2402:d400:fa00::/44AS17762Tata Teleservices Maharashtra LtdRPKI 有効2402:d400:fa00::
- 2402:d400:fa10::/44AS17762Tata Teleservices Maharashtra LtdRPKI 有効2402:d400:fa10::
- 2402:d400:fa20::/44AS17762Tata Teleservices Maharashtra LtdRPKI 有効2402:d400:fa20::
このテキストはまだ日本語で提供されていません。翻訳が公開されるまで英語で表示しています。
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.