BGPプレフィックス検索
プレフィックス(または単一のアドレス)を入力してください。世界のルーティングテーブルを毎日複製したデータから回答します。
207.178.96.0/19
完全一致で広報
- 207.178.96.0/19AS27425IdeaTek Telcom, LLCRPKI ROAなし207.178.96.0
- レジストリ
- ARIN · アメリカ合衆国 · 2001/03/23
- 割り振りブロック
- 207.178.96.0 – 207.178.127.255
包含する経路
包含する集約経路はありません。
より詳細な経路
- 207.178.98.0/24AS27425IdeaTek Telcom, LLCRPKI ROAなし207.178.98.0
- 207.178.100.0/22AS27425IdeaTek Telcom, LLCRPKI ROAなし207.178.100.0
- 207.178.102.0/24AS27425IdeaTek Telcom, LLCRPKI ROAなし207.178.102.0
- 207.178.103.0/24AS27425IdeaTek Telcom, LLCRPKI ROAなし207.178.103.0
- 207.178.106.0/24AS27425IdeaTek Telcom, LLCRPKI ROAなし207.178.106.0
- 207.178.108.0/24AS27425IdeaTek Telcom, LLCRPKI ROAなし207.178.108.0
- 207.178.109.0/24AS27425IdeaTek Telcom, LLCRPKI ROAなし207.178.109.0
- 207.178.110.0/24AS27425IdeaTek Telcom, LLCRPKI ROAなし207.178.110.0
- 207.178.112.0/24AS35851Bankers' Bank of KansasRPKI 有効207.178.112.0
- 207.178.114.0/23AS27425IdeaTek Telcom, LLCRPKI ROAなし207.178.114.0
- 207.178.116.0/23AS27425IdeaTek Telcom, LLCRPKI ROAなし207.178.116.0
- 207.178.117.0/24AS27425IdeaTek Telcom, LLCRPKI ROAなし207.178.117.0
- 207.178.119.0/24AS27425IdeaTek Telcom, LLCRPKI ROAなし207.178.119.0
- 207.178.120.0/21AS27425IdeaTek Telcom, LLCRPKI ROAなし207.178.120.0
- 207.178.120.0/24AS27425IdeaTek Telcom, LLCRPKI ROAなし207.178.120.0
- 207.178.121.0/24AS27425IdeaTek Telcom, LLCRPKI ROAなし207.178.121.0
- 207.178.123.0/24AS27425IdeaTek Telcom, LLCRPKI ROAなし207.178.123.0
- 207.178.124.0/23AS27425IdeaTek Telcom, LLCRPKI ROAなし207.178.124.0
- 207.178.126.0/24AS27425IdeaTek Telcom, LLCRPKI ROAなし207.178.126.0
- 207.178.127.0/24AS27425IdeaTek Telcom, LLCRPKI ROAなし207.178.127.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.