Pre-launch Switching fabric build in progress ASN AS-TBD Fabric MTU 9000 PeeringDB ix/TBD
GLIXGREAT LAKES INTERNET EXCHANGE
Request a port

GLIX/Peering fabric/Member matrix

Interconnect matrix

Participant directory

Every autonomous system interconnecting across the neutral GLIX switching fabric. All participants are expected to follow MANRS routing practice, publish valid RPKI and IRR objects, and deliver dual-stack.

The exchange has not turned up its first production port. The table below is the live structure of the directory with three example rows so the filters can be exercised; replace the rows in src/pages/participants.html as members join.

Connected networks

TBD

Verified ASNs

Provisioned capacity

TBD

Aggregate

Route server ratio

TBD

Multilateral participation

IPv6 dual stack

100%

Required of every participant

Redundant route server cluster

RPKI strict · RFC 7947 / 7948

Primary

Hostname
rs1.greatlakes-ix.net
Daemon
TBD
IPv4 session
TBD
IPv6 session
TBD
Colocation
TBD
Filtering
IRR aut-num plus RPKI

Secondary

Hostname
rs2.greatlakes-ix.net
Daemon
TBD
IPv4 session
TBD
IPv6 session
TBD
Colocation
TBD
Filtering
Maximum prefix plus RPKI strict
Two geographically separated servers on different BGP daemons, so an implementation bug cannot take both down. Route server guide →

Member matrix

Filter and export run in your browser
NetworkASNPort capacity IPv4IPv6 Route serverPolicyFacility
Example participantRegional service provider AS-TBD100GE TBDTBD RS1 + RS2 Open TBD
Example participantResearch and education network AS-TBD10GE TBDTBD RS1 + RS2 Open TBD
Example participantContent delivery network AS-TBD400GE TBDTBD RS1 + RS2 Selective TBD

Showing all 3 listed networks

Fabric MTU 9000 bytes PeeringDB record ↗

Joining the directory

  • Register your network in PeeringDB and keep the record current.
  • Publish route and route6 objects in a supported IRR, and sign ROAs for every prefix.
  • Maintain a reachable 24 hour NOC contact for the peering fabric.
  • Announce a consistent prefix set on both route servers and any bilateral sessions.

Port standards and quarantine

  • One MAC address per allocated port on the switching fabric.
  • Broadcast, unknown unicast, and multicast traffic is storm policed per interface.
  • New ports serve a quarantine VLAN period before production insertion.
  • Full detail lives on the technical specifications page.