asn.dev

Observed topology

AS263536 MICROSET MAQUINAS E SERVICOS LTDA

Residential RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS263536: 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
AS263558RD TELECOM LTDA -MEResidentialIPv4 IPv61,027
AS16735ALGAR TELECOM S/AUnclassifiedIPv4570
AS6939Hurricane Electric LLCTransitIPv4 IPv6318
AS270724CLIENT.CO SERVICOS E TELECOMUNICACOES LTDAUnclassifiedIPv492
AS24482SG.GSHostingIPv4 IPv633
AS52468UFINET PANAMA S.A.UnclassifiedIPv69
AS37721Virtual Technologies & SolutionsResidentialIPv42

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS262693WCOM COM E SERV TELECOM LTDAUnclassifiedIPv461

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS263558RD TELECOM LTDA -MEResidentialIPv4 IPv61,027
AS16735ALGAR TELECOM S/AUnclassifiedIPv4618
AS6939Hurricane Electric LLCTransitIPv4 IPv6329
AS270724CLIENT.CO SERVICOS E TELECOMUNICACOES LTDAUnclassifiedIPv492
AS262693WCOM COM E SERV TELECOM LTDAUnclassifiedIPv461
AS24482SG.GSHostingIPv4 IPv634
AS52468UFINET PANAMA S.A.UnclassifiedIPv69
AS37721Virtual Technologies & SolutionsResidentialIPv43

Provenance

Where this comes from

Derived from routing tables collected at 2026-10-29 10:00 UTC by route-views2,rrc00, as seen from 76 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.