asn.dev

Observed topology

AS265989 GARCIA TELECOMUNICACOES LTDA

Unclassified APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS265989: 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
AS271253LINK BRASIL TELECOMUNICACOES LTDAUnclassifiedIPv4 IPv6611
AS267232Good Net Provedor de Internet Ltda - EPPUnclassifiedIPv668
AS1031PEER 1031 LLCUnclassifiedIPv44

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS270714NETFIBRA MS COMUNICACAO LTDAUnclassifiedIPv4 IPv6111
AS267232Good Net Provedor de Internet Ltda - EPPUnclassifiedIPv461

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS271253LINK BRASIL TELECOMUNICACOES LTDAUnclassifiedIPv4 IPv6730
AS267232Good Net Provedor de Internet Ltda - EPPUnclassifiedIPv4 IPv6129
AS270714NETFIBRA MS COMUNICACAO LTDAUnclassifiedIPv4 IPv6111
AS6939Hurricane Electric LLCTransitIPv4 IPv638
AS1031PEER 1031 LLCUnclassifiedIPv413
AS24482SG.GSHostingIPv4 IPv63
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv62
AS35280F5 Networks SARLHostingIPv41

Provenance

Where this comes from

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