asn.dev

Observed topology

AS268155 AS268155 - TRACECOM SOLUCOES EM TI INFRA. E TELECOM. LTDA

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS268155: 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
AS269524Suprema Network Telecom LTDAResidentialIPv4 IPv6124

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS266015ALL FAST NETWORK LTDAUnclassifiedIPv4 IPv6212
AS270524R J C DA SILVA SERVICOSUnclassifiedIPv4 IPv692

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS269524Suprema Network Telecom LTDAResidentialIPv4 IPv6428
AS266015ALL FAST NETWORK LTDAUnclassifiedIPv4 IPv6212
AS270524R J C DA SILVA SERVICOSUnclassifiedIPv4 IPv692

Provenance

Where this comes from

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