BGPプレフィックス検索
プレフィックス(または単一のアドレス)を入力してください。世界のルーティングテーブルを毎日複製したデータから回答します。
205.209.128.0/18
完全一致で広報
- 205.209.128.0/18AS23338UNASSIGNEDRPKI ROAなし205.209.128.0
- レジストリ
- ARIN
- 割り振りブロック
- 205.209.128.0 – 205.209.191.255
包含する経路
包含する集約経路はありません。
より詳細な経路
- 205.209.129.0/24AS23338UNASSIGNEDRPKI ROAなし205.209.129.0
- 205.209.134.0/24AS23338UNASSIGNEDRPKI ROAなし205.209.134.0
- 205.209.150.0/24AS23338UNASSIGNEDRPKI ROAなし205.209.150.0
- 205.209.158.0/24AS23338UNASSIGNEDRPKI ROAなし205.209.158.0
- 205.209.160.0/24AS23338UNASSIGNEDRPKI ROAなし205.209.160.0
- 205.209.162.0/24AS23338UNASSIGNEDRPKI ROAなし205.209.162.0
- 205.209.163.0/24AS23338UNASSIGNEDRPKI ROAなし205.209.163.0
- 205.209.165.0/24AS23338UNASSIGNEDRPKI ROAなし205.209.165.0
- 205.209.170.0/24AS23338UNASSIGNEDRPKI ROAなし205.209.170.0
- 205.209.171.0/24AS23338UNASSIGNEDRPKI ROAなし205.209.171.0
- 205.209.172.0/24AS23338UNASSIGNEDRPKI ROAなし205.209.172.0
- 205.209.173.0/24AS23338UNASSIGNEDRPKI ROAなし205.209.173.0
- 205.209.174.0/24AS23338UNASSIGNEDRPKI ROAなし205.209.174.0
- 205.209.176.0/24AS23338UNASSIGNEDRPKI ROAなし205.209.176.0
- 205.209.177.0/24AS23338UNASSIGNEDRPKI ROAなし205.209.177.0
- 205.209.179.0/24AS23338UNASSIGNEDRPKI ROAなし205.209.179.0
- 205.209.180.0/24AS23338UNASSIGNEDRPKI ROAなし205.209.180.0
- 205.209.181.0/24AS23338UNASSIGNEDRPKI ROAなし205.209.181.0
- 205.209.182.0/23AS23338UNASSIGNEDRPKI ROAなし205.209.182.0
- 205.209.185.0/24AS23338UNASSIGNEDRPKI ROAなし205.209.185.0
- 205.209.186.0/24AS23338UNASSIGNEDRPKI ROAなし205.209.186.0
- 205.209.187.0/24AS23338UNASSIGNEDRPKI ROAなし205.209.187.0
- 205.209.188.0/24AS23338UNASSIGNEDRPKI ROAなし205.209.188.0
- 205.209.189.0/24AS23338UNASSIGNEDRPKI ROAなし205.209.189.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.