BGPプレフィックス検索
プレフィックス(または単一のアドレス)を入力してください。世界のルーティングテーブルを毎日複製したデータから回答します。
2607:fb90::/32
完全一致で広報
- 2607:fb90::/32AS21928T-Mobile USA, Inc.RPKI 有効2607:fb90::
- レジストリ
- ARIN · アメリカ合衆国 · 2009/07/14
- 割り振りブロック
- 2607:fb90:: – 2607:fb9f:ffff:ffff:ffff:ffff:ffff:ffff
包含する経路
- 2607:fb90::/28AS21928T-Mobile USA, Inc.RPKI 有効2607:fb90::
より詳細な経路
- 2607:fb90:500::/40AS21928T-Mobile USA, Inc.RPKI 有効2607:fb90:500::
- 2607:fb90:800::/40AS21928T-Mobile USA, Inc.RPKI 有効2607:fb90:800::
- 2607:fb90:d00::/40AS21928T-Mobile USA, Inc.RPKI 有効2607:fb90:d00::
- 2607:fb90:1c00::/40AS21928T-Mobile USA, Inc.RPKI 有効2607:fb90:1c00::
- 2607:fb90:2d00::/40AS21928T-Mobile USA, Inc.RPKI 有効2607:fb90:2d00::
- 2607:fb90:3900::/40AS21928T-Mobile USA, Inc.RPKI 有効2607:fb90:3900::
- 2607:fb90:3e00::/40AS21928T-Mobile USA, Inc.RPKI 有効2607:fb90:3e00::
- 2607:fb90:4500::/40AS21928T-Mobile USA, Inc.RPKI 有効2607:fb90:4500::
- 2607:fb90:5c00::/40AS21928T-Mobile USA, Inc.RPKI 有効2607:fb90:5c00::
- 2607:fb90:6c00::/38AS21928T-Mobile USA, Inc.RPKI 有効2607:fb90:6c00::
- 2607:fb90:6d00::/40AS21928T-Mobile USA, Inc.RPKI 有効2607:fb90:6d00::
- 2607:fb90:7900::/40AS21928T-Mobile USA, Inc.RPKI 有効2607:fb90:7900::
- 2607:fb90:8a00::/40AS21928T-Mobile USA, Inc.RPKI 有効2607:fb90:8a00::
- 2607:fb90:8d00::/40AS21928T-Mobile USA, Inc.RPKI 有効2607:fb90:8d00::
- 2607:fb90:9000::/40AS21928T-Mobile USA, Inc.RPKI 有効2607:fb90:9000::
- 2607:fb90:9100::/40AS21928T-Mobile USA, Inc.RPKI 有効2607:fb90:9100::
- 2607:fb90:9500::/40AS21928T-Mobile USA, Inc.RPKI 有効2607:fb90:9500::
- 2607:fb90:9a00::/40AS21928T-Mobile USA, Inc.RPKI 有効2607:fb90:9a00::
- 2607:fb90:9b00::/40AS21928T-Mobile USA, Inc.RPKI 有効2607:fb90:9b00::
- 2607:fb90:b300::/40AS21928T-Mobile USA, Inc.RPKI 有効2607:fb90:b300::
- 2607:fb90:bb00::/40AS21928T-Mobile USA, Inc.RPKI 有効2607:fb90:bb00::
- 2607:fb90:bd00::/40AS21928T-Mobile USA, Inc.RPKI 有効2607:fb90:bd00::
- 2607:fb90:be00::/40AS21928T-Mobile USA, Inc.RPKI 有効2607:fb90:be00::
- 2607:fb90:cb00::/40AS21928T-Mobile USA, Inc.RPKI 有効2607:fb90:cb00::
- 2607:fb90:d100::/40AS21928T-Mobile USA, Inc.RPKI 有効2607:fb90:d100::
- 2607:fb90:d300::/40AS21928T-Mobile USA, Inc.RPKI 有効2607:fb90:d300::
- 2607:fb90:d500::/40AS21928T-Mobile USA, Inc.RPKI 有効2607:fb90:d500::
- 2607:fb90:db00::/40AS21928T-Mobile USA, Inc.RPKI 有効2607:fb90:db00::
- 2607:fb90:e000::/40AS21928T-Mobile USA, Inc.RPKI 有効2607:fb90:e000::
- 2607:fb90:e200::/40AS21928T-Mobile USA, Inc.RPKI 有効2607:fb90:e200::
- 2607:fb90:e600::/40AS21928T-Mobile USA, Inc.RPKI 有効2607:fb90:e600::
- 2607:fb90:f200::/40AS21928T-Mobile USA, Inc.RPKI 有効2607:fb90:f200::
- 2607:fb90:fa00::/40AS21928T-Mobile USA, Inc.RPKI 有効2607:fb90:fa00::
このテキストはまだ日本語で提供されていません。翻訳が公開されるまで英語で表示しています。
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.