asn.dev

Observed topology

AS29468 INFRACOM

Residential APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS29468: 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
AS8473Bahnhof ABResidentialIPv4 IPv61,087
AS1257Tele2 Sverige ABMobileIPv4 IPv6511
AS6939Hurricane Electric LLCTransitIPv4242
AS42303LM Layer and Mesh ABUnclassifiedIPv46

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS49515DND Nordic ABUnclassifiedIPv4351
AS25223Infracom Managed Services ABUnclassifiedIPv4 IPv6150
AS15912Infracom Connect ABUnclassifiedIPv4116
AS197603Transtema Network Services ABUnclassifiedIPv4114
AS43591AddSecure ABUnclassifiedIPv432
AS43036Hostnode ABUnclassifiedIPv48
AS35565Infracom Managed Services ABUnclassifiedIPv44
AS208721Infracom Communications ABUnclassifiedIPv44

Adjacency

Adjacent networks

All 12

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

ASNetworkTypeFamiliesPaths seen
AS8473Bahnhof ABResidentialIPv4 IPv61,643
AS1257Tele2 Sverige ABMobileIPv4 IPv6658
AS49515DND Nordic ABUnclassifiedIPv4351
AS6939Hurricane Electric LLCTransitIPv4321
AS25223Infracom Managed Services ABUnclassifiedIPv4 IPv6150
AS197603Transtema Network Services ABUnclassifiedIPv4117
AS15912Infracom Connect ABUnclassifiedIPv4116
AS43591AddSecure ABUnclassifiedIPv432
AS43036Hostnode ABUnclassifiedIPv48
AS42303LM Layer and Mesh ABUnclassifiedIPv46

Provenance

Where this comes from

Derived from routing tables collected at 2026-10-19 10: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.