BGPプレフィックス検索
プレフィックス（または単一のアドレス）を入力してください。世界のルーティングテーブルを毎日複製したデータから回答します。
72.2.0.0/18
完全一致で広報
- 72.2.0.0/18AS6327Shaw CommunicationsRPKI ROAなし72.2.0.0
- レジストリ
- ARIN · カナダ · 2004/09/17
- 割り振りブロック
- 72.2.0.0 – 72.2.63.255
包含する経路
包含する集約経路はありません。
より詳細な経路
- 72.2.0.0/19AS6327Shaw CommunicationsRPKI ROAなし72.2.0.0
- 72.2.0.0/21AS6327Shaw CommunicationsRPKI ROAなし72.2.0.0
- 72.2.4.0/22AS53359CUBE Global Storage Ltd.RPKI ROAなし72.2.4.0
- 72.2.6.0/24AS53359CUBE Global Storage Ltd.RPKI ROAなし72.2.6.0
- 72.2.8.0/21AS6327Shaw CommunicationsRPKI ROAなし72.2.8.0
- 72.2.16.0/21AS6327Shaw CommunicationsRPKI ROAなし72.2.16.0
- 72.2.18.0/24AS3963743C Information Solutions Inc.RPKI ROAなし72.2.18.0
- 72.2.19.0/24AS3963743C Information Solutions Inc.RPKI ROAなし72.2.19.0
- 72.2.22.0/24AS29988Rogers Communications Canada Inc.RPKI ROAなし72.2.22.0
- 72.2.23.0/24AS6327Shaw CommunicationsRPKI ROAなし72.2.23.0
- 72.2.24.0/21AS6327Shaw CommunicationsRPKI ROAなし72.2.24.0
- 72.2.32.0/19AS6327Shaw CommunicationsRPKI ROAなし72.2.32.0
- 72.2.32.0/21AS6327Shaw CommunicationsRPKI ROAなし72.2.32.0
- 72.2.40.0/21AS6327Shaw CommunicationsRPKI ROAなし72.2.40.0
- 72.2.46.0/24AS6327Shaw CommunicationsRPKI ROAなし72.2.46.0
- 72.2.48.0/21AS6327Shaw CommunicationsRPKI ROAなし72.2.48.0
- 72.2.56.0/22AS6327Shaw CommunicationsRPKI ROAなし72.2.56.0
- 72.2.60.0/22AS6327Shaw CommunicationsRPKI ROAなし72.2.60.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.