asn.dev

Observed topology

AS263913 AS263913 - CIDADE ONLINE LTDA

Unclassified LACNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS263913: 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
AS267613ELETRONET S.A.UnclassifiedIPv4 IPv6460
AS61832DB3 SERVICOS DE TELECOMUNICACOES S.AUnclassifiedIPv4 IPv6405
AS28368unnamedResidentialIPv415

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS271520PLANET LINK LTDAUnclassifiedIPv4 IPv6153
AS267944Intercol Serv de Aux a Internet eireli MeUnclassifiedIPv4 IPv666

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS61832DB3 SERVICOS DE TELECOMUNICACOES S.AUnclassifiedIPv4 IPv6567
AS267613ELETRONET S.A.UnclassifiedIPv4 IPv6502
AS271520PLANET LINK LTDAUnclassifiedIPv4 IPv6153
AS267944Intercol Serv de Aux a Internet eireli MeUnclassifiedIPv4 IPv666
AS28368unnamedResidentialIPv4 IPv630

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.