asn.dev

Observed topology

AS267332 PROVEDOR NET MAIS LTDA - ME

Residential ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS267332: 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
AS53087TELY Ltda.ResidentialIPv4 IPv6378
AS267278PROVEDOR BAKANAS.NET LTDAResidentialIPv4 IPv6159

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS270891Fernandes e Silva Provedor de Internet Ltda-MeUnclassifiedIPv4 IPv6312
AS268439Claudenir dos Santos MEUnclassifiedIPv4 IPv6256
AS268504VM NET TELECOM EIRELIUnclassifiedIPv4 IPv6213
AS268464IAGO GUERRA RESENDE COMUNICACOES - MEUnclassifiedIPv4 IPv650
AS272503OSCAR TELECOMUNICAOES EIRELIUnclassifiedIPv61

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS53087TELY Ltda.ResidentialIPv4 IPv6979
AS267278PROVEDOR BAKANAS.NET LTDAResidentialIPv4 IPv6390
AS270891Fernandes e Silva Provedor de Internet Ltda-MeUnclassifiedIPv4 IPv6312
AS268439Claudenir dos Santos MEUnclassifiedIPv4 IPv6256
AS268504VM NET TELECOM EIRELIUnclassifiedIPv4 IPv6213
AS6939Hurricane Electric LLCTransitIPv456
AS267322SOLINTEL - SOLUCOES INTELIGENTES EM TELECOMUnclassifiedIPv456
AS268464IAGO GUERRA RESENDE COMUNICACOES - MEUnclassifiedIPv4 IPv650
AS272503OSCAR TELECOMUNICAOES EIRELIUnclassifiedIPv61

Provenance

Where this comes from

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