asn.dev

Observed topology

AS263791 REFSA TELECOMUNICACIONES

Unclassified APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS263791: 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
AS7049Silica Networks Argentina S.A.UnclassifiedIPv4 IPv6214
AS52361ARSAT - Empresa Argentina de Soluciones Satelitales S.A.UnclassifiedIPv459

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS267773ANTANET SAUnclassifiedIPv4 IPv696
AS274850ALVAREZ MILCIADEUnclassifiedIPv4 IPv687
AS266710Gimenez Pedro Santiago (Clorindaconectada)UnclassifiedIPv459
AS274227MOSSO MAYRA ADELA (INTERZONA FORMOSA)UnclassifiedIPv459
AS266656COOPERATIVA DE SERVICIOS PUBLICOS EL COLORADO LTDAUnclassifiedIPv455
AS274101VANGUARD INTERNET SRLUnclassifiedIPv632

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS7049Silica Networks Argentina S.A.UnclassifiedIPv4 IPv6602
AS267773ANTANET SAUnclassifiedIPv4 IPv696
AS274850ALVAREZ MILCIADEUnclassifiedIPv4 IPv687
AS52361ARSAT - Empresa Argentina de Soluciones Satelitales S.A.UnclassifiedIPv459
AS266710Gimenez Pedro Santiago (Clorindaconectada)UnclassifiedIPv459
AS274227MOSSO MAYRA ADELA (INTERZONA FORMOSA)UnclassifiedIPv459
AS266656COOPERATIVA DE SERVICIOS PUBLICOS EL COLORADO LTDAUnclassifiedIPv455
AS274101VANGUARD INTERNET SRLUnclassifiedIPv632

Provenance

Where this comes from

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