asn.dev

Observed topology

AS271935 AS271935 - AIRTIME TECHNOLOGY SRL

Unclassified LACNIC Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS271935: 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
AS12956TELEFONICA GLOBAL SOLUTIONS SLTransitIPv4545
AS394684GOLD DATA USA INCUnclassifiedIPv4 IPv6528

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS274069PERSIL SERVICIOS MULTIPLES SRLUnclassifiedIPv490
AS274979PROYECTOR DE COMUNICACION RD EDISAMO SRLUnclassifiedIPv460
AS272797DSI DOMINICANA S.R.LUnclassifiedIPv42
AS274040ARTEL DOMINICANA SRLUnclassifiedIPv41
AS274052SERVICIOS INTEGRALES PARA TELECOMUNICACION SERVITELECOM SRLUnclassifiedIPv41

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS12956TELEFONICA GLOBAL SOLUTIONS SLTransitIPv4685
AS394684GOLD DATA USA INCUnclassifiedIPv4 IPv6542
AS274069PERSIL SERVICIOS MULTIPLES SRLUnclassifiedIPv490
AS274979PROYECTOR DE COMUNICACION RD EDISAMO SRLUnclassifiedIPv460
AS272797DSI DOMINICANA S.R.LUnclassifiedIPv42
AS274040ARTEL DOMINICANA SRLUnclassifiedIPv41
AS274052SERVICIOS INTEGRALES PARA TELECOMUNICACION SERVITELECOM SRLUnclassifiedIPv41

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.