Useful Link
About 
Package
Services
Team
Contact
FAQ
Location
The Cloud
Contact
Social Media

Peering policy

Autonomous System Number (ASN): 213434
Contact Email: peering@gltx.org

1. Purpose

This document describes the peering policy for GLTX Microsystems (ASN 213434). Our goal is to establish mutually beneficial interconnections with other networks to optimize routing, reduce latency, and improve resilience for our traffic.

2. Peering Type

GLTX Microsystems are primarily interested in public and private peering at Internet Exchange Points (IXPs) and through direct interconnects where feasible.

3. Peering Requirements

We consider peering requests from networks that meet the following criteria:

  1. ASN Verification: The network must have a valid, registered ASN.
  2. Operational Network: The network must have a stable, operational IP backbone.
  3. Traffic Consideration: We prefer networks that can exchange meaningful traffic. Generally, we expect a minimum traffic level, which can be assessed during initial discussions.
  4. Technical Compatibility: The network must support standard BGP practices, including:
    • Full BGP routing table exchange (IPv4/IPv6) or selective prefixes as agreed.
    • Proper filtering to avoid route leaks or announcements of invalid prefixes.
  5. Routing Policies: The network must respect GLTX Microsystems’ routing policies, including prefix limits, communities, and any agreed route filtering.

4. Peering Setup

  • BGP Session: GLTX requires eBGP sessions for peering, using ASN 213434.
  • Multihop: Allowed only if agreed in advance.
  • IPv4 and IPv6: Both are supported.

5. Traffic Ratios

GLTX Microsystems does not enforce strict traffic ratios, but expects peering to be mutually beneficial. If traffic is heavily asymmetric, we may review the peering agreement.

6. Locations

We currently peer at:

  • Primary Data Centers / IXPs: BGP Exchange GB, LA, and NL

7. Contact

All peering requests should be sent to:

Email: peering@gltx.org
Required information:

  • ASN and network description
  • Locations you can peer
  • IPv4/IPv6 prefixes you plan to announce
  • Traffic expectations

We aim to respond to all peering inquiries within 7 business days.

8. Policy Updates

GLTX Microsystems may revise this peering policy at any time. Updates will be posted publicly on https://gltx.org/peering-policy.