Observed topology
AS29468 INFRACOM
Residential APNIC
Transit
Upstream networks
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.
Transit
Downstream networks
Networks for which AS29468 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS49515 | DND Nordic AB | Unclassified | IPv4 | 351 |
| AS25223 | Infracom Managed Services AB | Unclassified | IPv4 IPv6 | 150 |
| AS15912 | Infracom Connect AB | Unclassified | IPv4 | 116 |
| AS197603 | Transtema Network Services AB | Unclassified | IPv4 | 114 |
| AS43591 | AddSecure AB | Unclassified | IPv4 | 32 |
| AS43036 | Hostnode AB | Unclassified | IPv4 | 8 |
| AS35565 | Infracom Managed Services AB | Unclassified | IPv4 | 4 |
| AS208721 | Infracom Communications AB | Unclassified | IPv4 | 4 |
Adjacency
Adjacent networks
Every AS seen directly next to AS29468 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS8473 | Bahnhof AB | Residential | IPv4 IPv6 | 1,643 |
| AS1257 | Tele2 Sverige AB | Mobile | IPv4 IPv6 | 658 |
| AS49515 | DND Nordic AB | Unclassified | IPv4 | 351 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 | 321 |
| AS25223 | Infracom Managed Services AB | Unclassified | IPv4 IPv6 | 150 |
| AS197603 | Transtema Network Services AB | Unclassified | IPv4 | 117 |
| AS15912 | Infracom Connect AB | Unclassified | IPv4 | 116 |
| AS43591 | AddSecure AB | Unclassified | IPv4 | 32 |
| AS43036 | Hostnode AB | Unclassified | IPv4 | 8 |
| AS42303 | LM Layer and Mesh AB | Unclassified | IPv4 | 6 |
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.