1. Definition
Remote Peering is a service that allows members not physically located at a RegPEX POP to connect to the RegPEX peering fabric via a GRE tunnel.
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.
2. Service Model
2.1 Connection Method
- Protocol: GRE (Generic Routing Encapsulation) tunnel
- Termination: RegPEX Remote Peering Gateway (RPG) server
- Transport: Member's own internet/MPLS/DIA connection
- Encryption: Optional GRE-over-IPsec (upon member request)
2.2 Supported Speeds
| Remote Port Type | Logical Capacity | Rate Limit |
|---|---|---|
| Remote 1 GE | 1 Gbps | 1 Gbps |
| Remote 10 GE | 10 Gbps | 10 Gbps |
Note: Actual throughput depends on the quality of the member's transport connection.
3. Technical Requirements
3.1 Member Side
- Router with GRE tunnel support (Cisco, Juniper, MikroTik, Linux, etc.)
- Static public IP address (GRE endpoint)
- Sufficient bandwidth on transport connection
- MTU: Tunnel MTU of 1476 bytes due to GRE overhead (or jumbo frame support)
- BGP configuration capability
3.2 RegPEX Side
- IPv4 and IPv6 peering address allocated on the peering VLAN
- Route server access provided
- MAC address limit enforced (1 MAC per tunnel)
- Rate limiting applied (based on selected port type)
4. SLA Differences
Remote peering is subject to different SLA terms compared to physical connections:
| Metric | Physical Peer | Remote Peer |
|---|---|---|
| Uptime Guarantee | 99.95% | 99.5% |
| RegPEX Responsibility | Peering fabric | RPG server and peering fabric only |
| Transport Responsibility | RegPEX (cross-connect) | Member (internet/MPLS) |
| Latency Guarantee | Under 1 ms (same POP) | No guarantee (transport dependent) |
| Credit Policy | Standard SLA | Only for RPG-originated outages |
Important: RegPEX is not responsible for outages, latency, or packet loss on the remote peer's transport connection.
5. Pricing
| Service | Monthly (USD) | Yearly (USD) | Setup (USD) |
|---|---|---|---|
| Remote 1 GE | $200 | $2,160 (10% discount) | $300 |
| Remote 10 GE | $650 | $7,020 (10% discount) | $500 |
Founding member discounts also apply to remote peering services.
6. Acceptable Use
In addition to the standard RegPEX AUP:
- Only peering traffic may be transmitted over the GRE tunnel
- The tunnel may not be transferred to or shared with third parties
- Members must notify RegPEX NOC if their tunnel endpoint IP address changes
- Redundant connections via multiple GRE tunnels are supported (additional charge)
7. Application Process
- Submit a standard membership application
- Select "Remote Peering" as the connection type
- Provide your public IP address and preferred POP
- RegPEX provides GRE tunnel parameters and peering details
- Configure the GRE tunnel on your router
- Connection testing (ping, BGP session verification)
- Go live
8. Termination
- Standard membership termination terms apply
- GRE tunnel is deactivated on the termination date
- Allocated peering IP addresses are released
9. Contact
- Technical Support: noc@regpex.net
- Applications: peering@regpex.net