Reference visual: company and capital context snapshot.

Company Briefing / Individual registry-holder label

By Hazel Long MARKET EDITOR

Mohamad Chehimi

Changes to the registry record for AS210318 or the entity handle MC45897-RIPE could shift the contact point for routing issues, abuse reports, or resource management. Tracking Chehimi’s continued presence in public registry data helps analysts understand who operators and authorities might reach for coordination, even if the AS is not currently routing.

AuthorHazel Long

Editorial owner accountable for this profile route.

Reading Time3 min

Estimated reading time at standard editorial pace.

PublishedJun 02, 2026

Date this profile last entered editorial circulation.

Last updateJun 02, 2026

Date this profile last entered editorial circulation.

CategoryIndividual registry-holder label

Controlled classification used for cross-profile comparison.

RegionGlobal

Primary geography where current signals are most visible.

Signal FocusInstitution Type

Principal area tracked in this intelligence profile.

Content TypeProfile

Structured profile used for cross-category comparison.

Primary DomainInfrastructure

Primary editorial domain framing the analysis.

TopicInternet Infrastructure Contact

Controlled taxonomy label used for this profile route.

Time HorizonQuarter (30-120d)

Most likely window for material strategy effects.

ImpactMediumThe signal alters planning assumptions but usually requires secondary implementation before full effect.

Confidence0.95

Anchored to multiple primary-source references and direct disclosures.

Evidence Pack

Primary-source references used for classification and impact scoring.

Context

Mohamad Chehimi is a person listed in RIPE registry records as the administrative and technical contact for AS210318. The evidence is limited to official RDAP and RIPE Database records, confirming the entity handle MC45897-RIPE but providing no employer, biography, or prefix data. The profile establishes a baseline for monitoring this contact point; changes in the registry or any routing activity from AS210318 would alter the operational significance. Key uncertainties include record staleness and whether Chehimi is a current, active contact or a historical role account.

Core Entity Brief

Entity	Mohamad Chehimi
Public role	Changes to the registry record for AS210318 or the entity handle MC45897-RIPE could shift the contact point for routing issues, abuse reports, or resource management. Tracking Chehimi’s continued presence in public registry data helps analysts understand who operators and authorities might reach for coordination, even if the AS is not currently routing.
Region	Global
Category	Individual registry-holder label
Primary domain	Infrastructure
Signal focus	Institution Type
Time horizon	Quarter (30-120d)
Impact	Medium
Confidence	0.95
Evidence coverage	3 public source references
Related coverage	Profile anchor article
Website	Public evidence pending
Last update	Jun 02, 2026

Mohamad Chehimi appears in external numbering or routing evidence for AS210318; the public assessment is bounded by that source-backed context.

What It Does

Visible operating role: The public evidence shows Mohamad Chehimi listed with admin and tech roles for ASN 210318 in the RIPE registry, indicating a network-operations contact function. No other operating context is verified by the provided evidence.
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: Mohamad Chehimi is a person listed in public RIPE registry records as the holder of entity handle MC45897-RIPE and appears as an administrative and technical contact for autonomous system 210318.
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 only verified public control surface is the registry contact listing: Mohamad Chehimi is named in the RIPE database object MC45897-RIPE and referenced in the aut-num record for AS210318. The available evidence does not confirm ownership, decision-making authority, or control over the autonomous system or any prefixes.
Evidence changes: New announcements, withdrawals, or reassigned prefixes attached to AS210318 can change how much operational significance readers should assign to Mohamad Chehimi.

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 Mohamad Chehimi's infrastructure relevance.

Domain of operation

Public role: Mohamad Chehimi is framed by changes to the registry record for as210318 or the entity handle mc45897-ripe could shift the contact point for routing issues, abuse reports, or resource management. tracking chehimi’s continued presence in public registry data helps analysts understand who operators and authorities might reach for coordination, even if the as is not currently routing. and public infrastructure context. Evidence basis: Registry RDAP / WHOIS record; RIPE registry record
Operating surface: Internet Infrastructure Contact and Global provide the public context for this institution profile. Evidence basis: Registry RDAP / WHOIS record; RIPE registry record

Timeline

02 Jun 2026
Mohamad Chehimi public profile updated
Public coverage records Mohamad Chehimi as a subject for role, operating context, and evidence review.

Signal Map

Why tracked: Changes to the registry record for AS210318 or the entity handle MC45897-RIPE could shift the contact point for routing issues, abuse reports, or resource management. Tracking Chehimi’s continued presence in public registry data helps analysts understand who operators and authorities might reach for coordination, even if the AS is not currently routing.
Object role: Publicly accessible RDAP data for aut-num 210318 lists Mohamad Chehimi through entity handle MC45897-RIPE with admin and tech contact roles, indicating a network-operations contact context within RIPE-managed Internet number resource records. No other operating context is verified by the provided evidence.
Impact note: If AS210318 becomes active, Chehimi’s contact role would influence how quickly and with whom external parties coordinate during outages, hijacks, or disputes. Currently, the lack of BGP activity limits the immediate operational impact to a regulatory trail, but any change would raise his significance.
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 Mohamad Chehimi 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 Mohamad Chehimi included?

Mohamad Chehimi 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.

Actions

Back to Companies Desk Back to Front Page