asn.dev

Observed topology

AS269185 AS269185 - Globalfiber Telecom LTDA

Unclassified LACNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS269185: 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
AS53062GGNET TELECOMUNICACOES LTDAUnclassifiedIPv4934
AS271253LINK BRASIL TELECOMUNICACOES LTDAUnclassifiedIPv4249
AS529651TELECOM SERVICOS DE TECNOLOGIA EM INTERNET LTDAUnclassifiedIPv4 IPv6155
AS271597NEW LINK CONNECTUnclassifiedIPv4 IPv691
AS1031PEER 1031 LLCUnclassifiedIPv415

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS271628GIGANET FIBRAUnclassifiedIPv4 IPv692

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS53062GGNET TELECOMUNICACOES LTDAUnclassifiedIPv4934
AS271253LINK BRASIL TELECOMUNICACOES LTDAUnclassifiedIPv4249
AS271597NEW LINK CONNECTUnclassifiedIPv4 IPv6183
AS529651TELECOM SERVICOS DE TECNOLOGIA EM INTERNET LTDAUnclassifiedIPv4 IPv6155
AS271628GIGANET FIBRAUnclassifiedIPv4 IPv692
AS1031PEER 1031 LLCUnclassifiedIPv415

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.