RegPEX Membership Agreement

Binding text: The binding text between the parties is the signed RegPEX Participation Agreement and its Annexes (Annex 1–7; fees in Annex 5). This page is a general summary; in case of conflict the signed agreement prevails.

Memorandum of Understanding (MoU)

This agreement governs the rights, obligations, and terms between RegPEX (Regional Peering Exchange) and the party ("Member") receiving IX membership services.

1. Definitions

2. Membership Requirements

2.1 Prerequisites

To become a member, the following conditions must be met:

• Possession of a valid ASN (Autonomous System Number)
• Physical connectivity capability at least one RegPEX POP location
• PeeringDB record (existing or created during the application process)
• Equipment compliant with RegPEX technical requirements
• Acceptance of this agreement and all RegPEX policies

2.2 Application Process

The membership application follows these steps:

1. Completion of the online application form
2. Technical pre-assessment (ASN validation, prefix verification)
3. Approval by RegPEX technical team
4. Signing of the membership agreement
5. Port allocation and connection setup
6. BGP session configuration and testing
7. Go-live

The application process is normally completed within 10 business days.

3. Service Scope

3.1 Services Provided by RegPEX

• L2 connectivity — Layer 2 connection over the peering VLAN
• IPv4/IPv6 peering addresses — Allocation of peering address space
• Route server — Access to BIRD2-based route servers with RPKI and IRRDB filtering
• Looking Glass — Access to RegPEX looking glass for troubleshooting
• Member portal — Traffic statistics, peering matrix, and operational tools
• PeeringDB integration — RegPEX maintains and integrates with PeeringDB
• NOC — business-hours NOC, out-of-hours on-call engineer

3.2 Member Responsibilities

• All equipment and connection costs on the Member's side
• BGP configuration and maintenance
• Cross-connect ordering and fees (to the POP operator)
• Keeping PeeringDB information up to date
• Compliance with RegPEX policies

4. Pricing

4.1 Reference to Pricing Policy

Current pricing and fee structures are detailed in the RegPEX Pricing Policy document. Members are bound by the pricing in effect at the time of their membership commencement and any subsequent amendments as published.

4.2 Payment Terms

• Port fee and capacity fee are invoiced quarterly in advance, at the start of each calendar quarter (1 January, 1 April, 1 July, 1 October); the first invoice is pro-rated from activation to the end of that quarter
• Payment is due within 15 days of the invoice date; default interest applies to late payments
• Overdue payments are notified in writing; 15 days after notice the port may be temporarily disabled
• All prices are exclusive of VAT (or applicable local taxes)
• Amounts appear only on the Pricing page and in the Annex 5 Tariff Schedule; no annual-payment discount applies

5. Term and Termination

5.1 Term

• The agreement is open-ended; the capacity defined on a port is committed in 12-month periods
• Capacity renews for successive 12-month periods (Annex 5, section 5)

5.2 Termination or Capacity Reduction by Member

• Written notice of at least 3 months before the end of the current capacity period is required (email is sufficient); notice takes effect at the end of the period
• There is no minimum port term, but a port cannot be closed and capacity cannot be reduced within a capacity period; fees accrue until then
• The no-compensation termination rights stated in Annex 5 (tariff changes, incentive terms) remain reserved

5.3 Termination by RegPEX

RegPEX may terminate membership in the following circumstances:

• Policy violation — After written warning, if not remedied within a reasonable cure period
• Non-payment — If no settlement is reached 30 days after the port is closed (Annex 5, section 6.5)
• Security threats — Immediate termination in case of serious threats to network security

5.4 Effect of Termination

• Member IP addresses and port allocation are revoked
• Member is responsible for removal of their equipment and cross-connects
• All financial obligations up to the termination date remain in effect

6. Liability Limits

• As-is service — RegPEX provides peering services on an "as-is" basis
• No liability for bilateral agreements — RegPEX is not responsible for peering arrangements between members
• Force majeure — RegPEX is not liable for service interruptions due to force majeure (natural disasters, war, government action, etc.)
• Maximum liability — RegPEX's total liability is limited to an amount equal to 12 months of fees paid by the Member in the preceding year

7. Confidentiality

• Traffic data — Member traffic data is kept confidential and is not shared with third parties
• Aggregate statistics — Aggregate traffic statistics may be published anonymously
• Member list — Member list and ASN information are public (via PeeringDB)
• Personal data — Personal data is processed in accordance with applicable data protection law (including KVKK where applicable). See the RegPEX Privacy Policy for details.

8. Dispute Resolution

• Negotiation first — The parties shall endeavour to resolve disputes through good-faith negotiation
• Jurisdiction — Ankara Courts and Execution Offices shall have exclusive jurisdiction over unresolved disputes
• Governing law — This agreement is governed by Turkish law

9. Signatures

This agreement enters into force upon signature by both parties.