本文へスキップ
ipaddress.tr

BGPプレフィックス検索

プレフィックス（または単一のアドレス）を入力してください。世界のルーティングテーブルを毎日複製したデータから回答します。

例:

59.0.0.0/11

単一のコレクター（APNIC）の視点です。そこに届く前にフィルタされた経路は表示されません。

完全一致で広報

レジストリ
APNIC · 韓国 · 2004/08/02
割り振りブロック
59.0.0.0 – 59.31.255.255

包含する経路

0

包含する集約経路はありません。

より詳細な経路

40個の起源ASから111個のより詳細な経路

最初の100件を表示しています。

このテキストはまだ日本語で提供されていません。翻訳が公開されるまで英語で表示しています。

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.

関連