asn.dev

Observed topology

AS274749 Speed Connect

Residential LACNIC Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS274749: 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
AS266520VOOB TELECOMResidentialIPv6170
AS271201Vianet Telecomunicacoes LtdaResidentialIPv6160
AS24482SG.GSHostingIPv610

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS269586ARENNA FIBRA TELECOMUnclassifiedIPv4 IPv663
AS52778SANER TELECOM INFORMATICA LTDA MEUnclassifiedIPv462
AS271332MS NETUnclassifiedIPv462
AS268093DIRECTNET TELECOM LTDAUnclassifiedIPv426

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS271201Vianet Telecomunicacoes LtdaResidentialIPv4 IPv6307
AS266520VOOB TELECOMResidentialIPv4 IPv6265
AS269586ARENNA FIBRA TELECOMUnclassifiedIPv4 IPv697
AS52778SANER TELECOM INFORMATICA LTDA MEUnclassifiedIPv462
AS271332MS NETUnclassifiedIPv462
AS268093DIRECTNET TELECOM LTDAUnclassifiedIPv426
AS24482SG.GSHostingIPv4 IPv615

Provenance

Where this comes from

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