asn.dev

Observed topology

AS39156 FTELECOM-AS First Telecom Ltd

Unclassified ARIN

Upstreams 7 carry this network
Downstreams 5 this network carries
Adjacent (IPv4) 13
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 RASCOMUnclassifiedIPv486
AS28917Fiord Networks, UABUnclassifiedIPv472
AS1299Arelion Sweden ABTransitIPv418
AS8241Nets and Services JCSUnclassifiedIPv46
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.UnclassifiedIPv4126
AS199287First Telecom LtdUnclassifiedIPv464
AS31183LLC "European Media Group"UnclassifiedIPv458
AS48781AVK-computer ltdResidentialIPv452
AS35129"LLC Tetra-Telematik"UnclassifiedIPv48

Adjacency

Adjacent networks

All 13

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

ASNetworkTypeFamiliesPaths seen
AS20764CJSC RASCOMUnclassifiedIPv4201
AS35928BECKMAN COULTER, INC.UnclassifiedIPv4126
AS28917Fiord Networks, UABUnclassifiedIPv4103
AS57174Nets and Services JCSUnclassifiedIPv4102
AS48781AVK-computer ltdResidentialIPv465
AS199287First Telecom LtdUnclassifiedIPv464
AS31183LLC "European Media Group"UnclassifiedIPv458
AS1299Arelion Sweden ABTransitIPv453
AS50384iHome LLCUnclassifiedIPv424
AS8241Nets and Services JCSUnclassifiedIPv414

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.