asn.dev

Observed topology

AS28153 Micropic Ltda

Unclassified ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS28153: 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
AS263444Open X Tecnologia LtdaUnclassifiedIPv4 IPv6325
AS24482SG.GSHostingIPv4 IPv629
AS35280F5 Networks SARLHostingIPv4 IPv623
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv623
AS25091IP-Max SAUnclassifiedIPv62

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS268067Estivanet Multimidia e Telecom LtdaUnclassifiedIPv4 IPv6343
AS264286CRICCA COMERCIAL LTDAUnclassifiedIPv4 IPv6214
AS273586FLAVIO FERNANDO COSTAUnclassifiedIPv431

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS263444Open X Tecnologia LtdaUnclassifiedIPv4 IPv6892
AS268067Estivanet Multimidia e Telecom LtdaUnclassifiedIPv4 IPv6343
AS264286CRICCA COMERCIAL LTDAUnclassifiedIPv4 IPv6214
AS24482SG.GSHostingIPv4 IPv642
AS273586FLAVIO FERNANDO COSTAUnclassifiedIPv431
AS35280F5 Networks SARLHostingIPv4 IPv627
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv627
AS25091IP-Max SAUnclassifiedIPv62

Provenance

Where this comes from

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