asn.dev

Observed topology

AS267575 MARANET TELECOM LTDA

Unclassified APNIC NSP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS267575: 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
AS269194ST1 INTERNETResidentialIPv4 IPv61,056
AS262503WIKI TELECOMUNICACOES EIRELIUnclassifiedIPv4 IPv6143
AS6939Hurricane Electric LLCTransitIPv4 IPv6104
AS265269MEGA TELE INFORMATICAUnclassifiedIPv4 IPv694
AS24482SG.GSHostingIPv4 IPv611

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS264941Satcom Telecom Comercio e Servicos LtdaUnclassifiedIPv4 IPv6521
AS267656Martins e Barros LTDAUnclassifiedIPv4 IPv6334
AS269229Superondas Internet Ltda.UnclassifiedIPv4 IPv6299
AS271493SPEED NET PEDRAUnclassifiedIPv4 IPv6213

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS269194ST1 INTERNETResidentialIPv4 IPv61,625
AS264941Satcom Telecom Comercio e Servicos LtdaUnclassifiedIPv4 IPv6521
AS262503WIKI TELECOMUNICACOES EIRELIUnclassifiedIPv4 IPv6438
AS265269MEGA TELE INFORMATICAUnclassifiedIPv4 IPv6417
AS267656Martins e Barros LTDAUnclassifiedIPv4 IPv6334
AS269229Superondas Internet Ltda.UnclassifiedIPv4 IPv6299
AS6939Hurricane Electric LLCTransitIPv4 IPv6259
AS271493SPEED NET PEDRAUnclassifiedIPv4 IPv6213
AS24482SG.GSHostingIPv4 IPv636

Provenance

Where this comes from

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