asn.dev

Observed topology

AS43031 V-LAN-AS

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS43031: 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
AS8359MTS PJSCMobileIPv4 IPv643
AS20485Joint Stock Company TransTeleComUnclassifiedIPv437
AS6939Hurricane Electric LLCTransitIPv47
AS24482SG.GSHostingIPv4 IPv62
AS34927iFog GmbHHostingIPv41
AS37721Virtual Technologies & SolutionsResidentialIPv41

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS197044JSC ALIASUnclassifiedIPv4 IPv662
AS44162SE Chinkova Yuliya ViktorovnaUnclassifiedIPv432

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS20485Joint Stock Company TransTeleComUnclassifiedIPv487
AS8359MTS PJSCMobileIPv4 IPv669
AS197044JSC ALIASUnclassifiedIPv4 IPv662
AS44162SE Chinkova Yuliya ViktorovnaUnclassifiedIPv432
AS6939Hurricane Electric LLCTransitIPv418
AS24482SG.GSHostingIPv4 IPv65
AS34927iFog GmbHHostingIPv43
AS37721Virtual Technologies & SolutionsResidentialIPv43

Provenance

Where this comes from

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