BGPプレフィックス検索
プレフィックス(または単一のアドレス)を入力してください。世界のルーティングテーブルを毎日複製したデータから回答します。
104.132.0.0/14
完全一致で広報
- 104.132.0.0/14AS36384Google LLCRPKI 有効104.132.0.0
- レジストリ
- ARIN · アメリカ合衆国 · 2014/07/03
- 割り振りブロック
- 104.132.0.0 – 104.135.255.255
包含する経路
包含する集約経路はありません。
より詳細な経路
- 104.132.12.0/24AS4637Telstra GlobalRPKI 無効104.132.12.0
- 104.132.16.0/23AS36411Google LLCRPKI 有効104.132.16.0
- 104.132.16.0/24AS36411Google LLCRPKI 有効104.132.16.0
- 104.132.254.0/24AS36384Google LLCRPKI 有効104.132.254.0
- 104.133.128.0/23AS396982Google LLCRPKI 有効104.133.128.0
- 104.133.196.0/22AS36411Google LLCRPKI 有効104.133.196.0
- 104.133.196.0/23AS36411Google LLCRPKI 有効104.133.196.0
- 104.133.198.0/23AS36411Google LLCRPKI 有効104.133.198.0
- 104.134.70.0/23AS36411Google LLCRPKI 有効104.134.70.0
- 104.134.70.0/24AS36411Google LLCRPKI 有効104.134.70.0
- 104.134.71.0/24AS36411Google LLCRPKI 有効104.134.71.0
- 104.134.72.0/22AS36411Google LLCRPKI 有効104.134.72.0
- 104.134.72.0/23AS36411Google LLCRPKI 有効104.134.72.0
- 104.134.74.0/23AS36411Google LLCRPKI 有効104.134.74.0
- 104.134.76.0/23AS36411Google LLCRPKI 有効104.134.76.0
- 104.134.76.0/24AS36411Google LLCRPKI 有効104.134.76.0
- 104.134.77.0/24AS36411Google LLCRPKI 有効104.134.77.0
- 104.134.96.0/20AS36411Google LLCRPKI 有効104.134.96.0
- 104.134.112.0/21AS36411Google LLCRPKI 有効104.134.112.0
- 104.134.120.0/22AS36411Google LLCRPKI 有効104.134.120.0
- 104.134.140.0/24AS395973Google LLCRPKI 有効104.134.140.0
- 104.134.206.0/24AS395973Google LLCRPKI 有効104.134.206.0
- 104.134.232.0/24AS36383Google LLCRPKI 有効104.134.232.0
- 104.134.233.0/24AS36411Google LLCRPKI 有効104.134.233.0
- 104.134.236.0/24AS36383Google LLCRPKI 有効104.134.236.0
- 104.134.237.0/24AS36411Google LLCRPKI 有効104.134.237.0
- 104.134.240.0/24AS41264Google Switzerland GmbHRPKI 有効104.134.240.0
- 104.134.241.0/24AS41264Google Switzerland GmbHRPKI 有効104.134.241.0
- 104.134.244.0/24AS41264Google Switzerland GmbHRPKI 有効104.134.244.0
- 104.135.0.0/20AS36383Google LLCRPKI 有効104.135.0.0
- 104.135.16.0/21AS36383Google LLCRPKI 有効104.135.16.0
- 104.135.24.0/21AS36383Google LLCRPKI 有効104.135.24.0
- 104.135.136.0/21AS36411Google LLCRPKI 有効104.135.136.0
- 104.135.176.0/20AS36383Google LLCRPKI 有効104.135.176.0
- 104.135.176.0/22AS36383Google LLCRPKI 有効104.135.176.0
- 104.135.180.0/22AS36383Google LLCRPKI 有効104.135.180.0
- 104.135.184.0/22AS36383Google LLCRPKI 有効104.135.184.0
- 104.135.188.0/23AS36383Google LLCRPKI 有効104.135.188.0
- 104.135.190.0/23AS36383Google LLCRPKI 有効104.135.190.0
- 104.135.192.0/20AS36383Google LLCRPKI 有効104.135.192.0
- 104.135.192.0/23AS36383Google LLCRPKI 有効104.135.192.0
- 104.135.196.0/22AS36383Google LLCRPKI 有効104.135.196.0
- 104.135.200.0/24AS36383Google LLCRPKI 有効104.135.200.0
- 104.135.201.0/24AS36383Google LLCRPKI 有効104.135.201.0
- 104.135.202.0/23AS36383Google LLCRPKI 有効104.135.202.0
- 104.135.204.0/23AS36383Google LLCRPKI 有効104.135.204.0
- 104.135.208.0/20AS36411Google LLCRPKI 有効104.135.208.0
- 104.135.208.0/23AS36411Google LLCRPKI 有効104.135.208.0
- 104.135.210.0/23AS36411Google LLCRPKI 有効104.135.210.0
- 104.135.212.0/22AS36411Google LLCRPKI 有効104.135.212.0
- 104.135.216.0/24AS36411Google LLCRPKI 有効104.135.216.0
- 104.135.217.0/24AS36411Google LLCRPKI 有効104.135.217.0
- 104.135.218.0/23AS36411Google LLCRPKI 有効104.135.218.0
- 104.135.220.0/23AS36411Google LLCRPKI 有効104.135.220.0
- 104.135.222.0/24AS36411Google LLCRPKI 有効104.135.222.0
- 104.135.240.0/23AS36383Google LLCRPKI 有効104.135.240.0
- 104.135.242.0/23AS36411Google LLCRPKI 有効104.135.242.0
- 104.135.244.0/22AS36411Google LLCRPKI 有効104.135.244.0
- 104.135.248.0/22AS36383Google LLCRPKI 有効104.135.248.0
- 104.135.252.0/24AS36383Google LLCRPKI 有効104.135.252.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.