Observed topology
AS3491 CONSOLE-CONNECT-ASN
Transit APNIC NSP
Transit
Upstream networks
Networks observed carrying traffic for AS3491: 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.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 4,062 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 4,033 |
| AS2914 | NTT America, Inc. | Transit | IPv4 IPv6 | 2,944 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 2,673 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 2,513 |
| AS9002 | RETN Limited | Unclassified | IPv4 IPv6 | 1,601 |
| AS577 | Bell Canada | Mobile | IPv4 IPv6 | 1,070 |
| AS7018 | AT&T Enterprises, LLC | Residential | IPv4 IPv6 | 1,041 |
| AS3257 | GTT Communications Inc. | Transit | IPv4 IPv6 | 933 |
| AS6762 | TELECOM ITALIA SPARKLE S.p.A. | Transit | IPv4 IPv6 | 565 |
Transit
Downstream networks
Networks for which AS3491 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS7552 | Viettel Group | Mobile | IPv4 IPv6 | 63,357 |
| AS4760 | HKT Limited | Residential | IPv4 IPv6 | 34,659 |
| AS152194 | CTG Server Limited | Unclassified | IPv4 | 30,169 |
| AS9924 | Taiwan Fixed Network, Telco and Network Service Provider. | Residential | IPv4 IPv6 | 26,156 |
| AS36992 | ETISALAT MISR | Mobile | IPv4 IPv6 | 23,068 |
| AS4780 | Digital United Inc. | Residential | IPv4 | 18,710 |
| AS45899 | VNPT Corp | Mobile | IPv4 IPv6 | 16,266 |
| AS4515 | PCCW IMS Ltd (PCCW Business Internet Access) | Unclassified | IPv4 IPv6 | 16,208 |
| AS399077 | Tcloudnet | Hosting | IPv4 IPv6 | 13,757 |
| AS20473 | The Constant Company, LLC | Hosting | IPv4 IPv6 | 13,452 |
Adjacency
Adjacent networks
Every AS seen directly next to AS3491 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS38001 | NewMedia Express Pte Ltd | Hosting | IPv4 IPv6 | 439,464 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 166,446 |
| AS577 | Bell Canada | Mobile | IPv4 IPv6 | 148,175 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 133,780 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 128,554 |
| AS852 | TELUS Communications Inc. | Residential | IPv4 IPv6 | 116,907 |
| AS7018 | AT&T Enterprises, LLC | Residential | IPv4 IPv6 | 112,116 |
| AS3741 | Dimension Data | Unclassified | IPv4 | 104,942 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 104,846 |
| AS17639 | Converge ICT Solutions Inc. | Unclassified | IPv4 IPv6 | 104,473 |
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.