BGPプレフィックス検索
プレフィックス(または単一のアドレス)を入力してください。世界のルーティングテーブルを毎日複製したデータから回答します。
63.245.0.0/17
完全一致で広報
- 63.245.0.0/17AS23520Columbus Networks USA, Inc.RPKI ROAなし63.245.0.0
- レジストリ
- ARIN · アメリカ合衆国 · 2002/10/22
- 割り振りブロック
- 63.245.0.0 – 63.245.127.255
包含する経路
包含する集約経路はありません。
より詳細な経路
- 63.245.0.0/18AS23520Columbus Networks USA, Inc.RPKI 有効63.245.0.0
- 63.245.1.0/24AS23520Columbus Networks USA, Inc.RPKI 有効63.245.1.0
- 63.245.2.0/24AS23520Columbus Networks USA, Inc.RPKI 有効63.245.2.0
- 63.245.8.0/21AS27696LIBERTY NETWORKS HONDURAS, SOCIEDAD DE RESPONSABILIDAD LIMITADARPKI 有効63.245.8.0
- 63.245.8.0/22AS27696LIBERTY NETWORKS HONDURAS, SOCIEDAD DE RESPONSABILIDAD LIMITADARPKI 有効63.245.8.0
- 63.245.8.0/24AS27696LIBERTY NETWORKS HONDURAS, SOCIEDAD DE RESPONSABILIDAD LIMITADARPKI 有効63.245.8.0
- 63.245.9.0/24AS27696LIBERTY NETWORKS HONDURAS, SOCIEDAD DE RESPONSABILIDAD LIMITADARPKI 有効63.245.9.0
- 63.245.10.0/24AS27696LIBERTY NETWORKS HONDURAS, SOCIEDAD DE RESPONSABILIDAD LIMITADARPKI 有効63.245.10.0
- 63.245.12.0/24AS27696LIBERTY NETWORKS HONDURAS, SOCIEDAD DE RESPONSABILIDAD LIMITADARPKI 有効63.245.12.0
- 63.245.13.0/24AS27696LIBERTY NETWORKS HONDURAS, SOCIEDAD DE RESPONSABILIDAD LIMITADARPKI 有効63.245.13.0
- 63.245.14.0/24AS27696LIBERTY NETWORKS HONDURAS, SOCIEDAD DE RESPONSABILIDAD LIMITADARPKI 有効63.245.14.0
- 63.245.15.0/24AS27696LIBERTY NETWORKS HONDURAS, SOCIEDAD DE RESPONSABILIDAD LIMITADARPKI 有効63.245.15.0
- 63.245.18.0/24AS52286LIBERTY NETWORKS GUATEMALA, LIMITADARPKI 有効63.245.18.0
- 63.245.19.0/24AS52286LIBERTY NETWORKS GUATEMALA, LIMITADARPKI 有効63.245.19.0
- 63.245.29.0/24AS23520Columbus Networks USA, Inc.RPKI 有効63.245.29.0
- 63.245.32.0/24AS23520Columbus Networks USA, Inc.RPKI 有効63.245.32.0
- 63.245.64.0/21AS23520Columbus Networks USA, Inc.RPKI 有効63.245.64.0
- 63.245.69.0/24AS23520Columbus Networks USA, Inc.RPKI 有効63.245.69.0
- 63.245.72.0/21AS23520Columbus Networks USA, Inc.RPKI 有効63.245.72.0
- 63.245.72.0/24AS23520Columbus Networks USA, Inc.RPKI 有効63.245.72.0
- 63.245.80.0/20AS23520Columbus Networks USA, Inc.RPKI ROAなし63.245.80.0
- 63.245.88.0/24AS62627WorldNet Telecommunications, LLCRPKI ROAなし63.245.88.0
- 63.245.89.0/24AS62627WorldNet Telecommunications, LLCRPKI ROAなし63.245.89.0
- 63.245.91.0/24AS23520Columbus Networks USA, Inc.RPKI 有効63.245.91.0
- 63.245.93.0/24AS62627WorldNet Telecommunications, LLCRPKI ROAなし63.245.93.0
- 63.245.95.0/24AS62627WorldNet Telecommunications, LLCRPKI ROAなし63.245.95.0
- 63.245.96.0/19AS23520Columbus Networks USA, Inc.RPKI ROAなし63.245.96.0
- 63.245.104.0/24AS23520Columbus Networks USA, Inc.RPKI 有効63.245.104.0
- 63.245.105.0/24AS265590ABIX TELECOMUNICACIONES S.A. DE C.V.RPKI 有効63.245.105.0
- 63.245.108.0/23AS52233Columbus Communications Curacao NVRPKI ROAなし63.245.108.0
- 63.245.111.0/24AS23520Columbus Networks USA, Inc.RPKI 有効63.245.111.0
- 63.245.112.0/20AS8014Bahamas Telecommunications CorporationRPKI 有効63.245.112.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.