asn.dev

Observed topology

AS263920 MAST TELECOMUNICACOES E INFORMATICA LTDA

Residential LACNIC Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS263920: 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
AS61568ALOO TELECOM - FSF TECNOLOGIA SAResidentialIPv4 IPv6163
AS14840BR.Digital TelecomUnclassifiedIPv4 IPv6109
AS265290Uplink TelecomResidentialIPv4 IPv640

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS2673393M FibraUnclassifiedIPv4 IPv6499
AS267330JLCONECT PBUnclassifiedIPv4 IPv6389
AS266096NAVEGAR PROVEDORUnclassifiedIPv4 IPv6276
AS270305Acesse Internet LtdaUnclassifiedIPv4 IPv6223
AS269255JACINTO SILVEIRA COSTA MEResidentialIPv4 IPv6188
AS267287MEGANET PROVEDORUnclassifiedIPv4 IPv6101
AS270924JPA TelecomUnclassifiedIPv489

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS14840BR.Digital TelecomUnclassifiedIPv4 IPv61,157
AS61568ALOO TELECOM - FSF TECNOLOGIA SAResidentialIPv4 IPv6880
AS2673393M FibraUnclassifiedIPv4 IPv6499
AS267330JLCONECT PBUnclassifiedIPv4 IPv6389
AS266096NAVEGAR PROVEDORUnclassifiedIPv4 IPv6276
AS270305Acesse Internet LtdaUnclassifiedIPv4 IPv6223
AS269255JACINTO SILVEIRA COSTA MEResidentialIPv4 IPv6188
AS267287MEGANET PROVEDORUnclassifiedIPv4 IPv6101
AS270924JPA TelecomUnclassifiedIPv489
AS265290Uplink TelecomResidentialIPv4 IPv640

Provenance

Where this comes from

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