GLIX/Contact
Get connected
Request a port or reach the NOC
This site is deliberately static, so there is no contact form to submit and nothing collecting your details in a database. Email reaches the engineers directly.
Peering and port requests
New ports, quotations, LOA and CFA issuance, facility questions, and anything about joining the exchange.
Network operations
Fabric faults, port down, optical alarms, route server issues, and maintenance notifications.
- NOC phone
- +1 TBD
- Escalation
- TBD
What to include in a port request
- Your ASN and the organization name as it should appear in the directory.
- The facility you want to connect at, and your cage or suite there.
- Requested port speed and whether you want link aggregation.
- Whether you need a 9000 byte MTU from the start.
- Your PeeringDB record so the NOC can verify contacts and prefix counts.
- The IRR source and AS-SET your prefix filters should be generated from.
- A technical contact and a 24 hour NOC contact.
- Your peering policy: open, selective, or restrictive.
Reporting a fault
Put your ASN and port in the subject line. Include the time the problem started with a time zone, what you observe from your side, and whether the issue affects one peer or every peer on the fabric. If a BGP session is down, say which route server and whether the interface is up.
Mailing list and notices
Maintenance windows, route server changes, and fabric notices are announced to the participant mailing list. Subscription details are TBD and every technical contact on file is added at turn-up.
Exchange details
- Exchange ASN
- AS-TBD
- PeeringDB
- TBD
- Fabric MTU
- 9000 bytes available, 1500 default
- Peering policy
- Open on the route servers
- Legal entity
- TBD
- Registered address
- TBD