N0EMIS-AS Ember Keske

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 reference point: 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.

N0EMIS-AS Ember Keske

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.

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.

What Public Sources Show

N0EMIS-AS Ember Keske is the registered holder of autonomous system AS211479, according to RIPE NCC data. It announces no IP prefixes into the global routing table, meaning it does not participate in internet routing today. No corporate website, PeeringDB entry, or public contact information has been found, leaving it a ghostly registry entry.

Any AS holder can begin originating BGP announcements at any moment. That move would instantly turn this dormant entity into an active entity capable of redirecting traffic, forming peering relationships, or—if misconfigured—launching route hijacks. For now, the risk is hypothetical, but the potential is real.

Evidence is limited to two RIPE NCC data endpoints. One confirms the AS holder name for AS211479; the other shows zero announced prefixes. No additional public footprint—no website, no PeeringDB profile, no business registration—supplements the registry record.

The only observable control surface is the RIPE NCC LIR portal. Whoever holds the credentials can modify the AS211479 record, change contacts, or request IP resources. If the entity later configures routers and announces prefixes, BGP policy becomes a second, more dangerous control point.

Changes to the AS211479 registry record—new contacts, an address, a renamed organisation—would be a first sign of activation. The start of BGP prefix origination would shift the entity from dormant to operational, creating routing dependencies. The appearance of a named individual, a PeeringDB entry, or a corporate website would similarly transform the profile.

Nothing is known about ownership, geographic location, business purpose, or intent. The entity could be a pre-operational holder for future use, an abandoned registration, or a deliberate obscurity. Without further public signals, its purpose remains opaque, and its risk profile unchanged.

Operating Surface

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.

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. Monitoring is a cost-effective early-warning measure.

Key observables: (1) any modification to the AS211479 registry record—especially contact additions or address details; (2) BGP origin events for any prefix under AS211479; (3) appearance of an individual as admin-c or tech-c in registry data; (4) creation of a PeeringDB entry or a public website claiming to represent N0EMIS-AS Ember Keske.

Critical gaps: complete lack of corporate registration (location, jurisdiction), no named responsible party, no stated business purpose, and no routing history. Filling any of these gaps would transform the assessment from dormant entry to operational entity with a measurable risk profile.

Sources

• RIPE NCC AS Overview for AS211479 - Confirms that N0EMIS-AS Ember Keske is the registered holder of autonomous system AS211479.
• RIPEstat Announced Prefixes for AS211479 - Shows that AS211479 has zero publicly announced IP prefixes, indicating no active routing participation.