BGPプレフィックス検索
プレフィックス（または単一のアドレス）を入力してください。世界のルーティングテーブルを毎日複製したデータから回答します。
65.88.0.0/14
完全一致で広報
- 65.88.0.0/14AS3356Level 3 Parent, LLCRPKI ROAなし65.88.0.0
- レジストリ
- ARIN · アメリカ合衆国 · 2000/12/21
- 割り振りブロック
- 65.88.0.0 – 65.91.255.255
包含する経路
包含する集約経路はありません。
より詳細な経路
- 65.88.84.0/22AS62CyrusOne LLCRPKI ROAなし65.88.84.0
- 65.88.85.0/24AS401985Family DollarRPKI ROAなし65.88.85.0
- 65.88.88.0/23AS35999The New York Public Library, Astor, Lenox, and Tilden FoundationsRPKI ROAなし65.88.88.0
- 65.88.89.0/24AS35999The New York Public Library, Astor, Lenox, and Tilden FoundationsRPKI ROAなし65.88.89.0
- 65.88.96.0/20AS6621Hughes Network Systems, LLCRPKI ROAなし65.88.96.0
- 65.89.28.0/24AS14590Desert Schools Federal Credit UnionRPKI ROAなし65.89.28.0
- 65.89.172.0/24AS29946Union WirelessRPKI ROAなし65.89.172.0
- 65.89.173.0/24AS29946Union WirelessRPKI ROAなし65.89.173.0
- 65.89.176.0/23AS3356Level 3 Parent, LLCRPKI ROAなし65.89.176.0
- 65.89.208.0/23AS3356Level 3 Parent, LLCRPKI ROAなし65.89.208.0
- 65.90.11.0/24AS16574Gtek Computers LLCRPKI ROAなし65.90.11.0
- 65.90.67.0/24AS80General Electric CompanyRPKI ROAなし65.90.67.0
- 65.90.80.0/21AS62CyrusOne LLCRPKI ROAなし65.90.80.0
- 65.90.138.0/24AS32342Genex Services IncRPKI ROAなし65.90.138.0
- 65.91.11.0/24AS3356Level 3 Parent, LLCRPKI ROAなし65.91.11.0
- 65.91.162.0/24AS15065Slic Network Solutions, IncRPKI ROAなし65.91.162.0
- 65.91.196.0/24AS16574Gtek Computers LLCRPKI ROAなし65.91.196.0
- 65.91.197.0/24AS16574Gtek Computers LLCRPKI ROAなし65.91.197.0
- 65.91.198.0/24AS16574Gtek Computers LLCRPKI ROAなし65.91.198.0
- 65.91.199.0/24AS16574Gtek Computers LLCRPKI ROAなし65.91.199.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.