Reference visual: company and capital context snapshot.

Briefing entreprise / Individual registry-holder label

By Tuna Tu ÉDITEUR MARCHÉ

Technical Director

The profile matters because it identifies the actual operating entity—ONOFF TELECOM SAS—a licensed telecom operator offering cloud‑based virtual numbers. Mistaking the role for a person misdirects attention from the company’s control over number assignment, service stability, and API reliability, which are the real dependencies for users and businesses.

AuteurTuna Tu

Editorial owner accountable for this profile route.

Temps de lecture2 min

Estimated reading time at standard editorial pace.

Publié leMay 26, 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.

RégionFrance

Primary geography where current signals are most visible.

Signal FocusInstitution Type

Principal area tracked in this intelligence profile.

Type de contenuProfile

Structured profile used for cross-category comparison.

Domaine principalInfrastructure

Primary editorial domain framing the analysis.

SujetPublic network contact

Controlled taxonomy label used for this profile route.

HorizonQuarter (30-120d)

Most likely window for material strategy effects.

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

Confiance0.95

Anchored to multiple primary-source references and direct disclosures.

Dossier de preuves

Sources primaires utilisées pour la classification et l'évaluation d'impact.

Contexte

The Technical Director profile resolves to the RIPE role contact TD7104-RIPE for ONOFF TELECOM SAS. No person is verified behind the handle. The company provides cloud‑based virtual numbers via the Onoff app, operating in multiple European countries and holding RIPE NCC membership. Its control surface includes number assignment, account management, API access, and enforcement of terms. Key gaps are the absence of a named individual, missing revenue data, and a SIREN discrepancy in French numbering decisions. Watch for registry changes and active BGP announcements.

Core Entity Brief

Entity	Technical Director
Public role	The profile matters because it identifies the actual operating entity—ONOFF TELECOM SAS—a licensed telecom operator offering cloud‑based virtual numbers. Mistaking the role for a person misdirects attention from the company’s control over number assignment, service stability, and API reliability, which are the real dependencies for users and businesses.
Region	France
Category	Individual registry-holder label
Primary domain	Infrastructure
Signal focus	Institution Type
Time horizon	Quarter (30-120d)
Impact	Medium
Confidence	0.95
Evidence coverage	12 public source references
Related coverage	Profile anchor article
Website	Public evidence pending
Last update	Jun 02, 2026

Technical Director is presented as a Individual registry-holder label in the BTW company and institution directory. The profile matters because it identifies the actual operating entity—ONOFF TELECOM SAS—a licensed telecom operator offering cloud‑based virtual numbers. Mistaking the role for a person misdirects attention from the company’s control over number assignment, service stability, and API reliability, which are the real dependencies for users and businesses.

The current public read is bounded by primary domain: Infrastructure; signal focus: Institution Type; time horizon: Quarter (30-120d); impact band: Medium. These fields give readers a stable baseline for comparing the profile with other institutions, operators, and market actors.

The evidence basis currently includes 12 public evidence references and the linked public profile. Claims should stay limited to role, context, operating surface, dependencies, and watchpoints that are visible in reviewed public material.

Domain of operation

Public role: Technical Director is framed by the profile matters because it identifies the actual operating entity—onoff telecom sas—a licensed telecom operator offering cloud‑based virtual numbers. mistaking the role for a person misdirects attention from the company’s control over number assignment, service stability, and api reliability, which are the real dependencies for users and businesses. and public infrastructure context. Evidence basis: Registry RDAP / WHOIS record; Registry RDAP / WHOIS record
Operating surface: Public network contact and France provide the public context for this institution profile. Evidence basis: Registry RDAP / WHOIS record; Registry RDAP / WHOIS record

Timeline

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

Signal Map

Why tracked: The profile matters because it identifies the actual operating entity—ONOFF TELECOM SAS—a licensed telecom operator offering cloud‑based virtual numbers. Mistaking the role for a person misdirects attention from the company’s control over number assignment, service stability, and API reliability, which are the real dependencies for users and businesses.
Object role: Technical Director serves as the administrative and technical contact role for AS211948 within the RIPE registry, associated with ONOFF TELECOM SAS. It has no verified personal identity, employment history, or independent authority outside that registry function.
Impact note: Users and businesses depend on ONOFF’s ability to assign numbers, keep calls reachable, suspend accounts, and expose business APIs. Disruption or misuse of these controls can interrupt communications and business operations. Treating the registry role as a person instead of a company contact obscures where accountability sits.
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 Technical Director 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 Technical Director included?

Technical Director 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

Retour au desk entreprises Retour à l’accueil