asn.dev

Observed topology

AS266771 MAKRONET CONSULTING TECNOLOGIA E INFORMATICA LIMITADA

Upstreams 3 carry this network
Downstreams 14 this network carries
Adjacent (IPv4) 17
Adjacent (IPv6) 6

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS266771: 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
AS263237PowerHost Telecom SPAUnclassifiedIPv4 IPv6425
AS3356Level 3 Parent, LLCTransitIPv4 IPv6219
AS7195EDGEUNO S.A.SUnclassifiedIPv4 IPv6157

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.

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS264681Sociedad de Telecomunicaciones Netsouth SPAUnclassifiedIPv4 IPv61,070
AS52439OPTIC TELECOMUNICACIONES LIMITADAResidentialIPv4695
AS269988BINET NETWORKING DATA LIMITADAUnclassifiedIPv4332
AS27979Stel Chile S.A.UnclassifiedIPv4268
AS270024ICONEX SPAResidentialIPv4247
AS61444Enlaces Regionales de Chile S.A.HostingIPv4156
AS273879CRONET TELECOM SPAUnclassifiedIPv4 IPv6101
AS271869SERVICIOS ZONALES DE INTERNET LIMITADAResidentialIPv4 IPv682
AS27897UNIVERSIDAD DE SANTIAGO DE CHILEUnclassifiedIPv478
AS17044THE INTERPUBLIC GROUP OF COMPANIES, INC.UnclassifiedIPv467
AS274216MOVILMAX CHILE TELECOMUNICACIONES SPAUnclassifiedIPv461
AS27855AXESAT S.AUnclassifiedIPv460
AS28319WISPUnclassifiedIPv460
AS274327TELECOMUNICACIONES M Y F LIMITADAUnclassifiedIPv416

Adjacency

Adjacent networks

23 shown

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

ASNetworkTypeFamiliesPaths seen
AS7195EDGEUNO S.A.SUnclassifiedIPv4 IPv62,463
AS264681Sociedad de Telecomunicaciones Netsouth SPAUnclassifiedIPv4 IPv62,064
AS3356Level 3 Parent, LLCTransitIPv4 IPv61,764
AS263237PowerHost Telecom SPAUnclassifiedIPv4 IPv6960
AS52439OPTIC TELECOMUNICACIONES LIMITADAResidentialIPv4695
AS269988BINET NETWORKING DATA LIMITADAUnclassifiedIPv4390
AS27979Stel Chile S.A.UnclassifiedIPv4268
AS270024ICONEX SPAResidentialIPv4247
AS61444Enlaces Regionales de Chile S.A.HostingIPv4156
AS271869SERVICIOS ZONALES DE INTERNET LIMITADAResidentialIPv4 IPv6123
AS273879CRONET TELECOM SPAUnclassifiedIPv4 IPv6101
AS27897UNIVERSIDAD DE SANTIAGO DE CHILEUnclassifiedIPv478
AS17044THE INTERPUBLIC GROUP OF COMPANIES, INC.UnclassifiedIPv467
AS274216MOVILMAX CHILE TELECOMUNICACIONES SPAUnclassifiedIPv461
AS27855AXESAT S.AUnclassifiedIPv460
AS28319WISPUnclassifiedIPv460
AS274327TELECOMUNICACIONES M Y F LIMITADAUnclassifiedIPv416

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.

Interconnection

Exchange presence

recorded

Internet exchanges where Packet Clearing House has a port recorded for AS266771, largest fabric first. An exchange is shared switching where networks interconnect directly rather than paying a transit provider to carry traffic between them, so turning up at one is a deliberate choice about how this network wants to be reached. Each name opens that exchange's own page, with its peering LANs and every other network recorded on it.

No exchange membership on file. That is not the same as peering nowhere: the dataset records what PCH has collected, and many exchanges publish no participant list at all.

Unlike the tables above, this is recorded rather than inferred. An address on a peering LAN is at that exchange by definition. Two carve-outs all the same. Member ports counts every participant at the exchange, not this network's ports, so read it as a size proxy. And an absent exchange means PCH has no record of it, not that the network is not there.

Provenance

Where this comes from

Derived from routing tables collected at 2026-08-08 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 74.02M route entries. These are observations from those vantage points, not a complete or authoritative view of the internet.

Cross-check against RIPEstat or BGP.tools, which observe from a different and larger set of vantage points.

Exchange presence comes from a separate dataset: the directory collected 2026-08-09 by Packet Clearing House (https://www.pch.net/ixp/data), covering 1,327 exchanges and 93,164 recorded member ports, licensed CC BY-NC-SA 3.0.

PeeringDB is the better-known directory and is deliberately not the source here: its acceptable-use policy forbids the bulk storage this needs. The two answer different questions anyway. PeeringDB reports what an operator declares about itself; this reports what PCH has recorded.