BTW tracks this identity because even a lightly attested ASN can produce detectable routing events. A withdrawal, re-announcement, RPKI validation change, or transfer of its sole prefix would be observable by networks that filter or propagate the route. Monitoring AS216150 provides early warning of address-space churn in Kazakhstan and may reveal the emergence of a genuine operator behind the registry entry.
作者Harriet Li
Editorial owner accountable for this profile route.
阅读时间3 min
Estimated reading time at standard editorial pace.
发布时间Jun 02, 2026
Date this profile last entered editorial circulation.
Last updateJun 02, 2026
Date this profile last entered editorial circulation.
CategoryNetwork-related institution
Controlled classification used for cross-profile comparison.
区域KZ
Primary geography where current signals are most visible.
Signal FocusInstitution Type
Principal area tracked in this intelligence profile.
内容类型Profile
Structured profile used for cross-category comparison.
主领域Infrastructure
Primary editorial domain framing the analysis.
主题Network-related institution
Controlled taxonomy label used for this profile route.
时间跨度Quarter (30-120d)
Most likely window for material strategy effects.
影响MediumThe signal alters planning assumptions but usually requires secondary implementation before full effect.
置信度0.95
Anchored to multiple primary-source references and direct disclosures.
KZ-NURMUKANZHAN-20260508 is a Kazakhstan‑based routing identity (AS216150) appearing in public BGP and registry records with a single /24 prefix. The evidence does not verify a company, institution, or individual operator beyond the routing context; the name Nurmukan Zhantorin remains unconfirmed beyond directory labels. Its relevance is as a low‑impact routing watchpoint: changes in prefix advertisement, RPKI validation, or registry records would alter the assessment. Data gaps include the missing RIPE AUT‑NUM detail, no official operator page, and unresolved route count discrepancies. Until more evidence emerges, treat as a monitoring candidate, not a verified institutional actor.
Core Entity Brief
Core Entity Brief
Entity
KZ-NURMUKANZHAN-20260508
Public role
BTW tracks this identity because even a lightly attested ASN can produce detectable routing events. A withdrawal, re-announcement, RPKI validation change, or transfer of its sole prefix would be observable by networks that filter or propagate the route. Monitoring AS216150 provides early warning of address-space churn in Kazakhstan and may reveal the emergence of a genuine operator behind the registry entry.
Region
KZ
Category
Network-related institution
Primary domain
Infrastructure
Signal focus
Institution Type
Time horizon
Quarter (30-120d)
Impact
Medium
Confidence
0.95
Evidence coverage
6 public source references
Related coverage
Profile anchor article
Website
Public evidence pending
Last update
Jun 02, 2026
KZ-NURMUKANZHAN-20260508 appears in external numbering or routing evidence for AS48529, AS212743, AS216150; the public assessment is bounded by that source-backed context.
What It Does
Visible operating role: Public internet-routing context: AS216150 appears in Kazakhstan-oriented ASN/routing listings and in a current CIDR Report route-table change section. The evidence supports monitoring as a small route-origin/registry identity, not as a verified company or institution.
Revenue and customer gap: No supplied evidence establishes a revenue model, customer base, or contract position; those claims need official, financial, or service-source support before publication.
Operating Snapshot
Identity baseline: KZ-NURMUKANZHAN-20260508 (AS216150), also associated with the name Nurmukan Zhantorin, is a public routing identity in Kazakhstan known through BGP and registry observations.
Routing context: No active prefix sample is present in the current evidence set, so the public assessment is limited to ASN identity until routing evidence changes.
Control Surface
Numbering records: The verified control surface is limited to AS216150 registry/routing identity and associated route-origin observations. Public sources show a small BGP footprint and one observed IPv4 /24 context, but do not verify a corporate operator, customers, service platform, or wider institutional authority.
Evidence changes: New announcements, withdrawals, or reassigned prefixes attached to AS48529, AS212743, AS216150 can change how much operational significance readers should assign to KZ-NURMUKANZHAN-20260508.
Watchpoints
Record freshness: Stale, conflicting, or changed public records are the main uncertainty when translating source evidence into an operating profile.
Footprint change: New ASN, prefix, official website, PeeringDB, or registry evidence would raise or lower KZ-NURMUKANZHAN-20260508's infrastructure relevance.
Domain of operation
BTW tracks this identity because even a lightly attested ASN can produce detectable routing events. A withdrawal, re-announcement, RPKI validation change, or transfer of its sole prefix would be observable by networks that filter or propagate the route. Monitoring AS216150 provides early warning of address-space churn in Kazakhstan and may reveal the emergence of a genuine operator behind the registry entry.
Public role: KZ-NURMUKANZHAN-20260508 is framed by btw tracks this identity because even a lightly attested asn can produce detectable routing events. a withdrawal, re-announcement, rpki validation change, or transfer of its sole prefix would be observable by networks that filter or propagate the route. monitoring as216150 provides early warning of address-space churn in kazakhstan and may reveal the emergence of a genuine operator behind the registry entry. and public infrastructure context. Evidence basis: Registry RDAP / WHOIS record; RIPE registry record
Operating surface: Network-related institution and KZ provide the public context for this institution profile. Evidence basis: Registry RDAP / WHOIS record; RIPE registry record
Timeline
KZ-NURMUKANZHAN-20260508 public profile updated
Public coverage records KZ-NURMUKANZHAN-20260508 as a subject for role, operating context, and evidence review.
Signal Map
Signal Map
Why tracked: BTW tracks this identity because even a lightly attested ASN can produce detectable routing events. A withdrawal, re-announcement, RPKI validation change, or transfer of its sole prefix would be observable by networks that filter or propagate the route. Monitoring AS216150 provides early warning of address-space churn in Kazakhstan and may reveal the emergence of a genuine operator behind the registry entry.
Object role: The subject functions as a registry identity and BGP route origin for AS216150 in Kazakhstan. Public sources show it originates the prefix 217.60.24.0/24 and appears in third-party routing databases. There is no confirmed company, institution, or internet service provider behind the label; the available evidence supports only monitoring of its network-numbering context and routing behaviour.
Impact note: The impact mechanism is narrow: if AS216150 ceases to originate or loses RPKI validation for 217.60.24.0/24, downstream networks that accept the route may experience minor reachability disruptions for that /24 block. A new prefix announcement or a change in the ASN’s registry status would alter the address attribution. Because the footprint is tiny, broad internet impact is unlikely, but the signal is meaningful for routing-intelligence monitoring.
Control surface: public operating records, official service pages, source-backed relationship updates
Key dependencies: official company sources, public registries, operator-published records
Public View
The public read of KZ-NURMUKANZHAN-20260508 is limited to visible role, operating context, and relationship evidence.
Watchpoints
New public role, affiliation, product, policy, or market disclosures.
Verified relationship changes involving named organizations or people.
Caveats
Private or unverified claims are excluded from this public view.
FAQ
Why is KZ-NURMUKANZHAN-20260508 included?
KZ-NURMUKANZHAN-20260508 has public evidence that makes the institution relevant to BTW's coverage of digital infrastructure, governance, or markets.
What is public about this profile?
The public layer covers visible role, operating context, linked organizations, and evidence-backed watchpoints.
What should readers watch next?
Readers should watch for source-backed role changes, new partnerships, regulatory exposure, operating expansion, or evidence that changes the public assessment.
