asn.dev

Observed topology

AS28610 AS28610 - DEBIAN SIGNAL COMUNICACAO MULTIMIDIA LTDA ME

Residential ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS28610: 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
AS268624Gamers Club LtdaUnclassifiedIPv4 IPv6229
AS6939Hurricane Electric LLCTransitIPv4 IPv659
AS35280F5 Networks SARLHostingIPv4 IPv69
AS60503FNX Tecnologia LTDAUnclassifiedIPv49
AS24482SG.GSHostingIPv63
AS37721Virtual Technologies & SolutionsResidentialIPv63
AS16735ALGAR TELECOM S/AUnclassifiedIPv61

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS264178Coonexao Telecom e Informatica EIRELIUnclassifiedIPv461
AS263650Clicfacil TelecomUnclassifiedIPv460

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS268624Gamers Club LtdaUnclassifiedIPv4 IPv6330
AS6939Hurricane Electric LLCTransitIPv4 IPv669
AS264178Coonexao Telecom e Informatica EIRELIUnclassifiedIPv461
AS263650Clicfacil TelecomUnclassifiedIPv460
AS35280F5 Networks SARLHostingIPv4 IPv611
AS60503FNX Tecnologia LTDAUnclassifiedIPv410
AS16735ALGAR TELECOM S/AUnclassifiedIPv4 IPv66
AS24482SG.GSHostingIPv4 IPv64
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv64

Provenance

Where this comes from

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