asn.dev

Observed topology

AS268085 Plusnetfoz Provedor de Internet Ltda -ME

Unclassified APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS268085: 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 IPv6391
AS265207PLUS PROVEDOR DE INTERNET LTDA - MEUnclassifiedIPv4158
AS53062GGNET TELECOMUNICACOES LTDAUnclassifiedIPv4 IPv6110
AS262740VELOO NET LTDAResidentialIPv4 IPv672
AS264998SQUID NET TELECOMUNICACOES LTDA MEUnclassifiedIPv4 IPv627
AS60503FNX Tecnologia LTDAUnclassifiedIPv423
AS35280F5 Networks SARLHostingIPv4 IPv615
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv64
AS24482SG.GSHostingIPv62

Transit

Downstream networks

inferred

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

No downstream observed. This network does not appear to carry transit for anyone.

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS3356Level 3 Parent, LLCTransitIPv4 IPv6391
AS265207PLUS PROVEDOR DE INTERNET LTDA - MEUnclassifiedIPv4158
AS53062GGNET TELECOMUNICACOES LTDAUnclassifiedIPv4 IPv6110
AS262740VELOO NET LTDAResidentialIPv4 IPv672
AS264998SQUID NET TELECOMUNICACOES LTDA MEUnclassifiedIPv4 IPv627
AS60503FNX Tecnologia LTDAUnclassifiedIPv423
AS35280F5 Networks SARLHostingIPv4 IPv615
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv64
AS24482SG.GSHostingIPv62

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.