asn.dev

Observed topology

AS264248 Bandeiranet Telecomunicacoes Ltda ME

Unclassified APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS264248: 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
AS23106AMERICAN TOWER DO BRASIL-COMUNICACAO MULTIMIDIA LTUnclassifiedIPv4 IPv6224
AS7738V talUnclassifiedIPv4 IPv623
AS24482SG.GSHostingIPv4 IPv612
AS35280F5 Networks SARLHostingIPv4 IPv67
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv67

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS267036INSPYRE INTERNETUnclassifiedIPv4 IPv6505

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS267036INSPYRE INTERNETUnclassifiedIPv4 IPv6505
AS7738V talUnclassifiedIPv4 IPv6451
AS23106AMERICAN TOWER DO BRASIL-COMUNICACAO MULTIMIDIA LTUnclassifiedIPv4 IPv6289
AS24482SG.GSHostingIPv4 IPv619
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv610
AS35280F5 Networks SARLHostingIPv4 IPv69

Provenance

Where this comes from

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