asn.dev

Observed topology

AS28670 CST SERVICOS DE INFORMATICA E CALL CENTER LTDA.

Residential LACNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS28670: 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
AS14840BR.Digital TelecomUnclassifiedIPv4 IPv6165
AS6939Hurricane Electric LLCTransitIPv4 IPv644
AS24482SG.GSHostingIPv61

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS61571Metro TecnologiaUnclassifiedIPv4 IPv693
AS272212ILUMINET INTERNETUnclassifiedIPv4 IPv693
AS270765VIVA PIXEL AGENCIA DIGITALUnclassifiedIPv4 IPv661

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS14840BR.Digital TelecomUnclassifiedIPv4 IPv6292
AS6939Hurricane Electric LLCTransitIPv4 IPv6110
AS61571Metro TecnologiaUnclassifiedIPv4 IPv693
AS272212ILUMINET INTERNETUnclassifiedIPv4 IPv693
AS270765VIVA PIXEL AGENCIA DIGITALUnclassifiedIPv4 IPv661
AS16735ALGAR TELECOM S/AUnclassifiedIPv4 IPv628
AS53062GGNET TELECOMUNICACOES LTDAUnclassifiedIPv4 IPv622
AS24482SG.GSHostingIPv64
AS37721Virtual Technologies & SolutionsResidentialIPv61

Provenance

Where this comes from

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