BGPプレフィックス検索
プレフィックス(または単一のアドレス)を入力してください。世界のルーティングテーブルを毎日複製したデータから回答します。
206.47.0.0/16
完全一致で広報
- 206.47.0.0/16AS577Bell CanadaRPKI ROAなし206.47.0.0
- レジストリ
- ARIN · カナダ · 1995/07/07
- 割り振りブロック
- 206.47.0.0 – 206.47.31.255
包含する経路
包含する集約経路はありません。
より詳細な経路
- 206.47.0.0/24AS577Bell CanadaRPKI 有効206.47.0.0
- 206.47.11.0/24AS394958County of WellingtonRPKI 有効206.47.11.0
- 206.47.12.0/24AS397168National Capital Freenet IncRPKI 有効206.47.12.0
- 206.47.13.0/24AS397168National Capital Freenet IncRPKI 有効206.47.13.0
- 206.47.14.0/24AS397168National Capital Freenet IncRPKI 有効206.47.14.0
- 206.47.29.0/24AS397168National Capital Freenet IncRPKI 有効206.47.29.0
- 206.47.30.0/23AS397168National Capital Freenet IncRPKI 有効206.47.30.0
- 206.47.38.0/24AS21723GOCO TECHNOLOGY LIMITED PARTNERSHIPRPKI 有効206.47.38.0
- 206.47.42.0/24AS15830Equinix (EMEA) Acquisition Enterprises B.V.RPKI ROAなし206.47.42.0
- 206.47.46.0/24AS21723GOCO TECHNOLOGY LIMITED PARTNERSHIPRPKI 有効206.47.46.0
- 206.47.94.0/23AS397168National Capital Freenet IncRPKI ROAなし206.47.94.0
- 206.47.98.0/24AS577Bell CanadaRPKI 有効206.47.98.0
- 206.47.100.0/23AS397168National Capital Freenet IncRPKI ROAなし206.47.100.0
- 206.47.112.0/23AS397168National Capital Freenet IncRPKI ROAなし206.47.112.0
- 206.47.116.0/23AS397168National Capital Freenet IncRPKI ROAなし206.47.116.0
- 206.47.132.0/24AS40934Fortinet Inc.RPKI 有効206.47.132.0
- 206.47.134.0/24AS21723GOCO TECHNOLOGY LIMITED PARTNERSHIPRPKI 有効206.47.134.0
- 206.47.144.0/22AS21724GOCO TECHNOLOGY LIMITED PARTNERSHIPRPKI 有効206.47.144.0
- 206.47.154.0/24AS21724GOCO TECHNOLOGY LIMITED PARTNERSHIPRPKI 有効206.47.154.0
- 206.47.157.0/24AS21723GOCO TECHNOLOGY LIMITED PARTNERSHIPRPKI 有効206.47.157.0
- 206.47.161.0/24AS30048Convergia Inc.RPKI 有効206.47.161.0
- 206.47.162.0/24AS21724GOCO TECHNOLOGY LIMITED PARTNERSHIPRPKI 有効206.47.162.0
- 206.47.163.0/24AS13727NEXT DIMENSION INCRPKI 有効206.47.163.0
- 206.47.166.0/24AS21724GOCO TECHNOLOGY LIMITED PARTNERSHIPRPKI 有効206.47.166.0
- 206.47.167.0/24AS30048Convergia Inc.RPKI 有効206.47.167.0
- 206.47.173.0/24AS395088Convergia, incRPKI 有効206.47.173.0
- 206.47.178.0/24AS395088Convergia, incRPKI 有効206.47.178.0
- 206.47.181.0/24AS30048Convergia Inc.RPKI 有効206.47.181.0
- 206.47.182.0/24AS396110Creation Technologies LPRPKI 有効206.47.182.0
- 206.47.184.0/24AS40934Fortinet Inc.RPKI 有効206.47.184.0
- 206.47.192.0/24AS25946NetAccess Systems IncRPKI 有効206.47.192.0
- 206.47.196.0/24AS35911TelebecRPKI 有効206.47.196.0
- 206.47.198.0/24AS30048Convergia Inc.RPKI 有効206.47.198.0
- 206.47.201.0/24AS36522BELL MOBILITY INC.RPKI 有効206.47.201.0
- 206.47.216.0/24AS35911TelebecRPKI 有効206.47.216.0
- 206.47.233.0/24AS36522BELL MOBILITY INC.RPKI 有効206.47.233.0
- 206.47.234.0/24AS36522BELL MOBILITY INC.RPKI 有効206.47.234.0
- 206.47.239.0/24AS30048Convergia Inc.RPKI 有効206.47.239.0
- 206.47.240.0/24AS30048Convergia Inc.RPKI 有効206.47.240.0
- 206.47.249.0/24AS577Bell CanadaRPKI 有効206.47.249.0
- 206.47.251.0/24AS36522BELL MOBILITY INC.RPKI 有効206.47.251.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.