asn.dev

Observed topology

AS269144 AS269144 - SILVANET PROVEDOR DE INTERNET LTDA

Unclassified LACNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS269144: 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
AS61832DB3 SERVICOS DE TELECOMUNICACOES S.AUnclassifiedIPv4 IPv6148
AS268424GIGA MAIS FIBRA TELECOMUNICACOES S.A.UnclassifiedIPv4 IPv679
AS11432Telium Telecomunicacoes LtdaHostingIPv4 IPv678
AS273814Renato silva almeida e ciaUnclassifiedIPv461
AS268874IT FacilitiesUnclassifiedIPv417
AS6939Hurricane Electric LLCTransitIPv615
AS24482SG.GSHostingIPv4 IPv62

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS272458Speed Maxx Telecom Provedor de Internet LTDAUnclassifiedIPv631

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS61832DB3 SERVICOS DE TELECOMUNICACOES S.AUnclassifiedIPv4 IPv6178
AS268424GIGA MAIS FIBRA TELECOMUNICACOES S.A.UnclassifiedIPv4 IPv680
AS11432Telium Telecomunicacoes LtdaHostingIPv4 IPv678
AS273814Renato silva almeida e ciaUnclassifiedIPv461
AS272458Speed Maxx Telecom Provedor de Internet LTDAUnclassifiedIPv631
AS268874IT FacilitiesUnclassifiedIPv417
AS6939Hurricane Electric LLCTransitIPv615
AS24482SG.GSHostingIPv4 IPv62

Provenance

Where this comes from

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