asn.dev

Observed topology

AS267629 AS267629 - SGV TI E TELECOM LTDA

Residential APNIC Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS267629: 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
AS4230CLARO S.A.ResidentialIPv4 IPv6276
AS6939Hurricane Electric LLCTransitIPv4 IPv6100
AS24482SG.GSHostingIPv4 IPv67
AS35280F5 Networks SARLHostingIPv4 IPv67
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv67

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS271645SUPERTEC TELECOM LTDA.UnclassifiedIPv4 IPv6615
AS271078VEM Tecnologia em Informatica LTDAUnclassifiedIPv4 IPv6245
AS271486AP SOLUCOES EM NETWORK E INFORMATICA EIRELIUnclassifiedIPv4 IPv692
AS263638Prefeitura de CuiabaUnclassifiedIPv41

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS4230CLARO S.A.ResidentialIPv4 IPv61,113
AS271645SUPERTEC TELECOM LTDA.UnclassifiedIPv4 IPv6615
AS271078VEM Tecnologia em Informatica LTDAUnclassifiedIPv4 IPv6245
AS6939Hurricane Electric LLCTransitIPv4 IPv6201
AS271486AP SOLUCOES EM NETWORK E INFORMATICA EIRELIUnclassifiedIPv4 IPv692
AS24482SG.GSHostingIPv4 IPv618
AS35280F5 Networks SARLHostingIPv4 IPv69
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv69
AS263638Prefeitura de CuiabaUnclassifiedIPv41

Provenance

Where this comes from

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