asn.dev

Observed topology

AS268487 AS268487 - PRISMA TELECOMUNICACOES LTDA. EPP

Unclassified LACNIC NSP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS268487: 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
AS263546TURBONETT TELECOMUNICACOES LTDA. - MEUnclassifiedIPv4251
AS6939Hurricane Electric LLCTransitIPv4 IPv6188
AS263935I5 TELECOMUnclassifiedIPv475
AS269194ST1 INTERNETResidentialIPv633
AS24482SG.GSHostingIPv4 IPv614
AS35280F5 Networks SARLHostingIPv4 IPv611
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv611

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS265447Hilink ComunicacoesUnclassifiedIPv44

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS263546TURBONETT TELECOMUNICACOES LTDA. - MEUnclassifiedIPv4251
AS6939Hurricane Electric LLCTransitIPv4 IPv6188
AS263935I5 TELECOMUnclassifiedIPv479
AS269194ST1 INTERNETResidentialIPv666
AS265447Hilink ComunicacoesUnclassifiedIPv4 IPv637
AS24482SG.GSHostingIPv4 IPv614
AS35280F5 Networks SARLHostingIPv4 IPv611
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv611

Provenance

Where this comes from

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