RegPEX Membership Agreement
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
| Term | Definition |
|---|---|
| RegPEX | Regional Peering Exchange Internet Exchange Point service |
| Member | Legal or natural person connecting to RegPEX infrastructure and receiving peering services |
| POP | Point of Presence locations where RegPEX provides services |
| Peering Port | Physical or virtual port through which the Member connects to the RegPEX peering fabric |
| Route Server | BGP route server infrastructure operated by RegPEX |
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:
- Completion of the online application form
- Technical pre-assessment (ASN validation, prefix verification)
- Approval by RegPEX technical team
- Signing of the membership agreement
- Port allocation and connection setup
- BGP session configuration and testing
- 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
- 24/7 NOC — Around-the-clock network operations centre support
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
- Invoices are issued monthly or annually (annual payment entitles the Member to a 10% discount)
- Payment is due within 30 days of the invoice date
- 60-day warning — Non-payment beyond 60 days may result in a written warning and service restriction
- 90-day port disable — Non-payment beyond 90 days may result in port disconnection
- All prices are exclusive of VAT (or applicable local taxes)
5. Term and Termination
5.1 Term
- The agreement is valid for an initial term of one (1) year from the effective date
- The term auto-renews for successive one-year periods unless terminated
5.2 Termination by Member
- Minimum 30 days written notice required (email is sufficient)
- All fees accrued up to the termination date must be paid
5.3 Termination by RegPEX
RegPEX may terminate membership in the following circumstances:
- Policy violation — After written warning and 15 days to rectify, if not corrected
- Non-payment — Failure to pay for 90 days or more
- 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.
| Details | |
|---|---|
| On behalf of RegPEX | _________________________ |
| Date | _________________________ |
| On behalf of Member | _________________________ |
| Member Organisation | _________________________ |
| Date | _________________________ |