Core Entity Brief
| Entity | PE Novoshitskiy V.V. |
|---|---|
| Public role | PE Novoshitskiy V.V. is tracked because shifts in its registry records, routing posture, or upstream dependencies act as early indicators of changes in Russian sub-allocation practices and carrier relationships. Its reliance on major Russian transit providers creates a dependency chain useful for monitoring regional infrastructure shifts. |
| Region | Russian Federation |
| Category | Network infrastructure operator |
| Primary domain | Infrastructure |
| Signal focus | Company Type |
| Time horizon | Quarter (30-120d) |
| Impact | Medium |
| Confidence | 0.70 |
| Evidence coverage | 8 public source references |
| Related coverage | Profile anchor article |
| Website | Public evidence pending |
| Last update | Jun 02, 2026 |
PE Novoshitskiy V.V., operating as internet‑telecom‑as, is a Russian registry‑only network entity holding AS210720 and the 45.8.209.0/24 IPv4 prefix, with no independent commercial presence.
What It Does
- Registry‑presence role: PE Novoshitskiy V.V. holds AS210720 and a single IPv4 prefix in the RIPE NCC service region. It provides no visible online services, and its revenue model or customer base is not publicly documented.
- Dependency signal: The entity’s routing presence serves as an indicator for analysts tracking Russian sub‑allocations and carrier relationships, though it has no direct commercial impact on end users.
Operating Snapshot
- RIPE registration: Listed in RIPE WHOIS as the organisation ‘PE Novoshitskiy V.V.’ with AS210720 assigned and the as‑name ‘internet‑telecom‑as’. The administrative and technical contact is V.V. Novoshitskiy.
- Network footprint: Originates the 45.8.209.0/24 IPv4 route; no IPv6 route is announced. Upstream connectivity is through PJSC Rostelecom (AS12389) and Vimpelcom (AS3216), with an additional policy reference to AS50113.
- External visibility: No corporate website, PeeringDB page, or business registry listing has been identified. Information is derived entirely from RIPE records and public BGP monitoring platforms.
Control Surface
- RIPE registry objects: The aut‑num and organisation objects for AS210720, as well as the route object for 45.8.209.0/24, constitute the primary point of authority. Changes to these records directly affect the entity’s network identity.
- BGP routing: The entity controls BGP announcements for its prefix, influencing how the prefix is routed globally. Its routing posture is visible through public route collectors and monitoring services.
Watchpoints
- Registry record freshness: Stale or suddenly changed WHOIS records could indicate inactivity or reassignment. Regular registry audits help confirm the entity’s ongoing role.
- Footprint expansion: The appearance of new ASNs, prefixes, a PeeringDB entry, or a corporate website would signal increased operational scale and require reassessment of the entity’s significance.
- Routing anomalies: Unexpected BGP withdrawals, route leaks, or RPKI validation failures could indicate misconfiguration, network compromise, or a deliberate change in operational status.

