asn.dev

Observed topology

AS268890 AS268890 - ASTERNET SERVICOS DE COMUNICACAO MULTIMIDIA LTDA

Unclassified ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS268890: 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
AS28189JR & JS ENGENHARIA E COMERCIO LTDAUnclassifiedIPv4 IPv6421
AS6939Hurricane Electric LLCTransitIPv418
AS263966WORLD WIFI TELECOMUNICACOES LTDA - MEResidentialIPv43

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS268485Fibrativa Telecomunicacoes - Eireli - MEResidentialIPv429

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS28189JR & JS ENGENHARIA E COMERCIO LTDAUnclassifiedIPv4 IPv6570
AS268485Fibrativa Telecomunicacoes - Eireli - MEResidentialIPv499
AS263966WORLD WIFI TELECOMUNICACOES LTDA - MEResidentialIPv435
AS6939Hurricane Electric LLCTransitIPv418
AS272163LBC CAVALCANTE PARAISO FIBRA LTDAResidentialIPv414
AS22381SAMM TECNOLOGIA E TELECOMUNICACOES S.AUnclassifiedIPv44

Provenance

Where this comes from

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