asn.dev

Observed topology

AS263165 MARVITEL TELECOM

Unclassified APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS263165: 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
AS4230CLARO S.A.ResidentialIPv4 IPv6416
AS37468Angola CablesUnclassifiedIPv4 IPv630

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS28261EMPRESA SERGIPANA DE TECNOLOGIA DA INFORMACAOUnclassifiedIPv4 IPv6370
AS262393A ALVES GOMES INFORMATICA - MEResidentialIPv458
AS266589Sociedade de Educacao Tiradentes S.A.UnclassifiedIPv436
AS269607SERGIPE MINISTERIO PUBLICOUnclassifiedIPv430
AS275631CONEXAO ZN LTDAUnclassifiedIPv617

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS4230CLARO S.A.ResidentialIPv4 IPv6924
AS28261EMPRESA SERGIPANA DE TECNOLOGIA DA INFORMACAOUnclassifiedIPv4 IPv6370
AS262393A ALVES GOMES INFORMATICA - MEResidentialIPv458
AS266589Sociedade de Educacao Tiradentes S.A.UnclassifiedIPv436
AS37468Angola CablesUnclassifiedIPv4 IPv633
AS269607SERGIPE MINISTERIO PUBLICOUnclassifiedIPv430
AS275631CONEXAO ZN LTDAUnclassifiedIPv617

Provenance

Where this comes from

Derived from routing tables collected at 2026-10-25 12: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.