BGPプレフィックス検索
プレフィックス(または単一のアドレス)を入力してください。世界のルーティングテーブルを毎日複製したデータから回答します。
2400:58a0::/32
完全一致で広報
- 2400:58a0::/32AS38008Aperture Science LimitedRPKI ROAなし2400:58a0::
- レジストリ
- APNIC · オーストラリア · 2022/02/04
- 割り振りブロック
- 2400:58a0:: – 2400:58a0:ffff:ffff:ffff:ffff:ffff:ffff
包含する経路
包含する集約経路はありません。
より詳細な経路
- 2400:58a0:100::/44AS38008Aperture Science LimitedRPKI 有効2400:58a0:100::
- 2400:58a0:100::/48AS38008Aperture Science LimitedRPKI 有効2400:58a0:100::
- 2400:58a0:1000::/44AS149500Shane RenshawRPKI 有効2400:58a0:1000::
- 2400:58a0:1410::/48AS38008Aperture Science LimitedRPKI 有効2400:58a0:1410::
- 2400:58a0:1411::/48AS38008Aperture Science LimitedRPKI 有効2400:58a0:1411::
- 2400:58a0:141d::/48AS38008Aperture Science LimitedRPKI 有効2400:58a0:141d::
- 2400:58a0:1c00::/48AS151669Xiaofei XuRPKI 有効2400:58a0:1c00::
- 2400:58a0:1c0b::/48AS151669Xiaofei XuRPKI 有効2400:58a0:1c0b::
- 2400:58a0:1c0d::/48AS151669Xiaofei XuRPKI 有効2400:58a0:1c0d::
- 2400:58a0:1c0e::/48AS151669Xiaofei XuRPKI 有効2400:58a0:1c0e::
- 2400:58a0:d000::/40AS18250GEEK NETWORKS PTY LIMITEDRPKI 有効2400:58a0:d000::
- 2400:58a0:d100::/40AS18250GEEK NETWORKS PTY LIMITEDRPKI 有効2400:58a0:d100::
- 2400:58a0:d200::/40AS18250GEEK NETWORKS PTY LIMITEDRPKI 有効2400:58a0:d200::
- 2400:58a0:d300::/40AS18250GEEK NETWORKS PTY LIMITEDRPKI 有効2400:58a0:d300::
- 2400:58a0:d400::/40AS18250GEEK NETWORKS PTY LIMITEDRPKI 有効2400:58a0:d400::
- 2400:58a0:d500::/40AS18250GEEK NETWORKS PTY LIMITEDRPKI 有効2400:58a0:d500::
- 2400:58a0:d600::/40AS18250GEEK NETWORKS PTY LIMITEDRPKI 有効2400:58a0:d600::
- 2400:58a0:d700::/40AS18250GEEK NETWORKS PTY LIMITEDRPKI 有効2400:58a0:d700::
- 2400:58a0:d800::/40AS18250GEEK NETWORKS PTY LIMITEDRPKI 有効2400:58a0:d800::
- 2400:58a0:d900::/40AS18250GEEK NETWORKS PTY LIMITEDRPKI 有効2400:58a0:d900::
- 2400:58a0:da00::/40AS18250GEEK NETWORKS PTY LIMITEDRPKI 有効2400:58a0:da00::
- 2400:58a0:db00::/40AS18250GEEK NETWORKS PTY LIMITEDRPKI 有効2400:58a0:db00::
- 2400:58a0:dc00::/40AS18250GEEK NETWORKS PTY LIMITEDRPKI 有効2400:58a0:dc00::
- 2400:58a0:dd00::/40AS18250GEEK NETWORKS PTY LIMITEDRPKI 有効2400:58a0:dd00::
- 2400:58a0:de00::/40AS18250GEEK NETWORKS PTY LIMITEDRPKI 有効2400:58a0:de00::
- 2400:58a0:df00::/40AS18250GEEK NETWORKS PTY LIMITEDRPKI 有効2400:58a0:df00::
- 2400:58a0:e000::/36AS18250GEEK NETWORKS PTY LIMITEDRPKI 有効2400:58a0:e000::
- 2400:58a0:f000::/36AS38008Aperture Science LimitedRPKI 有効2400:58a0:f000::
このテキストはまだ日本語で提供されていません。翻訳が公開されるまで英語で表示しています。
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.