BGPプレフィックス検索
プレフィックス(または単一のアドレス)を入力してください。世界のルーティングテーブルを毎日複製したデータから回答します。
203.233.0.0/17
完全一致で広報
- 203.233.0.0/17AS3786LG DACOM CorporationRPKI ROAなし203.233.0.0
- レジストリ
- APNIC · 韓国 · 1996/02/16
- 割り振りブロック
- 203.233.0.0 – 203.233.127.255
包含する経路
包含する集約経路はありません。
より詳細な経路
- 203.233.9.0/24AS18373KOOKMIN BANKRPKI ROAなし203.233.9.0
- 203.233.22.0/24AS23573OCI Information CommunicationRPKI ROAなし203.233.22.0
- 203.233.25.0/24AS38707TosspaymentsRPKI ROAなし203.233.25.0
- 203.233.43.0/24AS18295ABL Life Insurance Co., Ltd.RPKI ROAなし203.233.43.0
- 203.233.44.0/24AS18295ABL Life Insurance Co., Ltd.RPKI ROAなし203.233.44.0
- 203.233.48.0/24AS38707TosspaymentsRPKI ROAなし203.233.48.0
- 203.233.54.0/23AS17841NATIONAL INFORMATION RESOURCES SERVICERPKI ROAなし203.233.54.0
- 203.233.56.0/23AS17841NATIONAL INFORMATION RESOURCES SERVICERPKI ROAなし203.233.56.0
- 203.233.72.0/24AS38428Korea Information Communicaions Co.RPKI ROAなし203.233.72.0
- 203.233.72.0/25AS38428Korea Information Communicaions Co.RPKI ROAなし203.233.72.0
- 203.233.72.128/25AS38428Korea Information Communicaions Co.RPKI ROAなし203.233.72.128
- 203.233.73.0/24AS38428Korea Information Communicaions Co.RPKI ROAなし203.233.73.0
- 203.233.73.0/25AS38428Korea Information Communicaions Co.RPKI ROAなし203.233.73.0
- 203.233.73.128/25AS38428Korea Information Communicaions Co.RPKI ROAなし203.233.73.128
- 203.233.74.0/24AS38428Korea Information Communicaions Co.RPKI ROAなし203.233.74.0
- 203.233.74.0/25AS38428Korea Information Communicaions Co.RPKI ROAなし203.233.74.0
- 203.233.74.128/25AS38428Korea Information Communicaions Co.RPKI ROAなし203.233.74.128
- 203.233.82.0/24AS9684HANWHA Corp. Information Service div.RPKI ROAなし203.233.82.0
- 203.233.85.0/24AS9968KYOBO Life Insurance Co., Ltd.RPKI ROAなし203.233.85.0
- 203.233.91.0/24AS9693KFTCRPKI ROAなし203.233.91.0
- 203.233.116.0/24AS38707TosspaymentsRPKI ROAなし203.233.116.0
- 203.233.124.0/24AS38707TosspaymentsRPKI ROAなし203.233.124.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.