PIT AR

Argentina

Ciudad
Buenos Aires

About this IXP

Data last updated noviembre 2025

Capacity at this IXP

930 Gbps

Cumulative port speeds of all IXP members. This shows the potential maximum traffic that can be exchanged at this IXP at one time.

Membership and capacity

The size and strength of an IXP is determined by a combination of how many members it has, and the total capacity. Larger networks tend to bring more capacity, which can benefit all members.

Data for PIT AR as shown in PeeringDB in noviembre 2025

Apr 2024Jul 2024Oct 2024Jan 2025Apr 2025Jul 2025Oct 20250.0 200 400 600 800 0 1 2 3 4
CapacityMembersCapacity (Gbps)Members

Members of this IXP

5

ASNs (autonomous system numbers) are listed in PeeringDB

In the last 12 months

  • ASNs left0
  • New ASNs joined2

Participates in the MANRS IXP program

No

IXPs that join this voluntary program apply a framework of enhanced routing security in peering. It signals an extra commitment to responsible Internet stewardship.

Source: MANRS

RIPE Atlas anchor

Yes

Organizations that run IXPs can host anchors to measure Internet connectivity and traffic. An anchor is a large capacity probe often used by IXPs.

Source: RIPEStat

Member information

Last sync from PeeringDB: noviembre 2025

View this IXP on PeeringDB

Países de registro

A summary of member registrations by country. An IXP with a mixture of international and near-neighbor members can indicate that an IXP is influential, or acts as a hub within its region or sub-region.

  • Chile: 2
  • Argentina: 1
  • Reino Unido: 1
  • Estados Unidos: 1

Types of network at this IXP

The mix of members is an indication of a strength or focus of an IXP.

  • Content: 2
  • Unknown: 1
  • Cable/DSL/ISP: 1
  • Route Server: 1

Members peering at the route server

4 / 5

The route server is a central hub that makes it easier for all networks to peer without having to create individual agreements with other members.

Members using RPKI

4 / 5

members at this IXP use Resource Public Key Infrastructure (RPKI), a security measure that helps ensure traffic is routed correctly. A member is counted as using RPKI if they have at least one valid ROA.

Peering policies of IXP members

OpenUnknownSelectiveNoRestrictive

Members of an IXP can choose how they peer with others. The Internet Society encourages open policies where possible.

Member list for PIT AR

This list uses the data available in PeeringDB, which is based on self-reported data, and was last updated in Pulse noviembre 2025

Nombre AS Number Peering policy RPKI Enabled
CDN77
  • Autonomous system (AS) number: 60068
  • Type of AS: Content
  • Peering policy: Open
  • Port speed: 100 Gbps
  • Does this member peer at the route server?: Yes
  • Country of registration: Reino Unido
  • Total peering locations for this AS: 50
60068 Open Yes
Meta
  • Autonomous system (AS) number: 32934
  • Type of AS: Content
  • Peering policy: Selective
  • Port speed: 200 Gbps
  • Does this member peer at the route server?: No
  • Country of registration: Estados Unidos
  • Total peering locations for this AS: 203
32934 Selective Yes
PIT Argentina - PIT AR Route Servers
  • Autonomous system (AS) number: 61527
  • Type of AS: Route Server
  • Peering policy: Unknown
  • Port speed: 20 Gbps
  • Does this member peer at the route server?: Yes
  • Country of registration: Chile
  • Total peering locations for this AS: 1
61527 Unknown No
PIT Chile - Transit
  • Autonomous system (AS) number: 64112
  • Type of AS:
  • Peering policy: Open
  • Port speed: 10 Gbps
  • Does this member peer at the route server?: Yes
  • Country of registration: Chile
  • Total peering locations for this AS: 4
64112 Open Yes
TELECOM ARGENTINA
  • Autonomous system (AS) number: 7303
  • Type of AS: Cable/DSL/ISP
  • Peering policy: Unknown
  • Port speed: 600 Gbps
  • Does this member peer at the route server?: Yes
  • Country of registration: Argentina
  • Total peering locations for this AS: 2
7303 Unknown Yes