asn.dev

Observed topology

AS28606 FSOnline Internet

Residential LACNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS28606: 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
AS53087TELY Ltda.ResidentialIPv4 IPv6169
AS14840BR.Digital TelecomUnclassifiedIPv4 IPv6165
AS6939Hurricane Electric LLCTransitIPv4 IPv689
AS52566SISALWEB INTERNETResidentialIPv462
AS270671Melo Oliveira Informatica Ltda MEUnclassifiedIPv418
AS24482SG.GSHostingIPv4 IPv69

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS61906UNIMAX TELECOMResidentialIPv4 IPv6103
AS270671Melo Oliveira Informatica Ltda MEUnclassifiedIPv4 IPv611

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv6188
AS53087TELY Ltda.ResidentialIPv4 IPv6169
AS14840BR.Digital TelecomUnclassifiedIPv4 IPv6165
AS61906UNIMAX TELECOMResidentialIPv4 IPv6103
AS52566SISALWEB INTERNETResidentialIPv462
AS270671Melo Oliveira Informatica Ltda MEUnclassifiedIPv4 IPv629
AS24482SG.GSHostingIPv4 IPv619
AS37721Virtual Technologies & SolutionsResidentialIPv45

Provenance

Where this comes from

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