BGP 前缀查询
输入一个前缀(或单个地址)。由我们每日复制的全球路由表回答。
2001:470::/32
精确宣告
- 2001:470::/32AS6939Hurricane Electric LLCRPKI 有效2001:470::
- 注册机构
- ARIN · 美国 · 2001年3月22日
- 分配的地址块
- 2001:470:: – 2001:470:ffff:ffff:ffff:ffff:ffff:ffff
覆盖路由
没有较不具体的路由覆盖它。
更具体的路由
- 2001:470:1:885::/64AS400474GhostFiberRPKI 无效2001:470:1:885::
- 2001:470:21::/48AS18779EGIHostingRPKI 有效2001:470:21::
- 2001:470:22::/48AS217University of MinnesotaRPKI 有效2001:470:22::
- 2001:470:2b::/48AS12266StoreRunner, Inc.RPKI 有效2001:470:2b::
- 2001:470:32::/48AS19969CyberCloud Professionals LLCRPKI 有效2001:470:32::
- 2001:470:4a::/48AS6379A-Link Network Services, Inc.RPKI 有效2001:470:4a::
- 2001:470:50::/48AS36791Portland Internet Hosting LLCRPKI 有效2001:470:50::
- 2001:470:5f::/48AS33309Heliacal NetworksRPKI 有效2001:470:5f::
- 2001:470:60::/48AS50763Robert McKayRPKI 有效2001:470:60::
- 2001:470:79::/48AS54118Robbins Research International IncRPKI 有效2001:470:79::
- 2001:470:8f::/48AS22296Vorsk LLCRPKI 有效2001:470:8f::
- 2001:470:96::/48AS55243Cedar Wireless, Inc.RPKI 有效2001:470:96::
- 2001:470:9a::/48AS17197The Daedelus GroupRPKI 有效2001:470:9a::
- 2001:470:a3::/48AS400765Omaticon CorporationRPKI 有效2001:470:a3::
- 2001:470:d0::/48AS38439ZFS.RENT LLCRPKI 有效2001:470:d0::
- 2001:470:de::/48AS8046NapaNetRPKI 有效2001:470:de::
- 2001:470:e4::/48AS36103Central Utah Telephone, Inc.RPKI 有效2001:470:e4::
- 2001:470:ed::/48AS11399Williams CollegeRPKI 有效2001:470:ed::
- 2001:470:f0::/48AS21589City of San JoseRPKI 有效2001:470:f0::
- 2001:470:f6::/48AS13925Null Route NetworksRPKI 有效2001:470:f6::
- 2001:470:f8::/48AS64238DNS-OARCRPKI 有效2001:470:f8::
- 2001:470:109::/48AS400719RJN ServicesRPKI 有效2001:470:109::
- 2001:470:113::/48AS15096Steven NobleRPKI 有效2001:470:113::
- 2001:470:120::/48AS63343Linear 1 Technologies, LLCRPKI 有效2001:470:120::
- 2001:470:121::/48AS46577Halibut Electronics, IncRPKI 有效2001:470:121::
- 2001:470:139::/48AS46997Black Mesa CorporationRPKI 有效2001:470:139::
- 2001:470:13e::/48AS14979Aeronet WirelessRPKI 有效2001:470:13e::
- 2001:470:142::/48AS22989Free Software Foundation, Inc.RPKI 有效2001:470:142::
- 2001:470:151::/48AS17117RITSnet, Inc.RPKI 有效2001:470:151::
- 2001:470:158::/48AS398922Jubilee Data Systems, LLCRPKI 有效2001:470:158::
- 2001:470:15f::/48AS58299Openfactory GmbHRPKI 有效2001:470:15f::
- 2001:470:16e::/48AS36610East Kentucky Network, LLC.RPKI 有效2001:470:16e::
- 2001:470:182::/48AS401742ServerOptimaRPKI 有效2001:470:182::
- 2001:470:241::/48AS11232Midcontinent CommunicationsRPKI 有效2001:470:241::
- 2001:470:2cf::/48AS132139VECLOUD LIMITEDRPKI 有效2001:470:2cf::
- 2001:470:309::/48AS132139VECLOUD LIMITEDRPKI 有效2001:470:309::
- 2001:470:3b6::/48AS893Ninja-IX FoundationRPKI 有效2001:470:3b6::
- 2001:470:40a::/48AS38439ZFS.RENT LLCRPKI 有效2001:470:40a::
- 2001:470:491::/48AS18526DDPS Networks, LLCRPKI 有效2001:470:491::
- 2001:470:526::/48AS5065Bunny CommunicationsRPKI 有效2001:470:526::
- 2001:470:5ef::/48AS24062NexusRPKI 有效2001:470:5ef::
- 2001:470:5f5::/48AS26523Province of New BrunswickRPKI 有效2001:470:5f5::
此内容尚无中文(中国)版本。在发布译文之前以英语显示。
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.