BGPプレフィックス検索
プレフィックス(または単一のアドレス)を入力してください。世界のルーティングテーブルを毎日複製したデータから回答します。
200.54.0.0/16
完全一致で広報
- 200.54.0.0/16AS16629CTC. CORP S.A. (TELEFONICA EMPRESAS)RPKI 有効200.54.0.0
- レジストリ
- LACNIC · チリ · 1999/11/09
- 割り振りブロック
- 200.54.0.0 – 200.54.255.255
包含する経路
包含する集約経路はありません。
より詳細な経路
- 200.54.96.0/24AS16629CTC. CORP S.A. (TELEFONICA EMPRESAS)RPKI 有効200.54.96.0
- 200.54.108.0/24AS52310Derco SPARPKI 有効200.54.108.0
- 200.54.114.0/24AS11340Red Universitaria NacionalRPKI 有効200.54.114.0
- 200.54.115.0/24AS52230Mapfre Compania de SegurosRPKI 有効200.54.115.0
- 200.54.120.0/24AS27880ATENTO CHILE S.A.RPKI 有効200.54.120.0
- 200.54.125.0/24AS52396TELEFONICA CHILE S.A. (MAYORISTAS)RPKI 有効200.54.125.0
- 200.54.128.0/20AS7418TELEFONICA CHILE S.A.RPKI 有効200.54.128.0
- 200.54.144.0/23AS15311TELEFONICA EMPRESAS CHILE SARPKI 有効200.54.144.0
- 200.54.146.0/24AS15311TELEFONICA EMPRESAS CHILE SARPKI 有効200.54.146.0
- 200.54.147.0/24AS7418TELEFONICA CHILE S.A.RPKI 有効200.54.147.0
- 200.54.153.0/24AS15311TELEFONICA EMPRESAS CHILE SARPKI 有効200.54.153.0
- 200.54.154.0/23AS15311TELEFONICA EMPRESAS CHILE SARPKI 有効200.54.154.0
- 200.54.156.0/22AS15311TELEFONICA EMPRESAS CHILE SARPKI 有効200.54.156.0
- 200.54.160.0/20AS15311TELEFONICA EMPRESAS CHILE SARPKI 有効200.54.160.0
- 200.54.176.0/22AS15311TELEFONICA EMPRESAS CHILE SARPKI 有効200.54.176.0
- 200.54.181.0/24AS15311TELEFONICA EMPRESAS CHILE SARPKI 有効200.54.181.0
- 200.54.182.0/23AS15311TELEFONICA EMPRESAS CHILE SARPKI 有効200.54.182.0
- 200.54.184.0/22AS15311TELEFONICA EMPRESAS CHILE SARPKI 有効200.54.184.0
- 200.54.188.0/24AS15311TELEFONICA EMPRESAS CHILE SARPKI 有効200.54.188.0
- 200.54.193.0/24AS15311TELEFONICA EMPRESAS CHILE SARPKI 有効200.54.193.0
- 200.54.194.0/24AS15311TELEFONICA EMPRESAS CHILE SARPKI 有効200.54.194.0
- 200.54.196.0/23AS15311TELEFONICA EMPRESAS CHILE SARPKI 有効200.54.196.0
- 200.54.199.0/24AS15311TELEFONICA EMPRESAS CHILE SARPKI 有効200.54.199.0
- 200.54.215.0/24AS16629CTC. CORP S.A. (TELEFONICA EMPRESAS)RPKI 有効200.54.215.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.