asn.dev

Observed topology

AS53112 AS53112 - SULNET TELECOM

Unclassified RIPE Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS53112: 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
AS8167V talResidentialIPv4 IPv6185
AS28283Adylnet TelecomResidentialIPv4 IPv6183
AS53062GGNET TELECOMUNICACOES LTDAUnclassifiedIPv4 IPv6133

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS269133Fundacao Regional Integrada - Campus Santo AngeloUnclassifiedIPv4 IPv695

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS28283Adylnet TelecomResidentialIPv4 IPv6256
AS8167V talResidentialIPv4 IPv6206
AS53062GGNET TELECOMUNICACOES LTDAUnclassifiedIPv4 IPv6133
AS269133Fundacao Regional Integrada - Campus Santo AngeloUnclassifiedIPv4 IPv695
AS262907BRASIL TECPAR AMIGO AVATOResidentialIPv41

Provenance

Where this comes from

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