N0EMIS-AS Ember Keske is a dormant autonomous system holder in the RIPE NCC region. It holds AS211479 but has no announced prefixes, no business footprint, and no public contacts. The profile establishes a baseline: any future routing activity, registry update, or human operator disclosure would turn this idle dormant entry into an operational concern. Evidence is limited to two RIPE data endpoints; key uncertainties include ownership, location, and intent. Watchpoints center on registry record changes, BGP origination, and the emergence of a named individual.
The entity holds AS211479 but does not originate any BGP announcements, making it a dormant autonomous system holder. It has no visible products, services, customers, or staff, and no public contacts. Its current role is limited to a registry entry with the potential to influence internet routing if it ever begins announcing prefixes.
Any autonomous system holder can begin originating BGP announcements at any time, altering internet traffic paths and creating new routing dependencies. Although inactive today, N0EMIS-AS Ember Keske’s latent capability makes it a monitoring concern: activation could introduce route hijacking risks or unexpected traffic shifts.
Any autonomous system holder can begin originating BGP announcements at any time, altering internet traffic paths and creating new routing dependencies. Although inactive today, N0EMIS-AS Ember Keske’s latent capability makes it a monitoring concern: activation could introduce route hijacking risks or unexpected traffic shifts.
The entity holds AS211479 but does not originate any BGP announcements, making it a dormant autonomous system holder. It has no visible products, services, customers, or staff, and no public contacts. Its current role is limited to a registry entry with the potential to influence internet routing if it ever begins announcing prefixes.
Currently, the entity exerts zero influence on internet routing. If it were to originate prefixes or establish peering, its impact could become significant—redirecting traffic, creating new dependencies, and exposing networks to route leaks or hijacks. The gap between dormant registration and active threat is narrow.
N0EMIS-AS Ember Keske is a dormant autonomous system holder in the RIPE NCC region. It holds AS211479 but has no announced prefixes, no business footprint, and no public contacts. The profile establishes a baseline: any future routing activity, registry update, or human operator disclosure would turn this idle dormant entry into an operational concern. Evidence is limited to two RIPE data endpoints; key uncertainties include ownership, location, and intent. Watchpoints center on registry record changes, BGP origination, and the emergence of a named individual.
Currently, the entity exerts zero influence on internet routing. If it were to originate prefixes or establish peering, its impact could become significant—redirecting traffic, creating new dependencies, and exposing networks to route leaks or hijacks. The gap between dormant registration and active threat is narrow.
| 0.90–1.00 | A | High — direct sources |
| 0.75–0.89 | A/B | Strong |
| 0.55–0.74 | B/C | Medium |
| 0.35–0.54 | C/D | Weak–medium |
| 0.10–0.34 | D | Weak signal |
| 0.00–0.09 | D | Internal monitoring |
Several public sources
N0EMIS-AS Ember Keske
N0EMIS-AS Ember Keske是RIPE NCC注册数据库中自治系统AS211479的注册持有者，但它没有宣告任何IP前缀，也没有任何公开的企业存在。该实体处于休眠状态——一个尚未投入运营的注册条目，具有潜在的路由能力，但在互联网流量中没有实际作用。 另见: 罗伯特·纽沃斯.
为何关注
目前，该实体对互联网路由的影响为零。如果它开始发起前缀或建立对等关系，其影响可能会变得显著——重定向流量、创建新的依赖关系，并使网络面临路由泄露或劫持的风险。休眠注册与活跃威胁之间的差距很窄。 另见: 尤金·贡恰连科.
公开来源显示的内容
根据RIPE NCC的数据，N0EMIS-AS Ember Keske是自治系统AS211479的注册持有者。它没有向全球路由表宣告任何IP前缀，这意味着它目前不参与互联网路由。未发现任何公司网站、PeeringDB条目或公开联系信息，使其成为一个幽灵般的注册条目。 另见: NGA Connect Limited.
任何AS持有者都可以随时开始发起BGP公告。这一举动将立即将这个休眠实体转变为能够重定向流量、建立对等关系，或者在配置错误的情况下发起路由劫持的活跃参与者。目前，风险是假设性的，但潜力是真实的。 另见: Skywolf Inc（天狼公司）.
证据仅限于两个RIPE NCC数据端点。一个确认了AS211479的AS持有者名称；另一个显示零个已宣告前缀。没有额外的公开足迹——没有网站，没有PeeringDB资料，没有商业注册——来补充注册记录。 另见: Devout BV.
唯一可观察的控制界面是RIPE NCC LIR门户。持有凭证的人可以修改AS211479记录、更改联系人或请求IP资源。如果该实体随后配置路由器并宣告前缀，BGP策略将成为第二个更危险的控制点。 另见: FUTURE SPACE SA.
AS211479注册记录的变更——新的联系人、一个地址、一个更名后的组织——将是激活的第一个迹象。BGP前缀发起的开始将把实体从休眠状态转变为运行状态，创建路由依赖。一个有名有姓的个人、一个PeeringDB条目或一个公司网站的出现，同样会改变其轮廓。 另见: Dcent Investments BV.
关于所有权、地理位置、商业目的或意图，我们一无所知。该实体可能是一个为未来使用而预注册的持有者，一个被遗弃的注册，或者是一种故意模糊的存在。没有进一步的公开信号，其目的仍然不透明，风险状况也保持不变。 另见: VoltzzNode Enterprise SRL.
操作层面
该实体持有AS211479，但不发起任何BGP公告，使其成为一个休眠的自治系统持有者。它没有可见的产品、服务、客户或员工，也没有公开联系方式。其当前角色仅限于一个注册条目，如果它开始宣告前缀，就有潜力影响互联网路由。
任何自治系统持有者都可以随时开始发起BGP公告，改变互联网流量路径并建立新的路由依赖。尽管今天处于不活跃状态，N0EMIS-AS Ember Keske的潜在能力使其成为一个监测关注点：激活可能引入路由劫持风险或意外的流量转移。
监测要点
该实体是一个低活动、高不确定性的基础设施持有者。其休眠状态意味着它目前没有引入路由风险，但所有权缺乏透明度使得无法评估意图。从战略上讲，它符合一种预先部署或被遗弃的ASN注册模式，这些注册可以被激活用于善意或恶意目的。监测是一项具有成本效益的预警措施。
关键可观察项：(1) AS211479注册记录的任何修改——特别是添加联系人或地址细节；(2) 任何前缀在AS211479下的BGP起源事件；(3) 在注册数据中出现个人作为admin-c或tech-c；(4) 创建PeeringDB条目或声称代表N0EMIS-AS Ember Keske的公开网站。
关键差距：完全缺乏公司注册（地点、管辖地），没有指定的负责人，没有明确的商业目的，也没有路由历史。填补任何这些差距都将把评估从休眠条目转变为具有可衡量风险概况的运营实体。
来源
- AS211479的RIPE NCC AS概览 - 确认N0EMIS-AS Ember Keske是自治系统AS211479的注册持有者。
- AS211479的RIPEstat已宣告前缀 - 显示AS211479有零个公开宣告的IP前缀，表明没有活跃的路由参与。
Domain of operation
N0EMIS-AS Ember Keske is the registered holder of autonomous system AS211479 in the RIPE NCC registry, yet it announces no IP prefixes and lacks any public corporate presence. The entity sits dormant—a pre-operational registry entry with latent routing capability but no active role in internet traffic.
- RIPE NCC AS Overview for AS211479: Confirms that N0EMIS-AS Ember Keske is the registered holder of autonomous system AS211479. Evidence basis: source-ed8525ff39ff
Timeline
- N0EMIS-AS Ember Keske public evidence observed
Any autonomous system holder can begin originating BGP announcements at any time, altering internet traffic paths and creating new routing dependencies. Although inactive today, N0EMIS-AS Ember Keske’s latent capability makes it a monitoring concern: activation could introduce route hijacking risks or unexpected traffic shifts.
At A Glance
- Name: N0EMIS-AS Ember Keske
- Type: Digital infrastructure institution
- Base: RIPE NCC region (Europe, Central Asia, Middle East) – subject location not independently confirmed
- Profile focus: Institution
What It Does
- public operating records
- official service pages
- documented relationships updates
Why It Matters
- Currently, the entity exerts zero influence on internet routing. If it were to originate prefixes or establish peering, its impact could become significant—redirecting traffic, creating new dependencies, and exposing networks to route leaks or hijacks. The gap between dormant registration and active threat is narrow.
- Operational criticality: Medium
- Time horizon: Next quarter
What To Watch
- official company sources
- public registries
- operator-published records
Track verified source updates, role changes, and current public evidence.
Currently, the entity exerts zero influence on internet routing. If it were to originate prefixes or establish peering, its impact could become significant—redirecting traffic, creating new dependencies, and exposing networks to route leaks or hijacks. The gap between dormant registration and active threat is narrow.
Longer-term relevance depends on verified operating, policy, and relationship changes.
Member Briefing
Deeper Profile Context
Login is required to unlock the full profile briefing and source notes.
Only for Strategy Circle
Strategic Circle Access
Open to all readers. Unlock profile briefings after joining and logging in.
Join Strategic CircleOnly for Leadership Alliance
Leadership Alliance Access
For owners and management of IP-holding companies. Login required to unlock.
Join Leadership AlliancePublic View
Currently, the entity exerts zero influence on internet routing. If it were to originate prefixes or establish peering, its impact could become significant—redirecting traffic, creating new dependencies, and exposing networks to route leaks or hijacks. The gap between dormant registration and active threat is narrow.
Watchpoints
- This entity is a low-activity, high-uncertainty infrastructure holder.
- Its dormancy means it currently introduces no routing risk, but the absence of ownership transparency makes it impossible to assess intent.
- Strategically, it fits a pattern of pre-positioned or abandoned ASN registrations that can be activated for benign or malicious purposes.
Caveats
- Public evidence is used only for source-backed claims.
- Private control or contract claims require separate public support.
FAQ
Why does BTW track N0EMIS-AS Ember Keske?
Any autonomous system holder can begin originating BGP announcements at any time, altering internet traffic paths and creating new routing dependencies. Although inactive today, N0EMIS-AS Ember Keske’s latent capability makes it a monitoring concern: activation could introduce route hijacking risks or unexpected traffic shifts.
What evidence supports the profile?
Confirms that N0EMIS-AS Ember Keske is the registered holder of autonomous system AS211479.
What should readers watch next?
This entity is a low-activity, high-uncertainty infrastructure holder.
