BGPプレフィックス検索
プレフィックス(または単一のアドレス)を入力してください。世界のルーティングテーブルを毎日複製したデータから回答します。
79.127.0.0/17
完全一致で広報
- 79.127.0.0/17AS43754Asiatech Data Transmission companyRPKI 有効79.127.0.0
- レジストリ
- RIPE NCC · イラン · 2007/09/17
- 割り振りブロック
- 79.127.0.0 – 79.127.127.255
包含する経路
包含する集約経路はありません。
より詳細な経路
- 79.127.0.0/18AS43754Asiatech Data Transmission companyRPKI 有効79.127.0.0
- 79.127.0.0/19AS43754Asiatech Data Transmission companyRPKI 有効79.127.0.0
- 79.127.0.0/22AS43754Asiatech Data Transmission companyRPKI 有効79.127.0.0
- 79.127.4.0/22AS43754Asiatech Data Transmission companyRPKI 有効79.127.4.0
- 79.127.12.0/22AS43754Asiatech Data Transmission companyRPKI 有効79.127.12.0
- 79.127.23.0/24AS43754Asiatech Data Transmission companyRPKI 有効79.127.23.0
- 79.127.24.0/24AS43754Asiatech Data Transmission companyRPKI 有効79.127.24.0
- 79.127.25.0/24AS43754Asiatech Data Transmission companyRPKI 有効79.127.25.0
- 79.127.27.0/24AS43754Asiatech Data Transmission companyRPKI 有効79.127.27.0
- 79.127.32.0/19AS43754Asiatech Data Transmission companyRPKI 有効79.127.32.0
- 79.127.42.0/24AS43754Asiatech Data Transmission companyRPKI 有効79.127.42.0
- 79.127.44.0/23AS44400Ertebatat Sabet Parsian Co. PJSRPKI 有効79.127.44.0
- 79.127.46.0/24AS43415Secure Infrastructure of Transactional Services Company PJSCRPKI 有効79.127.46.0
- 79.127.48.0/20AS43754Asiatech Data Transmission companyRPKI 有効79.127.48.0
- 79.127.59.0/24AS43754Asiatech Data Transmission companyRPKI 有効79.127.59.0
- 79.127.60.0/23AS44400Ertebatat Sabet Parsian Co. PJSRPKI 有効79.127.60.0
- 79.127.64.0/18AS43754Asiatech Data Transmission companyRPKI 有効79.127.64.0
- 79.127.64.0/19AS43754Asiatech Data Transmission companyRPKI 有効79.127.64.0
- 79.127.64.0/24AS61209University of Sistan and BaluchestanRPKI 有効79.127.64.0
- 79.127.65.0/24AS34837Institute for Research in Fundamental SciencesRPKI 有効79.127.65.0
- 79.127.70.0/24AS43754Asiatech Data Transmission companyRPKI 有効79.127.70.0
- 79.127.72.0/22AS43754Asiatech Data Transmission companyRPKI 有効79.127.72.0
- 79.127.76.0/22AS43754Asiatech Data Transmission companyRPKI 有効79.127.76.0
- 79.127.76.0/24AS43754Asiatech Data Transmission companyRPKI 有効79.127.76.0
- 79.127.80.0/20AS43754Asiatech Data Transmission companyRPKI 有効79.127.80.0
- 79.127.84.0/22AS43754Asiatech Data Transmission companyRPKI 有効79.127.84.0
- 79.127.96.0/19AS43754Asiatech Data Transmission companyRPKI 有効79.127.96.0
- 79.127.112.0/22AS43754Asiatech Data Transmission companyRPKI 有効79.127.112.0
- 79.127.114.0/23AS43754Asiatech Data Transmission companyRPKI 有効79.127.114.0
- 79.127.120.0/23AS43754Asiatech Data Transmission companyRPKI 有効79.127.120.0
- 79.127.124.0/24AS43754Asiatech Data Transmission companyRPKI 有効79.127.124.0
- 79.127.125.0/24AS43754Asiatech Data Transmission companyRPKI 有効79.127.125.0
- 79.127.126.0/23AS43754Asiatech Data Transmission companyRPKI 有効79.127.126.0
- 79.127.126.0/24AS43754Asiatech Data Transmission companyRPKI 有効79.127.126.0
- 79.127.127.0/24AS43754Asiatech Data Transmission companyRPKI 有効79.127.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.