Company Profiling / Network infrastructure operator

PE Novoshitskiy V.V.

The entity serves as the registrant and administrative contact for AS210720 in RIPE WHOIS. It maintains a single IPv4 route and imports connectivity from PJSC Rostelecom and Vimpelcom, providing no customer-facing services. Its operational role is confined to maintaining registry records and announcing a BGP route.

PE Novoshitskiy V.V.
Caption: A conceptual rendering of PE Novoshitskiy V.V.'s minimal network presence, emphasizing registry documentation and a single active route. · Source context: AI-generated editorial illustration. · Relevance reason: The image visualizes the entity's sole observable infrastructure—a single server representing the 45.8.209.0/24 prefix, the RIPE certificate symbolizing registry-bound identity, and the BGP feed showcasing the routing relationship with Rostelecom. · Image provenance: AI-generated editorial illustration.

Sources

Public references used for this article.

  • Internet registry recordpublic-source identity and registry context for internet-telecom-as PE Novoshitskiy V.V.. (source risk: low)
  • RIPE registry recordRIPE Database query surface for AS210720 is the official source for the aut-num record, including as-name, organisation reference, public contact references, status, and routing policy attributes. (source risk: low)
  • radar.cloudflare.comCloudflare Radar lists AS210720 as internet-telecom-as, AKA PE Novoshitskiy V.V., in the Russian Federation and exposes traffic and BGP monitoring panels for the AS. (source risk: low)
  • radar.cloudflare.comCloudflare Radar routing page shows AS210720 routing statistics, announced address-space views, prefix views, connectivity, RPKI ASPA, IRR AS-SET, and routing-anomaly panels for internet-telecom-as. (source risk: low)
  • ipinfo.ioIPinfo page for 45.8.209.0/24 identifies the prefix under AS210720 PE Novoshitskiy V.V., registry RIPE, ID INTERNET-TELECOM, includes RIPE WHOIS-derived inetnum and route details, and reports hosted-domain and pingability observations. (source risk: low)
  • ip2location.comIP2Location reports AS210720 PE Novoshitskiy V.V. with country Russian Federation, 256 IPv4 addresses, zero IPv6 addresses, prefix 45.8.209.0/24, upstream AS12389 PJSC Rostelecom, and no downstreams. (source risk: low)
  • Registry RDAP / WHOIS recordIPIP.NET mirrors RIPE-derived AS210720 data including as-name internet-telecom-as, organisation PE Novoshitskiy V.V., prefix 45.8.209.0/24, IPv4 and IPv6 route counts, and upstream context including AS3216 and AS12389. (source risk: low)
  • bigdatacloud.comBigDataCloud network lookup reports 45.8.209.0/24 as globally reachable, registered in RIPE, announced by AS210720 PE Novoshitskiy V.V., and receiving from AS3216 and AS12389. (source risk: low)
CategoryCompany

The entity serves as the registrant and administrative contact for AS210720 in RIPE WHOIS. It maintains a single IPv4 route and imports connectivity from PJSC Rostelecom and Vimpelcom, providing no customer-facing services. Its operational role is confined to maintaining registry records and announcing a BGP route.

RegionRussian Federation

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.

Signal FocusNetwork infrastructure operator

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.

Content TypeProfile

The entity serves as the registrant and administrative contact for AS210720 in RIPE WHOIS. It maintains a single IPv4 route and imports connectivity from PJSC Rostelecom and Vimpelcom, providing no customer-facing services. Its operational role is confined to maintaining registry records and announcing a BGP route.

Primary DomainInfrastructure

Anomalous BGP events—prefix hijacks, RPKI invalidity, or sudden withdrawals—could disrupt routing stability for networks dependent on its upstream carriers. The entity itself has no direct user impact, but its signals help detect policy or connectivity changes involving Rostelecom and Vimpelcom.

TopicNetwork infrastructure operator

PE Novoshitskiy V.V. is a registry‑only network entity in Russia, holding AS210720 and a single IPv4 prefix. Public evidence is limited to RIPE records and third‑party routing data, with no corporate website or biographical verification. The subject matters primarily as a signal for sub‑allocation changes and upstream dependency shifts. Key watchpoints include registry updates, prefix changes, and the emergence of any operator‑controlled online presence. The main uncertainty is whether the entity represents an active commercial operation or a dormant registration.

ImpactMedium

Anomalous BGP events—prefix hijacks, RPKI invalidity, or sudden withdrawals—could disrupt routing stability for networks dependent on its upstream carriers. The entity itself has no direct user impact, but its signals help detect policy or connectivity changes involving Rostelecom and Vimpelcom.

Confidence?Confidence Grade
0.90–1.00AHigh — direct sources
0.75–0.89A/BStrong
0.55–0.74B/CMedium
0.35–0.54C/DWeak–medium
0.10–0.34DWeak signal
0.00–0.09DInternal monitoring
Good confidence (70%)

