asn.dev

Observed topology

AS53236 JF Solucoes Informatica Ltda.

Residential APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS53236: 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
AS61568ALOO TELECOM - FSF TECNOLOGIA SAResidentialIPv4 IPv6162
AS529651TELECOM SERVICOS DE TECNOLOGIA EM INTERNET LTDAUnclassifiedIPv4 IPv696
AS28126BRISANET SERVICOS DE TELECOMUNICACOES S.AResidentialIPv475
AS6939Hurricane Electric LLCTransitIPv430
AS24482SG.GSHostingIPv4 IPv69
AS37721Virtual Technologies & SolutionsResidentialIPv48
AS35280F5 Networks SARLHostingIPv45

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS267086MUNICIPIO DE ESTANCIAUnclassifiedIPv4 IPv698

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS61568ALOO TELECOM - FSF TECNOLOGIA SAResidentialIPv4 IPv6224
AS529651TELECOM SERVICOS DE TECNOLOGIA EM INTERNET LTDAUnclassifiedIPv4 IPv6125
AS267086MUNICIPIO DE ESTANCIAUnclassifiedIPv4 IPv698
AS28126BRISANET SERVICOS DE TELECOMUNICACOES S.AResidentialIPv482
AS6939Hurricane Electric LLCTransitIPv430
AS24482SG.GSHostingIPv4 IPv69
AS37721Virtual Technologies & SolutionsResidentialIPv48
AS35280F5 Networks SARLHostingIPv45

Provenance

Where this comes from

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