Peering and Interconnect Agreements

This dataset provides a comprehensive record of peering and interconnect agreements between network operators, detailing peer AS numbers, peering types, interconnect locations, traffic volumes, SLA parameters, and dispute resolution methods. It is ideal for analyzing network interconnection strategies, monitoring SLA compliance, and supporting peering policy decisions in the telecommunications industry.

  • last updated 1 Nov 2025
  • by GoMask
The brief that made it

Analyzing and optimizing network peering strategies

Sample rows

preview · 8 of 100 rows · all 17 columns
agreement_idstringinterconnect_location_typestringsla_latency_msfloatis_activebooleaninterconnect_location_countrystringlocal_asnintegerpeer_asnintegerpeering_typestringinterconnect_location_namestringinterconnect_location_citystringtraffic_volume_gbpsfloatsla_guaranteed_uptime_percentfloatsla_packet_loss_percentfloatdispute_resolution_methodstringagreement_start_datedateagreement_end_datedatenotesstring
AGMT-20240101-001IXP2.1trueGermany6451213335settlement-freeDE-CIX FrankfurtFrankfurt45.699.9990.01arbitration2023-01-10blankHigh-volume exchange, peak traffic observed during evenings.
AGMT-20240101-002private NNI6.5trueUnited Kingdom6449615169paid transitEquinix LD5London12.299.90.03mediation2022-11-012025-11-01Transit arrangement includes backup routing.
AGMT-20240101-003IXP3.4falseNetherlands6450132934partial transitAMS-IXAmsterdam7.899.980.02court2021-08-152024-08-14Agreement ending soon, review for renewal.
AGMT-20240101-004IXP1.9trueUnited Kingdom645138075settlement-freeLINX LON1London22.399.9950.01arbitration2023-03-22blankDirect peering for cloud traffic.
AGMT-20240101-005private NNI4.2trueUSA6451516509paid transitDigital Realty NYCNew York18.799.950.04court2022-05-302026-05-29Includes DDoS protection clause.
AGMT-20240101-006IXP2.8trueIreland645166939settlement-freeINEXDublin5.199.90.05mediation2023-07-05blankSeasonal traffic spikes observed.
AGMT-20240101-007private NNI5.9falseJapan645179002partial transitEquinix TY2Tokyo2.599.970.02arbitration2021-10-102024-10-09Low utilization periods documented.
AGMT-20240101-008IXP2.4trueChina64518174settlement-freeHKIXHong Kong14.999.990.01mediation2022-04-12blankNew route filters deployed.

What the 100 rows show

from the 100-row sample

IXP (interconnect location type) stands out: mean sla_latency_ms is 3.6, against 7.5 for the rest.

  • 68%is_active = true
  • 4.8median sla_latency_ms
  • 3peering types
  • 3dispute resolution methods
  • 64,781median local_asn
  • 64,756median peer_asn
Mean sla_latency_ms by interconnect_location_type100 rows
0483.6IXP54 rows7.5private NNI46 rows
sla_latency_ms100 rows, in bands of 2
0204033132151180612sla_latency_ms →

Median 4.8, from 1.5 to 11.5.

interconnect_location_country100 rows · top 10 of 32 values
  1. USA14
  2. Japan8
  3. Germany7
  4. Singapore6
  5. France5
  6. Netherlands4
  7. Ireland4
  8. Australia4
  9. Sweden4
  10. United Kingdom3
17 columns by typefrom the column list below
  • string 8
  • integer 2
  • float 4
  • date 2
  • boolean 1

Columns

17 columns in four groups
blueprint · 17 columns
columntypedescriptionexample
Text 8 columns
agreement_idstringUnique identifier for the peering or interconnect agreementuniqueAGMT-20240101-001
peering_typestringType of peering arrangementsettlement-free · paid transit · partial transitsettlement-free
interconnect_location_typestringType of interconnect locationIXP · private NNIIXP
interconnect_location_namestringName of the interconnect location (e.g., IXP name or data center)DE-CIX Frankfurt
interconnect_location_citystringCity where the interconnect location is situatedoptionalFrankfurt
interconnect_location_countrystringCountry where the interconnect location is situatedoptionalGermany
dispute_resolution_methodstringMethod or process for resolving disputes (e.g., arbitration, mediation, court)3 methods · optionalarbitration
notesstringAdditional notes or comments regarding the agreementoptionalAgreement renewal in Q4.
Numbers 6 columns
local_asnintegerAutonomous System Number (ASN) of the local network party to the agreement1 or more64512
peer_asnintegerAutonomous System Number (ASN) of the peer network party to the agreement1 or more13335
traffic_volume_gbpsfloatAverage traffic volume exchanged at this interconnect (in Gbps)0 or more · optional45.6
sla_guaranteed_uptime_percentfloatService Level Agreement guaranteed uptime percentage0 to 100 · optional99.999
sla_latency_msfloatService Level Agreement maximum allowed latency in milliseconds0 or more · optional2.1
sla_packet_loss_percentfloatService Level Agreement maximum allowed packet loss percentage0 to 100 · optional0.01
Dates and times 2 columns
agreement_start_datedateDate when the agreement became effective2023-01-10
agreement_end_datedateDate when the agreement is set to expire (null if ongoing)optional2025-11-01
True or false 1 column
is_activebooleanIndicates whether the agreement is currently activetrue

Use it for

  • is active68%68 of 100 rowsmean sla latency ms b…3.6IXP7.5privat…

    A telecommunications dashboard

    The is_active rate, sla_latency_ms by interconnect_location_type and a breakdown of interconnect_location_country. Excel, Power BI or Tableau.

  • Why do the 54 IXP rows have a mean sla_latency_ms of 3.6?

    A root-cause class exercise

    Hand out the rows and one question. The answer is in the data, not in the brief.

  • A software demo

    Believable agreements with local_asn, peer_asn and peering_type to fill a screen in front of a buyer.

Not quite right?

Make it yours.

Same 17 columns, your size and your rules. See 20 rows before you pay.

Preview 20 rows free

1,000 rows: $1.99 · 10,000: $12.99One-time. No subscription. All prices

This dataset100 rows17 columns
Yours1,000 rows17 columnsinterconnect_location_type: UK only

blueprint · peering-and-interconnect-agreements

Behind this dataset

Same schema. As many rows as you need.

These 100 rows came out of a blueprint — 17 columns with generation rules behind each one. Open it in Data Factory to retune a column, add your own, wire in foreign keys, and run it at the size you actually need.

Rules it was built with
  • Peer AS number and network name
  • Peering type: settlement-free (no payment), paid transit, partial transit
  • Interconnect location: internet exchange point (IXP) or private NNI
  • IXP names: DE-CIX, AMS-IX, LINX, Equinix IX, etc.
  • Traffic volumes: inbound Gbps, outbound Gbps, total exchanged
  • Peering ratio: traffic balance (inbound/outbound), typically 1.5:1 or better
  • Port capacity: 10GE, 100GE, 400GE interconnect links
  • SLA: packet loss, latency, availability commitments
Rows
Open the blueprint in Data Factory

1 credit per row. New accounts start with 25 free credits.

Exports
CSV, JSON, JSONL, Parquet, SQL, Excel, TSV, XML
Licence
yours to use, including commercially
API slug
peering-and-interconnect-agreements

What should your data show?

Preview 20 rows free
No signup. No card.