asn.dev

Observed topology

AS269417 AS269417 - PONTOCOM SOLUCOES EM TECNOLOGIA LTDA

Unclassified LACNIC NSP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS269417: 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
AS268068TRAUDI INES SEHNEMResidentialIPv4 IPv691
AS6939Hurricane Electric LLCTransitIPv613
AS24482SG.GSHostingIPv4 IPv62

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS269427ONSTARK SISTEMAS INTELIGENTES LTDA -EPPUnclassifiedIPv4122
AS264434Rech e Bernardi LTDA MEUnclassifiedIPv427

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS268068TRAUDI INES SEHNEMResidentialIPv4 IPv6209
AS269427ONSTARK SISTEMAS INTELIGENTES LTDA -EPPUnclassifiedIPv4122
AS6939Hurricane Electric LLCTransitIPv4 IPv639
AS264434Rech e Bernardi LTDA MEUnclassifiedIPv427
AS24482SG.GSHostingIPv4 IPv67

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.