asn.dev

Observed topology

AS39156 FTELECOM-AS Vorontsovskaya str., 35b, building 2

Unclassified ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS39156: 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
AS20764CJSC RASCOMUnclassifiedIPv482
AS28917Fiord Networks, UABUnclassifiedIPv471
AS1299Arelion Sweden ABTransitIPv418
AS8241Nets and Services JCSUnclassifiedIPv46
AS9049JSC "ER-Telecom Holding"UnclassifiedIPv42
AS24482SG.GSHostingIPv42
AS37721Virtual Technologies & SolutionsResidentialIPv42
AS50384iHome LLCUnclassifiedIPv42

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS35928BECKMAN COULTER, INC.UnclassifiedIPv4124
AS199287First Telecom LtdUnclassifiedIPv463
AS31183LLC "European Media Group"UnclassifiedIPv456
AS48781AVK-computer ltdResidentialIPv416
AS35129"LLC Tetra-Telematik"UnclassifiedIPv411

Adjacency

Adjacent networks

All 15

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

ASNetworkTypeFamiliesPaths seen
AS20764CJSC RASCOMUnclassifiedIPv4200
AS35928BECKMAN COULTER, INC.UnclassifiedIPv4124
AS28917Fiord Networks, UABUnclassifiedIPv4100
AS199287First Telecom LtdUnclassifiedIPv463
AS57174Nets and Services JCSUnclassifiedIPv461
AS31183LLC "European Media Group"UnclassifiedIPv456
AS1299Arelion Sweden ABTransitIPv449
AS48781AVK-computer ltdResidentialIPv422
AS50384iHome LLCUnclassifiedIPv420
AS8241Nets and Services JCSUnclassifiedIPv413

All 15 adjacent →

Provenance

Where this comes from

Derived from routing tables collected at 2026-10-21 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.14M 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.