asn.dev

Observed topology

AS61708 AS61708 - INFOCAT INFORMATICA LTDA

Unclassified LACNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS61708: 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
AS37468Angola CablesUnclassifiedIPv4 IPv6194
AS16735ALGAR TELECOM S/AUnclassifiedIPv4 IPv692
AS61832DB3 SERVICOS DE TELECOMUNICACOES S.AUnclassifiedIPv4 IPv674
AS61775AW FibraResidentialIPv460
AS52468UFINET PANAMA S.A.UnclassifiedIPv49
AS28368unnamedResidentialIPv4 IPv62
AS28370GUIFAMI Informatica Ltda.UnclassifiedIPv41

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS273544Alex Ferreira dos SantosUnclassifiedIPv633

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS37468Angola CablesUnclassifiedIPv4 IPv6194
AS61775AW FibraResidentialIPv4 IPv693
AS16735ALGAR TELECOM S/AUnclassifiedIPv4 IPv692
AS61832DB3 SERVICOS DE TELECOMUNICACOES S.AUnclassifiedIPv4 IPv674
AS273544Alex Ferreira dos SantosUnclassifiedIPv633
AS52468UFINET PANAMA S.A.UnclassifiedIPv49
AS28368unnamedResidentialIPv4 IPv62
AS28370GUIFAMI Informatica Ltda.UnclassifiedIPv41

Provenance

Where this comes from

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