asn.dev

Observed topology

AS270442 AS270442 - G15NET LTDA

Residential LACNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS270442: 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
AS22381SAMM TECNOLOGIA E TELECOMUNICACOES S.AUnclassifiedIPv4 IPv690
AS6939Hurricane Electric LLCTransitIPv4 IPv658
AS24482SG.GSHostingIPv4 IPv64
AS35280F5 Networks SARLHostingIPv4 IPv64
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv64

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS273766Rural TelecomUnclassifiedIPv628

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS22381SAMM TECNOLOGIA E TELECOMUNICACOES S.AUnclassifiedIPv4 IPv6105
AS6939Hurricane Electric LLCTransitIPv4 IPv673
AS273766Rural TelecomUnclassifiedIPv4 IPv632
AS24482SG.GSHostingIPv4 IPv66
AS35280F5 Networks SARLHostingIPv4 IPv64
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv64

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.