BGPプレフィックス検索
プレフィックス(または単一のアドレス)を入力してください。世界のルーティングテーブルを毎日複製したデータから回答します。
74.8.0.0/14
完全一致で広報
- 74.8.0.0/14AS7029Windstream Communications LLCRPKI 有効74.8.0.0
- レジストリ
- ARIN · アメリカ合衆国 · 2006/01/17
- 割り振りブロック
- 74.8.0.0 – 74.11.255.255
包含する経路
包含する集約経路はありません。
より詳細な経路
- 74.8.0.0/24AS397932New York State AssemblyRPKI 有効74.8.0.0
- 74.8.19.0/24AS27338GoNetSpeedRPKI 有効74.8.19.0
- 74.8.52.0/24AS27338GoNetSpeedRPKI 有効74.8.52.0
- 74.8.54.0/24AS27338GoNetSpeedRPKI 有効74.8.54.0
- 74.8.87.0/24AS27338GoNetSpeedRPKI 有効74.8.87.0
- 74.8.94.0/24AS27338GoNetSpeedRPKI 有効74.8.94.0
- 74.8.136.0/24AS27338GoNetSpeedRPKI 有効74.8.136.0
- 74.8.171.0/24AS27338GoNetSpeedRPKI 有効74.8.171.0
- 74.8.216.0/23AS27338GoNetSpeedRPKI 有効74.8.216.0
- 74.8.253.0/24AS27338GoNetSpeedRPKI 有効74.8.253.0
- 74.8.254.0/23AS27338GoNetSpeedRPKI 有効74.8.254.0
- 74.9.4.0/23AS27338GoNetSpeedRPKI 有効74.9.4.0
- 74.9.6.0/24AS27338GoNetSpeedRPKI 有効74.9.6.0
- 74.9.16.0/23AS27338GoNetSpeedRPKI 有効74.9.16.0
- 74.9.224.0/23AS27338GoNetSpeedRPKI 有効74.9.224.0
- 74.10.11.0/24AS7029Windstream Communications LLCRPKI 有効74.10.11.0
- 74.10.20.0/24AS27338GoNetSpeedRPKI 有効74.10.20.0
- 74.10.36.0/24AS27338GoNetSpeedRPKI 有効74.10.36.0
- 74.10.38.0/23AS27338GoNetSpeedRPKI 有効74.10.38.0
- 74.10.44.0/24AS27338GoNetSpeedRPKI 有効74.10.44.0
- 74.10.50.0/24AS27338GoNetSpeedRPKI 有効74.10.50.0
- 74.10.56.0/23AS27338GoNetSpeedRPKI 有効74.10.56.0
- 74.10.73.0/24AS55161Digipress IncRPKI 有効74.10.73.0
- 74.10.154.0/23AS27338GoNetSpeedRPKI 有効74.10.154.0
- 74.10.193.0/24AS27338GoNetSpeedRPKI 有効74.10.193.0
- 74.11.34.0/23AS27338GoNetSpeedRPKI 有効74.11.34.0
- 74.11.209.0/24AS7029Windstream Communications LLCRPKI 有効74.11.209.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.