asn.dev

Observed topology

AS269075 GO-NET FIBRA

Residential LACNIC Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS269075: 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 IPv676
AS267079MUNDO ONLINEUnclassifiedIPv430
AS53427TGLOBAL NETWORKSUnclassifiedIPv4 IPv628
AS262740VELOO NET LTDAResidentialIPv625
AS270735COMPUTIZE NETWORK TELECOMUNICACOES LTDAHostingIPv4 IPv612
AS24482SG.GSHostingIPv4 IPv66
AS16735ALGAR TELECOM S/AUnclassifiedIPv65
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv65
AS35280F5 Networks SARLHostingIPv4 IPv64

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS270751RNET TELECOM LTDA MEResidentialIPv4 IPv6233
AS268126DGNETSP EIRELIResidentialIPv4 IPv660

Adjacency

Adjacent networks

All 11

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

ASNetworkTypeFamiliesPaths seen
AS270735COMPUTIZE NETWORK TELECOMUNICACOES LTDAHostingIPv4 IPv6522
AS268126DGNETSP EIRELIResidentialIPv4 IPv6444
AS270751RNET TELECOM LTDA MEResidentialIPv4 IPv6379
AS267079MUNDO ONLINEUnclassifiedIPv4 IPv6151
AS53427TGLOBAL NETWORKSUnclassifiedIPv4 IPv6111
AS6939Hurricane Electric LLCTransitIPv4 IPv6104
AS262740VELOO NET LTDAResidentialIPv4 IPv6100
AS24482SG.GSHostingIPv4 IPv612
AS16735ALGAR TELECOM S/AUnclassifiedIPv65
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv65

All 11 adjacent →

Provenance

Where this comes from

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