asn.dev

Observed topology

AS268272 TBN TELECOMUNICACOES LTDA ME

Residential ARIN Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS268272: 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
AS8167V talResidentialIPv4 IPv6143
AS267256ONETIS TECNOLOGIA LTDAUnclassifiedIPv4 IPv6128
AS7738V talUnclassifiedIPv469
AS264275ROLIM NET TECNOLOGIA LTDAUnclassifiedIPv461

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS52926ZAPNET Provedor de Internet Eireli - MEUnclassifiedIPv4 IPv6250
AS268176LINK TELECOM EIRELIUnclassifiedIPv4 IPv6182
AS262568Netvia Telecom Provedor de Internet Ltda.UnclassifiedIPv4 IPv695

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS267256ONETIS TECNOLOGIA LTDAUnclassifiedIPv4 IPv6467
AS8167V talResidentialIPv4 IPv6255
AS52926ZAPNET Provedor de Internet Eireli - MEUnclassifiedIPv4 IPv6250
AS268176LINK TELECOM EIRELIUnclassifiedIPv4 IPv6182
AS7738V talUnclassifiedIPv4145
AS262568Netvia Telecom Provedor de Internet Ltda.UnclassifiedIPv4 IPv695
AS264275ROLIM NET TECNOLOGIA LTDAUnclassifiedIPv461

Provenance

Where this comes from

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