asn.dev

Observed topology

AS269658 AS269658 - HUGS TELECOM

Unclassified APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS269658: 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
AS6939Hurricane Electric LLCTransitIPv4 IPv677
AS269558B S V TELECOMUNICACOES E SERVICOS LTDAResidentialIPv4 IPv668
AS263362REDE SPEEDNET TELECOM LTDAResidentialIPv68
AS24482SG.GSHostingIPv63
AS35280F5 Networks SARLHostingIPv62
AS37721Virtual Technologies & SolutionsResidentialIPv62

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS270497HRCNET TELECOM LTDAUnclassifiedIPv631
AS269107J L TELECOMUNICACAO E MULTIMIDIA COMERCIO E SERVICResidentialIPv4 IPv621

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS269558B S V TELECOMUNICACOES E SERVICOS LTDAResidentialIPv4 IPv6104
AS6939Hurricane Electric LLCTransitIPv4 IPv692
AS270497HRCNET TELECOM LTDAUnclassifiedIPv631
AS269107J L TELECOMUNICACAO E MULTIMIDIA COMERCIO E SERVICResidentialIPv4 IPv621
AS263362REDE SPEEDNET TELECOM LTDAResidentialIPv68
AS24482SG.GSHostingIPv64
AS35280F5 Networks SARLHostingIPv62
AS37721Virtual Technologies & SolutionsResidentialIPv62

Provenance

Where this comes from

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