BGPプレフィックス検索
プレフィックス（または単一のアドレス）を入力してください。世界のルーティングテーブルを毎日複製したデータから回答します。
74.82.0.0/18
完全一致で広報
- 74.82.0.0/18AS6939Hurricane Electric LLCRPKI 有効74.82.0.0
- レジストリ
- ARIN · アメリカ合衆国 · 2008/07/22
- 割り振りブロック
- 74.82.0.0 – 74.82.63.255
包含する経路
包含する集約経路はありません。
より詳細な経路
- 74.82.0.0/24AS394740Consolidated CooperativeRPKI 有効74.82.0.0
- 74.82.6.0/23AS36103Central Utah Telephone, Inc.RPKI 有効74.82.6.0
- 74.82.8.0/24AS54288SolidTools Technology, Inc.RPKI 有効74.82.8.0
- 74.82.16.0/24AS394230Civilized Discourse Construction Kit, Inc.RPKI 有効74.82.16.0
- 74.82.22.0/23AS6939Hurricane Electric LLCRPKI 有効74.82.22.0
- 74.82.25.0/24AS54466ISSQUARED, Inc.RPKI 有効74.82.25.0
- 74.82.28.0/23AS39499647-2339071RPKI 有効74.82.28.0
- 74.82.30.0/24AS39499647-2339071RPKI 有効74.82.30.0
- 74.82.31.0/24AS39499647-2339071RPKI 有効74.82.31.0
- 74.82.34.0/24AS398885Aerwave, Inc.RPKI 有効74.82.34.0
- 74.82.43.0/24AS18779EGIHostingRPKI 有効74.82.43.0
- 74.82.44.0/23AS36103Central Utah Telephone, Inc.RPKI 有効74.82.44.0
- 74.82.46.0/24AS6939Hurricane Electric LLCRPKI 有効74.82.46.0
- 74.82.48.0/22AS6939Hurricane Electric LLCRPKI 有効74.82.48.0
- 74.82.53.0/24AS39499647-2339071RPKI 有効74.82.53.0
- 74.82.54.0/23AS36103Central Utah Telephone, Inc.RPKI 有効74.82.54.0
- 74.82.56.0/24AS63186Call One Inc.RPKI 有効74.82.56.0
- 74.82.57.0/24AS36103Central Utah Telephone, Inc.RPKI 有効74.82.57.0
- 74.82.58.0/24AS401977Sierra Nevada CommunicationsRPKI 有効74.82.58.0
- 74.82.63.0/24AS401742ServerOptimaRPKI 有効74.82.63.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.