asn.dev

Observed topology

AS268941 PAGSEGURO INTERNET S.A.

Unclassified AFRINIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS268941: 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
AS13335Cloudflare, Inc.HostingIPv4320
AS4230CLARO S.A.ResidentialIPv4 IPv6301
AS202Level 3 Parent, LLCUnclassifiedIPv4 IPv6191
AS10429TELEFONICA BRASIL S.AResidentialIPv4182
AS13878Scala Data CentersUnclassifiedIPv4172
AS3356Level 3 Parent, LLCTransitIPv4 IPv6165
AS19089Scala Data CentersUnclassifiedIPv441

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS7162Universo Online S.A.HostingIPv4117

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS4230CLARO S.A.ResidentialIPv4 IPv6418
AS13335Cloudflare, Inc.HostingIPv4320
AS202Level 3 Parent, LLCUnclassifiedIPv4 IPv6191
AS10429TELEFONICA BRASIL S.AResidentialIPv4182
AS13878Scala Data CentersUnclassifiedIPv4172
AS3356Level 3 Parent, LLCTransitIPv4 IPv6165
AS7162Universo Online S.A.HostingIPv4117
AS19089Scala Data CentersUnclassifiedIPv441

Provenance

Where this comes from

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