Several public sources

PE Novoshitskiy V.V. is a registry‑only network entity in Russia, holding AS210720 and a single IPv4 prefix. Public evidence is limited to RIPE records and third‑party routing data, with no corporate website or biographical verification. The subject matters primarily as a signal for sub‑allocation changes and upstream dependency shifts. Key watchpoints include registry updates, prefix changes, and the emergence of any operator‑controlled online presence. The main uncertainty is whether the entity represents an active commercial operation or a dormant registration.

PE Novoshitskiy V.V.

PE Novoshitskiy V.V., operating as internet-telecom-as, is a Russian network entity holding AS210720 and the 45.8.209.0/24 IPv4 prefix. Its existence is documented only through RIPE NCC registry records and public BGP monitoring, with no commercial website or service presence, making it a low-visibility signal for analysts monitoring Russian sub-allocation dynamics.

Why It Matters

Anomalous BGP events—prefix hijacks, RPKI invalidity, or sudden withdrawals—could disrupt routing stability for networks dependent on its upstream carriers. The entity itself has no direct user impact, but its signals help detect policy or connectivity changes involving Rostelecom and Vimpelcom.

What Public Sources Show

PE Novoshitskiy V.V., operating under the AS-name internet-telecom-as, is a Russian network entity that exists solely within the RIPE NCC registry and public BGP data. It holds Autonomous System 210720 and announces a single IPv4 prefix, but provides no visible commercial services or corporate website. Its minimal footprint makes it a subtle but concrete signal for analysts tracking Russian internet sub-allocations.

The RIPE WHOIS records list the organisation as PE Novoshitskiy V.V., with both administrative and technical contacts attributed to V.V. Novoshitskiy. The aut-num object for AS210720 specifies imports from AS12389 (Rostelecom) and AS50113, and exports to those networks. This configuration indicates that the entity depends on large Russian transit providers for global connectivity.

The only observed IPv4 route originated by AS210720 is 45.8.209.0/24, a /24 subnet created in September 2021. No IPv6 routes have ever been announced. Monitoring platforms such as Cloudflare Radar and IPinfo confirm that the prefix is reachable, and routing data shows that upstream traffic flows primarily through PJSC Rostelecom (AS12389) and Vimpelcom (AS3216).

Public evidence is limited to registry records and third-party measurement sites. No company website, PeeringDB page, or Russian business registry listing has been found. Observations of hosted domains or ping responses on the prefix are measurement artifacts; they do not confirm that PE Novoshitskiy V.V. operates active customer-facing services.

The operating surface of the entity is confined to the RIPE registry objects and BGP route announcements. Changes to the aut-num or organisation records directly alter its network identity, while its routing posture influences how the 45.8.209.0/24 prefix is seen globally. These controls form the only verifiable authority surface for PE Novoshitskiy V.V.

For infrastructure analysts, this entity matters because its behavior can indicate shifts in Russian sub-allocation practices or carrier relationships. A sudden withdrawal of the prefix, a new upstream, or a registry update could serve as an early-watch signal for broader changes involving Rostelecom or Vimpelcom. However, the entity itself has no direct service impact.

Watchpoints include any modifications to the RIPE records, such as contact changes or policy updates. The appearance of new ASNs, prefixes, or a commercial website would significantly alter the assessment. Routing anomalies like unexpected BGP withdrawals or RPKI invalidity would also demand attention.

The primary uncertainty is whether PE Novoshitskiy V.V. represents an active network operator, a dormant shelf holding, or a pre-operational registration. The individual V.V. Novoshitskiy is known only from the RIPE contact fields, with no independent biographical verification. Until operator-controlled sources emerge, the entity’s true purpose and decision-making authority remain unconfirmed.

Operating Surface

The entity serves as the registrant and administrative contact for AS210720 in RIPE WHOIS. It maintains a single IPv4 route and imports connectivity from PJSC Rostelecom and Vimpelcom, providing no customer-facing services. Its operational role is confined to maintaining registry records and announcing a BGP route.

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.

Watchpoints

The entity acts as an infrastructure canary: because it depends on major Russian carriers, changes in its posture can precede or reflect strategic shifts by Rostelecom or Vimpelcom without requiring monitoring of those larger entities directly.

Track RIPE object modifications, BGP announcement changes (additions, withdrawals, RPKI status), upstream provider additions or removals, and any appearance of a commercial website or service.

Lack of corporate registration documents, financial records, and verified identity of V.V. Novoshitskiy. Without these, the entity's exact purpose and decision-making structure remain opaque.

