asn.dev

Observed topology

AS262433 AS262433 - QI Equipamentos para Informatica Ltda.

Residential ARIN Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS262433: 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
AS3356Level 3 Parent, LLCTransitIPv4 IPv6322
AS16735ALGAR TELECOM S/AUnclassifiedIPv4 IPv6188
AS6939Hurricane Electric LLCTransitIPv426
AS24482SG.GSHostingIPv4 IPv617
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv617
AS35280F5 Networks SARLHostingIPv4 IPv69

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS266917MARIPANET TELECOM LTDAResidentialIPv4 IPv6214
AS272272GILBERTO DE AGUIARUnclassifiedIPv4 IPv692

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS3356Level 3 Parent, LLCTransitIPv4 IPv6591
AS266917MARIPANET TELECOM LTDAResidentialIPv4 IPv6214
AS16735ALGAR TELECOM S/AUnclassifiedIPv4 IPv6210
AS272272GILBERTO DE AGUIARUnclassifiedIPv4 IPv692
AS6939Hurricane Electric LLCTransitIPv4 IPv639
AS24482SG.GSHostingIPv4 IPv618
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv618
AS35280F5 Networks SARLHostingIPv4 IPv69

Provenance

Where this comes from

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