asn.dev

Observed topology

AS43309 GIPERNET-AS GIPERNET-AS

Residential ARIN Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS43309: 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
AS49183"Galichina Telekommunication" LTDResidentialIPv4 IPv6188
AS21497PrJSC "VF UKRAINE"MobileIPv4 IPv6145
AS6939Hurricane Electric LLCTransitIPv4 IPv659
AS50263A-Systems Sp. z o.o.UnclassifiedIPv4 IPv656
AS24482SG.GSHostingIPv4 IPv69
AS8218Zayo Infrastructure France SAUnclassifiedIPv62
AS34927iFog GmbHHostingIPv42

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS44340GIPERNET LLCUnclassifiedIPv4198
AS209907FOP Saiv Igor StepanovichUnclassifiedIPv4130

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS49183"Galichina Telekommunication" LTDResidentialIPv4 IPv6446
AS44340GIPERNET LLCUnclassifiedIPv4198
AS21497PrJSC "VF UKRAINE"MobileIPv4 IPv6177
AS209907FOP Saiv Igor StepanovichUnclassifiedIPv4130
AS50263A-Systems Sp. z o.o.UnclassifiedIPv4 IPv687
AS6939Hurricane Electric LLCTransitIPv4 IPv659
AS24482SG.GSHostingIPv4 IPv613
AS50629LWLcom GmbHUnclassifiedIPv43
AS8218Zayo Infrastructure France SAUnclassifiedIPv62
AS34927iFog GmbHHostingIPv42

Provenance

Where this comes from

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