asn.dev

Observed topology

AS31214 TIS-DIALOG-AS TIS Dialog LLC

Residential APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS31214: 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
AS57304JSC "RetnNet"UnclassifiedIPv4 IPv6663
AS9002RETN LimitedUnclassifiedIPv4 IPv6144
AS35598INETCOM CARRIER LLCUnclassifiedIPv4 IPv651
AS24482SG.GSHostingIPv4 IPv616
AS34927iFog GmbHHostingIPv415
AS37721Virtual Technologies & SolutionsResidentialIPv415
AS49673Truenetwork LLCUnclassifiedIPv415
AS50384iHome LLCUnclassifiedIPv411
AS1299Arelion Sweden ABTransitIPv4 IPv65
AS62255BiMajLink d.o.o.UnclassifiedIPv64

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS196786IP Yashutkin Andrei VladimirovichUnclassifiedIPv464
AS41975OOO RIVC "Simplex"UnclassifiedIPv48

Adjacency

Adjacent networks

All 13

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

ASNetworkTypeFamiliesPaths seen
AS57304JSC "RetnNet"UnclassifiedIPv4 IPv6663
AS9002RETN LimitedUnclassifiedIPv4 IPv6165
AS196786IP Yashutkin Andrei VladimirovichUnclassifiedIPv464
AS35598INETCOM CARRIER LLCUnclassifiedIPv4 IPv657
AS12389PJSC RostelecomResidentialIPv429
AS24482SG.GSHostingIPv4 IPv617
AS37721Virtual Technologies & SolutionsResidentialIPv417
AS49673Truenetwork LLCUnclassifiedIPv416
AS34927iFog GmbHHostingIPv415
AS62255BiMajLink d.o.o.UnclassifiedIPv4 IPv613

All 13 adjacent →

Provenance

Where this comes from

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