asn.dev

Observed topology

AS263153 Work Banda Larga

Residential ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS263153: 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
AS264409Huge Solucoes Corporativas LtdaUnclassifiedIPv4 IPv685
AS6939Hurricane Electric LLCTransitIPv439
AS53181Avanca Telecom e Servicos LTDAUnclassifiedIPv4 IPv69
AS24482SG.GSHostingIPv43
AS35280F5 Networks SARLHostingIPv43
AS37721Virtual Technologies & SolutionsResidentialIPv43

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS271352Starsat Telecom Comercio e Servicos LTDAUnclassifiedIPv4 IPv695
AS270610WORK INTERNETUnclassifiedIPv461

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS264409Huge Solucoes Corporativas LtdaUnclassifiedIPv4 IPv6228
AS271352Starsat Telecom Comercio e Servicos LTDAUnclassifiedIPv4 IPv695
AS270610WORK INTERNETUnclassifiedIPv461
AS6939Hurricane Electric LLCTransitIPv457
AS53181Avanca Telecom e Servicos LTDAUnclassifiedIPv4 IPv625
AS265043GPP SOLUCOES EM INFORMATICAResidentialIPv47
AS24482SG.GSHostingIPv45
AS35280F5 Networks SARLHostingIPv43
AS37721Virtual Technologies & SolutionsResidentialIPv43

Provenance

Where this comes from

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