asn.dev

Observed topology

AS269499 AS269499 - FIBRALINK INTERNET E TELECOMUNICACOES LTDA

Residential LACNIC Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS269499: 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 IPv6218
AS52468UFINET PANAMA S.A.UnclassifiedIPv4 IPv661
AS3356Level 3 Parent, LLCTransitIPv4 IPv647
AS1031PEER 1031 LLCUnclassifiedIPv4 IPv68
AS3303Swisscom (Schweiz) AGResidentialIPv42
AS33891Core-Backbone GmbHHostingIPv41

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS2638523M DE MAGE INFORMATICA LTDAUnclassifiedIPv414

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv6231
AS52468UFINET PANAMA S.A.UnclassifiedIPv4 IPv661
AS3356Level 3 Parent, LLCTransitIPv4 IPv647
AS2638523M DE MAGE INFORMATICA LTDAUnclassifiedIPv414
AS1031PEER 1031 LLCUnclassifiedIPv4 IPv68
AS3303Swisscom (Schweiz) AGResidentialIPv42
AS33891Core-Backbone GmbHHostingIPv41
AS35280F5 Networks SARLHostingIPv41

Provenance

Where this comes from

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