asn.dev

Observed topology

AS270042 AS270042 - RED DOT TECHNOLOGIES, C.A.

Unclassified ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS270042: 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
AS7195EDGEUNO S.A.SUnclassifiedIPv4107
AS23379Blackburn Technologies II, LLCUnclassifiedIPv4 IPv656
AS174Cogent Communications, LLCTransitIPv449

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS264628CORPORACION FIBEX TELECOM, C.A.ResidentialIPv4 IPv61,109
AS263223SATELITES Y TELECOMUNICACIONES C.AUnclassifiedIPv4 IPv6333
AS32109Reddot Networks Inc.UnclassifiedIPv4118
AS23379Blackburn Technologies II, LLCUnclassifiedIPv41
AS27648TELECOMUNICACIONES BANTEL, C.A.UnclassifiedIPv41

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS264628CORPORACION FIBEX TELECOM, C.A.ResidentialIPv4 IPv62,871
AS52320GlobeNet Cabos Submarinos Colombia, S.A.S.UnclassifiedIPv4 IPv62,358
AS7195EDGEUNO S.A.SUnclassifiedIPv4 IPv6841
AS23379Blackburn Technologies II, LLCUnclassifiedIPv4 IPv6467
AS174Cogent Communications, LLCTransitIPv4 IPv6439
AS263223SATELITES Y TELECOMUNICACIONES C.AUnclassifiedIPv4 IPv6333
AS32109Reddot Networks Inc.UnclassifiedIPv4118
AS27648TELECOMUNICACIONES BANTEL, C.A.UnclassifiedIPv41

Provenance

Where this comes from

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