asn.dev

Observed topology

AS34241 NCT-AS New Communication Technologies LLC

Hosting RIPE

Upstreams 2 carry this network
Downstreams 4 this network carries
Adjacent (IPv4) 6
Adjacent (IPv6) 4
Upstream graph Who carries AS34241, and who carries them, drawn as a map up to the transit-free core. 0 exchanges Where AS34241 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS34241: the AS immediately before it in a routing path. Ranked by how many paths showed the relationship, which reflects how widely it is used, not how much traffic crosses it.

ASNetworkTypeFamiliesPaths seen
AS20485Joint Stock Company TransTeleComUnclassifiedIPv4 IPv6784
AS3216PJSC "Vimpelcom"MobileIPv4 IPv6180

Transit

Downstream networks

inferred

Networks for which AS34241 was observed as the last hop before the origin, meaning it appears to provide them transit.

ASNetworkTypeFamiliesPaths seen
AS57418VIP-TELECOM LLCUnclassifiedIPv4 IPv6327
AS59404Korkino-Cable Television Networks LtdUnclassifiedIPv4157
AS43085CJSC Nauchno-technicheskiy centr lokalnih i geograficheskih sistemUnclassifiedIPv460
AS197044JSC ALIASUnclassifiedIPv4 IPv632

Adjacency

Adjacent networks

observed

Every AS seen directly next to AS34241 in a routing path, in either direction.

ASNetworkTypeFamiliesPaths seen
AS20485Joint Stock Company TransTeleComUnclassifiedIPv4 IPv61,270
AS57418VIP-TELECOM LLCUnclassifiedIPv4 IPv6327
AS3216PJSC "Vimpelcom"MobileIPv4 IPv6270
AS59404Korkino-Cable Television Networks LtdUnclassifiedIPv4157
AS43085CJSC Nauchno-technicheskiy centr lokalnih i geograficheskih sistemUnclassifiedIPv460
AS197044JSC ALIASUnclassifiedIPv4 IPv632

Provenance

Where this comes from

Derived from routing tables collected at 2026-11-13 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 74.40M route entries. These are observations from those vantage points, not a complete or authoritative view of the internet.

Inferred from path position, not from any declaration by either party. A network appearing here is carrying these routes; whether that is a paid transit arrangement, a backup, or something else is not something routing data can tell you. Adjacency is not the same as peering. Being next to each other in a path covers paid transit, settlement-free peering and customer connections alike, and routing data cannot distinguish them. Treat this as "these networks exchange routes", nothing more specific.

Cross-check against RIPEstat or BGP.tools, which observe from a different and larger set of vantage points.