BGP 前缀查询
输入一个前缀(或单个地址)。由我们每日复制的全球路由表回答。
44.128.0.0/10
精确宣告
- 44.128.0.0/10AS7377University of California, San DiegoRPKI 无 ROA44.128.0.0
- 注册机构
- ARIN · 美国 · 1992年7月1日
- 分配的地址块
- 44.128.0.0 – 44.191.255.255
覆盖路由
没有较不具体的路由覆盖它。
更具体的路由
- 44.130.98.0/24AS28748Marc Pauls (AlphaCron Datensysteme)RPKI 无 ROA44.130.98.0
- 44.130.99.0/24AS28748Marc Pauls (AlphaCron Datensysteme)RPKI 无 ROA44.130.99.0
- 44.130.100.0/24AS28748Marc Pauls (AlphaCron Datensysteme)RPKI 无 ROA44.130.100.0
- 44.135.121.0/24AS15102Xplore Inc.RPKI 无 ROA44.135.121.0
- 44.135.160.0/21AS25999Provision Data Systems Inc.RPKI 无 ROA44.135.160.0
- 44.135.163.0/24AS25999Provision Data Systems Inc.RPKI 无 ROA44.135.163.0
- 44.135.168.0/23AS23181Quicksilver WirelessRPKI 无 ROA44.135.168.0
- 44.135.180.0/24AS63479HamWANRPKI 无 ROA44.135.180.0
- 44.135.197.0/24AS26288Keewaytinook OkimakanakRPKI 无 ROA44.135.197.0
- 44.135.199.0/24AS22113Belair TechnologiesRPKI 无 ROA44.135.199.0
- 44.135.208.0/21AS40598British Columbia Frequency Modulation Communications AssociationRPKI 无 ROA44.135.208.0
- 44.135.216.0/23AS25999Provision Data Systems Inc.RPKI 无 ROA44.135.216.0
- 44.135.219.0/24AS63479HamWANRPKI 无 ROA44.135.219.0
- 44.136.58.0/24AS20473The Constant Company, LLCRPKI 无 ROA44.136.58.0
- 44.136.59.0/24AS137219Meltus NetworksRPKI 无 ROA44.136.59.0
- 44.136.138.0/24AS4764Aussie BroadbandRPKI 无 ROA44.136.138.0
- 44.136.158.0/23AS38887NAB Investment Holdings Pty LtdRPKI 无 ROA44.136.158.0
- 44.136.158.0/24AS38887NAB Investment Holdings Pty LtdRPKI 无 ROA44.136.158.0
- 44.136.159.0/24AS38887NAB Investment Holdings Pty LtdRPKI 无 ROA44.136.159.0
- 44.136.160.0/24AS17559Spectrums Core NetworkRPKI 无 ROA44.136.160.0
- 44.136.161.0/24AS56199THOMAX TECH SYDRPKI 无 ROA44.136.161.0
- 44.136.201.0/24AS45671Wholesale Services ProviderRPKI 无 ROA44.136.201.0
- 44.137.0.0/16AS1101SURF B.V.RPKI 无 ROA44.137.0.0
- 44.141.132.0/24AS58302SAMFUNDET-ASRPKI 无 ROA44.141.132.0
- 44.155.0.0/16AS1213ASIERA TECHNOLOGY SERVICES CLGRPKI 无 ROA44.155.0.0
- 44.184.136.0/24AS55016Imperium Inc.RPKI 无 ROA44.184.136.0
- 44.184.137.0/24AS55016Imperium Inc.RPKI 无 ROA44.184.137.0
- 44.184.138.0/24AS55016Imperium Inc.RPKI 无 ROA44.184.138.0
- 44.184.139.0/24AS55016Imperium Inc.RPKI 无 ROA44.184.139.0
- 44.190.5.0/24AS7247Mojo NetworksRPKI 无 ROA44.190.5.0
- 44.190.9.0/24AS15102Xplore Inc.RPKI 无 ROA44.190.9.0
- 44.190.40.0/24AS6556AZSIGNSHOP LLCRPKI 无 ROA44.190.40.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.