BGPプレフィックス検索
プレフィックス(または単一のアドレス)を入力してください。世界のルーティングテーブルを毎日複製したデータから回答します。
2403:c580:fff0::/44
完全一致で広報
- 2403:c580:fff0::/44AS2571DHL Information Services (Europe) s.r.oRPKI ROAなし2403:c580:fff0::
- レジストリ
- APNIC · マレーシア · 2015/12/01
- 割り振りブロック
- 2403:c580:: – 2403:c580:ffff:ffff:ffff:ffff:ffff:ffff
包含する経路
包含する集約経路はありません。
より詳細な経路
- 2403:c580:fff1::/48AS2571DHL Information Services (Europe) s.r.oRPKI 有効2403:c580:fff1::
- 2403:c580:fff2::/48AS2571DHL Information Services (Europe) s.r.oRPKI 有効2403:c580:fff2::
- 2403:c580:fff3::/48AS19905Vercara, LLCRPKI 有効2403:c580:fff3::
- 2403:c580:fff4::/48AS2571DHL Information Services (Europe) s.r.oRPKI 有効2403:c580:fff4::
- 2403:c580:fff5::/48AS2571DHL Information Services (Europe) s.r.oRPKI 有効2403:c580:fff5::
- 2403:c580:fff6::/48AS2571DHL Information Services (Europe) s.r.oRPKI 有効2403:c580:fff6::
- 2403:c580:fff7::/48AS2571DHL Information Services (Europe) s.r.oRPKI 有効2403:c580:fff7::
- 2403:c580:fff8::/48AS2571DHL Information Services (Europe) s.r.oRPKI 有効2403:c580:fff8::
- 2403:c580:fff9::/48AS2571DHL Information Services (Europe) s.r.oRPKI 有効2403:c580:fff9::
- 2403:c580:fffa::/48AS2571DHL Information Services (Europe) s.r.oRPKI 有効2403:c580:fffa::
- 2403:c580:fffb::/48AS2571DHL Information Services (Europe) s.r.oRPKI 有効2403:c580:fffb::
- 2403:c580:fffc::/48AS2571DHL Information Services (Europe) s.r.oRPKI 有効2403:c580:fffc::
- 2403:c580:fffd::/48AS19905Vercara, LLCRPKI 有効2403:c580:fffd::
- 2403:c580:fffe::/48AS2571DHL Information Services (Europe) s.r.oRPKI 有効2403:c580:fffe::
- 2403:c580:ffff::/48AS2571DHL Information Services (Europe) s.r.oRPKI 有効2403:c580:ffff::
このテキストはまだ日本語で提供されていません。翻訳が公開されるまで英語で表示しています。
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.