Sources

  • Internet registry record - public-source identity and registry context for internet-telecom-as PE Novoshitskiy V.V..
  • RIPE registry record - RIPE Database query surface for AS210720 is the official source for the aut-num record, including as-name, organisation reference, public contact references, status, and routing policy attributes.
  • radar.cloudflare.com - Cloudflare Radar lists AS210720 as internet-telecom-as, AKA PE Novoshitskiy V.V., in the Russian Federation and exposes traffic and BGP monitoring panels for the AS.
  • radar.cloudflare.com - Cloudflare Radar routing page shows AS210720 routing statistics, announced address-space views, prefix views, connectivity, RPKI ASPA, IRR AS-SET, and routing-anomaly panels for internet-telecom-as.
  • ipinfo.io - IPinfo page for 45.8.209.0/24 identifies the prefix under AS210720 PE Novoshitskiy V.V., registry RIPE, ID INTERNET-TELECOM, includes RIPE WHOIS-derived inetnum and route details, and reports hosted-domain and pingability observations.
  • ip2location.com - IP2Location reports AS210720 PE Novoshitskiy V.V. with country Russian Federation, 256 IPv4 addresses, zero IPv6 addresses, prefix 45.8.209.0/24, upstream AS12389 PJSC Rostelecom, and no downstreams.
  • Registry RDAP / WHOIS record - IPIP.NET mirrors RIPE-derived AS210720 data including as-name internet-telecom-as, organisation PE Novoshitskiy V.V., prefix 45.8.209.0/24, IPv4 and IPv6 route counts, and upstream context including AS3216 and AS12389.
  • bigdatacloud.com - BigDataCloud network lookup reports 45.8.209.0/24 as globally reachable, registered in RIPE, announced by AS210720 PE Novoshitskiy V.V., and receiving from AS3216 and AS12389.

Domain of operation

PE Novoshitskiy V.V., operating as internet-telecom-as, is a Russian network entity holding AS210720 and the 45.8.209.0/24 IPv4 prefix. Its existence is documented only through RIPE NCC registry records and public BGP monitoring, with no commercial website or service presence, making it a low-visibility signal for analysts monitoring Russian sub-allocation dynamics.

  • Internet registry record: public-source identity and registry context for internet-telecom-as PE Novoshitskiy V.V.. Evidence basis: source-ab829eea225a

Timeline

  1. PE Novoshitskiy V.V. public evidence observed

    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.

At A Glance

  • Name: PE Novoshitskiy V.V.
  • Type: Network infrastructure operator
  • Base: Russian Federation
  • Profile focus: Company

What It Does

  • public operating records
  • official service pages
  • source-backed relationship updates

Why It Matters

  • Anomalous BGP events—prefix hijacks, RPKI invalidity, or sudden withdrawals—could disrupt routing stability for networks dependent on its upstream carriers. The entity itself has no direct user impact, but its signals help detect policy or connectivity changes involving Rostelecom and Vimpelcom.
  • Operational criticality: Medium
  • Time horizon: Next quarter

What To Watch

  • official company sources
  • public registries
  • operator-published records
NowMedium priority

Track verified source updates, role changes, and current public evidence.

QuarterMedium policy sensitivity

Anomalous BGP events—prefix hijacks, RPKI invalidity, or sudden withdrawals—could disrupt routing stability for networks dependent on its upstream carriers. The entity itself has no direct user impact, but its signals help detect policy or connectivity changes involving Rostelecom and Vimpelcom.

YearNext quarter outlook

Longer-term relevance depends on verified operating, policy, and relationship changes.

Member Briefing

Deeper Profile Context

Login is required to unlock the full profile briefing and source notes.

Only for Strategy Circle

Strategic Circle Access

Open to all readers. Unlock profile briefings after joining and logging in.

Join Strategic Circle

Only for Leadership Alliance

Leadership Alliance Access

For owners and management of IP-holding companies. Login required to unlock.

Join Leadership Alliance

Public View

Anomalous BGP events—prefix hijacks, RPKI invalidity, or sudden withdrawals—could disrupt routing stability for networks dependent on its upstream carriers. The entity itself has no direct user impact, but its signals help detect policy or connectivity changes involving Rostelecom and Vimpelcom.

Watchpoints

  • The entity acts as an infrastructure canary: because it depends on major Russian carriers, changes in its posture can precede or reflect strategic shifts by Rostelecom or Vimpelcom without requiring monitoring of those larger entities directly.
  • Track RIPE object modifications, BGP announcement changes (additions, withdrawals, RPKI status), upstream provider additions or removals, and any appearance of a commercial website or service.
  • Lack of corporate registration documents, financial records, and verified identity of V.V.

Caveats

  • Public evidence is used only for source-backed claims.
  • Private control or contract claims require separate public support.

FAQ

Why does BTW track PE Novoshitskiy V.V.?

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.

What evidence supports the profile?

public-source identity and registry context for internet-telecom-as PE Novoshitskiy V.V..

What should readers watch next?

The entity acts as an infrastructure canary: because it depends on major Russian carriers, changes in its posture can precede or reflect strategic shifts by Rostelecom or Vimpelcom without requiring monitoring of those larger entities directly.

← BackAll Companies