asn.dev

Autonomous system

AS34879 CCT-AS NGENIX

Hosting RIPE Content

IPv4 addresses 25.09K 32 prefixes
IPv6 prefixes 0 counted as prefixes, not addresses
Countries 1 mostly RU
Exchanges 6 recorded by PCH
Upstreams 25 1 downstream
Flagged prefixes 0 none

Summary

NGENIX

Russian Federation · AI-generated

cdn content business russia

The AS handle CCT-AS NGENIX is held by NGENIX (OOO "Sovremennye setevye tekhnologii").

What it's used for

  • The address space carries content delivery infrastructure, with reverse DNS entries consistently pointing to cdn.ngenix.net across the sampled prefixes.
  • The network announces 24,576 IPv4 addresses across 34 prefixes and maintains 56 observed neighbours, a ratio consistent with a content delivery network peering broadly to deliver traffic efficiently.

Notable

  • Registrants are predominantly "NGENIX Network Operations Center; OOO 'Sovremennye setevye tekhnologii'", aligning with the announcer, though one prefix (195.209.196.0/22) is registered to the Russian Scientific-Research Institute for Public Networks.
  • The address inventory is finely subdivided into 34 prefixes, including multiple /21 and /22 blocks, reflecting a segmented corporate estate rather than a single contiguous allocation.

This description is AI-generated, best-effort context — not authoritative, and provided without any guarantee of accuracy. Source, and how to suggest an edit.

Interconnection

Peering at a glance

Full topology · Graph

Internet exchanges

Recorded at 6 exchanges in 1 country, largest first.

ExchangeLocationTheir address
MSK-IX MoscowMoscow, Russia195.208.208.37
MSK-IX St. PetersburgSt. Petersburg, Russia194.226.102.48
MSK-IX NovosibirskNovosibirsk, Russia193.232.87.70
MSK-IX EkaterinburgEkaterinburg, Russia194.85.107.58
MSK-IX SamaraSamara, Russia193.232.135.52
MSK-IX VladivostokVladivostok, Russia193.232.136.37

Transit providers

25 upstream, 1 downstream and 26 adjacent networks observed; most-used upstreams first.

ASNetworkPaths seen
AS12389PJSC Rostelecom3,714
AS8359MTS PJSC711
AS3216PJSC "Vimpelcom"400
AS31133PJSC MegaFon187
AS20485Joint Stock Company TransTeleCom167
AS49800GNC-Alfa CJSC120
AS8402PJSC "Vimpelcom"88
AS21299Kar-Tel LLC65

Exchange presence is recorded rather than inferred: the directory collected by Packet Clearing House (https://www.pch.net/ixp/data) on 2026-10-13, licensed CC BY-NC-SA 3.0. Transit is inferred from observed BGP paths, never declared by either party.

Address space

Summary

Shape and geography

IPv4 32 prefixes · 25.09K addresses IPv6 0 prefixes

CountryNamePrefixes
RURussian Federation32

Registry

Allocation record

RIPE · via Atlas (registry + RDAP)
Registry
RIPE
Handle
AS34879
Registry name
CCT-AS
Registrant
CCT-MNT
Abuse contact
abuse@ngenix.net
Registered
2005-04-22
Last changed
2023-06-09
Allocation
allocated

Declared

PeeringDB profile

self-reported
Name
NGENIX
Network type
Content
Scope
Regional
Traffic ratio
Heavy Outbound
Peering policy
Open
IRR as-set
RIPE::AS-NGENIX
Present at
10 exchanges
Facilities
8 facilities
Website
https://ngenix.net/

PeeringDB records are maintained by the network operator and are not independently verified. Treat them as a statement of intent rather than of fact. For the observed and recorded view, see peering, which lists the exchanges Packet Clearing House has a port on file for.

Routing security

RPKI and IRR

Full detail
RPKI
100% valid · 100 valid, 0 with no ROA
ROAs
75 authorising AS34879
ASPA
no ASPA record
IRR
100% registered · 100 of 100 announcements
Route objects
137 naming AS34879

Reputation

Classification and threat

Hosting Datacenter or cloud provider. Addresses are servers, not people.

Spamhaus DROP

Not on ASN-DROP The network as a whole is not listed.

No DROP prefixes None of its announced space is on the DROP prefix list.

Spamhaus DROP ("Don't Route Or Peer") lists space and networks run by, or hijacked for, spam and cybercrime operations: 436 networks and 1,771 prefixes, as published 2026-10-13. A short, high-confidence list, so a match is worth taking seriously, and absence from it says little on its own.

FBI IC3

No IC3 indicators Nothing from the FBI IC3 feed.

IC3 threat data is alpha. Absence of an indicator is not evidence of good behaviour, only of absence from this one feed.

Elsewhere

Cross-check