BGPプレフィックス検索
プレフィックス（または単一のアドレス）を入力してください。世界のルーティングテーブルを毎日複製したデータから回答します。
34.2.0.0/16
完全一致で広報
- 34.2.0.0/16AS15169Google LLCRPKI 有効34.2.0.0
- レジストリ
- ARIN · アメリカ合衆国 · 2022/05/09
- 割り振りブロック
- 34.2.0.0 – 34.2.255.255
包含する経路
包含する集約経路はありません。
より詳細な経路
- 34.2.0.0/20AS19527Google LLCRPKI 有効34.2.0.0
- 34.2.16.0/20AS15169Google LLCRPKI 有効34.2.16.0
- 34.2.32.0/20AS43515Google Ireland LimitedRPKI 有効34.2.32.0
- 34.2.48.0/20AS15169Google LLCRPKI 有効34.2.48.0
- 34.2.64.0/22AS15169Google LLCRPKI 有効34.2.64.0
- 34.2.68.0/23AS15169Google LLCRPKI 有効34.2.68.0
- 34.2.70.0/23AS15169Google LLCRPKI 有効34.2.70.0
- 34.2.72.0/22AS15169Google LLCRPKI 有効34.2.72.0
- 34.2.76.0/23AS15169Google LLCRPKI 有効34.2.76.0
- 34.2.78.0/23AS15169Google LLCRPKI 有効34.2.78.0
- 34.2.80.0/23AS15169Google LLCRPKI 有効34.2.80.0
- 34.2.82.0/23AS15169Google LLCRPKI 有効34.2.82.0
- 34.2.84.0/24AS15169Google LLCRPKI 有効34.2.84.0
- 34.2.85.0/24AS15169Google LLCRPKI 有効34.2.85.0
- 34.2.86.0/23AS43515Google Ireland LimitedRPKI 有効34.2.86.0
- 34.2.88.0/23AS43515Google Ireland LimitedRPKI 有効34.2.88.0
- 34.2.90.0/23AS19527Google LLCRPKI 有効34.2.90.0
- 34.2.92.0/23AS15169Google LLCRPKI 有効34.2.92.0
- 34.2.94.0/23AS15169Google LLCRPKI 有効34.2.94.0
- 34.2.96.0/20AS15169Google LLCRPKI 有効34.2.96.0
- 34.2.112.0/24AS43515Google Ireland LimitedRPKI 有効34.2.112.0
- 34.2.113.0/24AS43515Google Ireland LimitedRPKI 有効34.2.113.0
- 34.2.114.0/23AS15169Google LLCRPKI 有効34.2.114.0
- 34.2.116.0/23AS15169Google LLCRPKI 有効34.2.116.0
- 34.2.118.0/23AS15169Google LLCRPKI 有効34.2.118.0
- 34.2.120.0/22AS15169Google LLCRPKI 有効34.2.120.0
- 34.2.124.0/22AS15169Google LLCRPKI 有効34.2.124.0
- 34.2.128.0/17AS15169Google LLCRPKI 有効34.2.128.0
このテキストはまだ日本語で提供されていません。翻訳が公開されるまで英語で表示しています。
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.