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.
Sample rows
preview · 8 of 100 rows · all 17 columns| agreement_idstring | interconnect_location_typestring | sla_latency_msfloat | is_activeboolean | interconnect_location_countrystring | local_asninteger | peer_asninteger | peering_typestring | interconnect_location_namestring | interconnect_location_citystring | traffic_volume_gbpsfloat | sla_guaranteed_uptime_percentfloat | sla_packet_loss_percentfloat | dispute_resolution_methodstring | agreement_start_datedate | agreement_end_datedate | notesstring |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| AGMT-20240101-001 | IXP | 2.1 | true | Germany | 64512 | 13335 | settlement-free | DE-CIX Frankfurt | Frankfurt | 45.6 | 99.999 | 0.01 | arbitration | 2023-01-10 | blank | High-volume exchange, peak traffic observed during evenings. |
| AGMT-20240101-002 | private NNI | 6.5 | true | United Kingdom | 64496 | 15169 | paid transit | Equinix LD5 | London | 12.2 | 99.9 | 0.03 | mediation | 2022-11-01 | 2025-11-01 | Transit arrangement includes backup routing. |
| AGMT-20240101-003 | IXP | 3.4 | false | Netherlands | 64501 | 32934 | partial transit | AMS-IX | Amsterdam | 7.8 | 99.98 | 0.02 | court | 2021-08-15 | 2024-08-14 | Agreement ending soon, review for renewal. |
| AGMT-20240101-004 | IXP | 1.9 | true | United Kingdom | 64513 | 8075 | settlement-free | LINX LON1 | London | 22.3 | 99.995 | 0.01 | arbitration | 2023-03-22 | blank | Direct peering for cloud traffic. |
| AGMT-20240101-005 | private NNI | 4.2 | true | USA | 64515 | 16509 | paid transit | Digital Realty NYC | New York | 18.7 | 99.95 | 0.04 | court | 2022-05-30 | 2026-05-29 | Includes DDoS protection clause. |
| AGMT-20240101-006 | IXP | 2.8 | true | Ireland | 64516 | 6939 | settlement-free | INEX | Dublin | 5.1 | 99.9 | 0.05 | mediation | 2023-07-05 | blank | Seasonal traffic spikes observed. |
| AGMT-20240101-007 | private NNI | 5.9 | false | Japan | 64517 | 9002 | partial transit | Equinix TY2 | Tokyo | 2.5 | 99.97 | 0.02 | arbitration | 2021-10-10 | 2024-10-09 | Low utilization periods documented. |
| AGMT-20240101-008 | IXP | 2.4 | true | China | 64518 | 174 | settlement-free | HKIX | Hong Kong | 14.9 | 99.99 | 0.01 | mediation | 2022-04-12 | blank | New route filters deployed. |
| AGMT-20240101-009 | private NNI | 7.3 | false | Australia | 64519 | 4826 | paid transit | Global Switch SY3 | Sydney | 9.3 | 99.96 | 0.05 | court | 2020-12-01 | 2024-12-01 | Pending review of performance metrics. |
| AGMT-20240101-010 | IXP | 2 | true | Sweden | 64520 | 2914 | settlement-free | Netnod Stockholm | Stockholm | 11.5 | 99.995 | 0.01 | arbitration | 2023-09-21 | blank | Peak traffic aligned with local holidays. |
| AGMT-20240101-011 | private NNI | 6.8 | false | Japan | 64521 | 3356 | partial transit | NTT DC Osaka | Osaka | 4.7 | 99.92 | 0.03 | mediation | 2021-03-04 | 2024-03-03 | Renewal discussions underway. |
| AGMT-20240101-012 | IXP | 2.7 | true | Japan | 64522 | 4808 | settlement-free | JPNAP Tokyo | Tokyo | 20.4 | 99.99 | 0.01 | arbitration | 2022-11-18 | blank | Additional capacity provisioned for Olympics. |
| AGMT-20240101-013 | private NNI | 5.4 | true | Singapore | 64523 | 16509 | paid transit | Equinix SG3 | Singapore | 8.8 | 99.95 | 0.04 | court | 2020-02-11 | 2025-02-10 | Transit for business-critical applications. |
| AGMT-20240101-014 | IXP | 2.2 | true | France | 64524 | 13335 | settlement-free | France-IX Paris | Paris | 13.2 | 99.98 | 0.02 | mediation | 2022-07-01 | blank | New route optimizations implemented. |
| AGMT-20240101-015 | private NNI | 3.7 | true | Germany | 64525 | 8075 | paid transit | Interxion FRA6 | Frankfurt | 10.5 | 99.96 | 0.03 | arbitration | 2021-06-17 | 2025-06-16 | Backup path included in service. |
| AGMT-20240101-016 | IXP | 4.1 | false | Netherlands | 64526 | 15169 | partial transit | NL-IX Rotterdam | Rotterdam | 3.3 | 99.97 | 0.02 | mediation | 2020-04-21 | 2024-04-20 | Historical low traffic periods. |
| AGMT-20240101-017 | IXP | 1.5 | true | Switzerland | 64527 | 32934 | settlement-free | SwissIX | Zurich | 7.2 | 99.99 | 0.01 | court | 2023-02-13 | blank | Agreement covers IPv6 prefix exchange. |
| AGMT-20240101-018 | private NNI | 7.2 | true | USA | 64528 | 64510 | paid transit | Equinix MI1 | Miami | 16.5 | 99.94 | 0.04 | arbitration | 2022-09-08 | 2027-09-07 | Includes Latin America traffic. |
| AGMT-20240101-019 | IXP | 3 | false | USA | 64529 | 34347 | partial transit | SIX Seattle | Seattle | 5.6 | 99.98 | 0.03 | mediation | 2021-12-02 | 2024-12-01 | Active during holiday sales season. |
| AGMT-20240101-020 | IXP | 2.3 | true | Italy | 64530 | 5400 | settlement-free | MIX Milan | Milan | 9.9 | 99.99 | 0.01 | arbitration | 2023-06-09 | blank | Sports streaming peaks observed. |
What the 100 rows show
from the 100-row sampleIXP (interconnect location type) stands out: mean sla_
- 68%is_
active = true - 4.8median sla_
latency_ ms - 3peering types
- 3dispute resolution methods
- 64,781median local_
asn - 64,756median peer_
asn
Median 4.8, from 1.5 to 11.5.
- string 8
- integer 2
- float 4
- date 2
- boolean 1
Columns
17 columns in four groups| column | type | description | example |
|---|---|---|---|
| Text 8 columns | |||
agreement_id | string | Unique identifier for the peering or interconnect agreementunique | AGMT-20240101-001 |
peering_type | string | Type of peering arrangementsettlement-free · paid transit · partial transit | settlement-free |
interconnect_location_type | string | Type of interconnect locationIXP · private NNI | IXP |
interconnect_location_name | string | Name of the interconnect location (e.g., IXP name or data center) | DE-CIX Frankfurt |
interconnect_location_city | string | City where the interconnect location is situatedoptional | Frankfurt |
interconnect_location_country | string | Country where the interconnect location is situatedoptional | Germany |
dispute_resolution_method | string | Method or process for resolving disputes (e.g., arbitration, mediation, court)3 methods · optional | arbitration |
notes | string | Additional notes or comments regarding the agreementoptional | Agreement renewal in Q4. |
| Numbers 6 columns | |||
local_asn | integer | Autonomous System Number (ASN) of the local network party to the agreement1 or more | 64512 |
peer_asn | integer | Autonomous System Number (ASN) of the peer network party to the agreement1 or more | 13335 |
traffic_volume_gbps | float | Average traffic volume exchanged at this interconnect (in Gbps)0 or more · optional | 45.6 |
sla_guaranteed_uptime_percent | float | Service Level Agreement guaranteed uptime percentage0 to 100 · optional | 99.999 |
sla_latency_ms | float | Service Level Agreement maximum allowed latency in milliseconds0 or more · optional | 2.1 |
sla_packet_loss_percent | float | Service Level Agreement maximum allowed packet loss percentage0 to 100 · optional | 0.01 |
| Dates and times 2 columns | |||
agreement_start_date | date | Date when the agreement became effective | 2023-01-10 |
agreement_end_date | date | Date when the agreement is set to expire (null if ongoing)optional | 2025-11-01 |
| True or false 1 column | |||
is_active | boolean | Indicates whether the agreement is currently active | true |
Use it for
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.
- Agreements100AGMT-20240101-0012.1IXPAGMT-20240101-0026.5private …AGMT-20240101-0033.4IXP
A software demo
Believable agreements with local_
asn, peer_ asn and peering_ type to fill a screen in front of a buyer.
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.
- 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
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