1. Definition
Remote Peering is a temporary introductory service that allows members not physically located at a RegPEX POP to connect to the RegPEX peering fabric via a GRE tunnel over their own internet connection.
Remote peers are virtually connected to the RegPEX peering VLAN and have access to the same route server and bilateral peering capabilities as locally connected members.
Important: Remote Peering is not a permanent connection model. It may be used for a maximum of 6 months; migration to Model 1 (Cross-Connect) or Model 2 (Carrier VLAN) is required thereafter. See the Connection Models Policy for full details.
2. Service Model
2.1 Connection Method
- Protocol: GRE (Generic Routing Encapsulation) tunnel — RFC 2784
- Termination: RegPEX Remote Peering Gateway (RPG) — Ankara location
- Transport: Member's own internet connection
- Encryption: Optional GRE-over-IPsec (upon member request)
2.2 Capacity Limit
| Parameter | Value |
|---|---|
| Maximum capacity | 1 Gbps (95th percentile) |
| Rate limiting | Hard limit — traffic above 1 Gbps is policed |
| Tunnel MTU | 1476 bytes (GRE overhead: 24 bytes) |
3. Pricing
| Rate | Monthly Fee |
|---|---|
| Standard | €100/month |
| Founder member (first 10 members) | €75/month |
| Setup | Free |
3.1 Free Trial Period
Approved Remote Peering members are offered a 1-month free trial upon activation.
- The trial period begins on the tunnel activation date.
- The trial period counts towards the 6-month maximum.
- If no notification is given at the end of the trial, the connection is automatically terminated.
4. Technical Requirements
Member side:
- Router with GRE support (Cisco IOS/XE, Juniper Junos, MikroTik, Linux iproute2, FRRouting, etc.)
- Fixed, publicly routable IPv4 address (GRE endpoint)
- Tunnel MTU configured at 1476 bytes or lower
- Transport connection: minimum 100 Mbps, low packet-loss recommended
RegPEX side:
- IPv4 and IPv6 peering addresses allocated on the peering VLAN
- Route server access provided
- 1 MAC address limit per tunnel enforced
- 1 Gbps rate limiting applied
5. SLA
| Metric | Physical Connection | Remote Peering (GRE) |
|---|---|---|
| Uptime guarantee | 99.95% | 99.0% (RPG only) |
| Transport responsibility | RegPEX | Member |
| Latency guarantee | < 1 ms (same POP) | None |
| SLA credit | Standard | RPG-caused outages only |
| Support priority | Standard | Low |
6. Duration and Migration
- Remote Peering may be used for a maximum of 6 months (including the free trial).
- RegPEX sends a written migration notice at month 4.
- At the end of month 6, if the member has not migrated or given notice of withdrawal, the connection is terminated.
- In exceptional circumstances (natural disaster, POP access restrictions, etc.), RegPEX may grant an extension of up to 3 months.
7. Acceptable Use
- Only peering traffic may be transmitted over the GRE tunnel; transit traffic is prohibited.
- The tunnel may not be transferred to or shared with third parties.
- Members must notify RegPEX NOC before changing their tunnel endpoint IP address.
- Use of more than one MAC address requires prior approval.
8. Application Process
- Select "Remote Peering (GRE)" in the membership application
- Provide your GRE endpoint public IP address and preferred POP
- RegPEX reviews and approves the application
- Upon approval, RPG parameters are provided (RPG IP, tunnel key, peering IP)
- Configure the GRE tunnel on your router
- Connectivity test (ping, MTU check)
- BGP configuration and go-live — 1-month free trial begins
9. Termination
- Termination requires at least 30 days' written notice.
- The GRE tunnel is deactivated on the termination date.
- Allocated peering IP addresses are released.
10. Contact
- Applications: peering@regpex.tr
- NOC: noc@regpex.tr