AS5413 - GX Networks
Peering Information
GX Networks UK Ltd is an International Internet Service Provider based in the United Kingdom. It is focused on providing a high quality, redundant and resilient service to its clients and will enter into a peering relationship if it feels that such a relationship will be to a benefit to GX Networks and its clients.
This policy applies to all requests for settlement-free interconnect with GX Networks either via private peering on dedicated interconnect or via public peering at Internet Exchange Points (IXPs) and should only be taken as a general guide to the approach taken by GX Networks when deciding to peer with another [ Internet ] Autonomous System. GX Networks has no obligations as a result of providing this document. Each request to peer with GX Networks will be considered on a case by case basis. GX Networks may choose not to peer if we receive a route via an existing peering relationship.
GX Networks conducts periodic internal reviews of its Peering Policy to ensure that elegibilty for peering is consistant with its growth. Existing Peers may be asked at times to re-qualify for continued peering.
Role |
Name |
Phone |
Email |
| General Peering Contact | Peering Engineers | peering@as5413.net | |
| Maintenance & Outage Notification/Reporting | NOC | +44 1865 381 647 | noc@gxn.net |
| Co-Ordinator | Steve Colam | steve.colam@eng.gxn.net |
ASN |
export policy (as-set and route-set) |
max prefix |
| AS5413 | AS5413:AS-CUSTOMER AS5413:RS-CUSTOMER | 500 recommended |
Location |
Port |
ipv4 |
ipv6 |
| LINX, London (Telehouse North) | 10GE | 195.66.224.29 | 2001:7F8:4::1525:1/64 |
| LINX, London (Redbus Harbour Exchange) | 10GE (via Redbus Sovereign House) | 195.66.226.29 | 2001:7F8:4:1::1525:1/64 |
| AMS-IX, Amsterdam | 10GE | 195.69.144.95 | 2001:7F8:1::A500:5413:1/64 |
| DE-CIX, Frankfurt | 10GE | 80.81.192.11 | 2001:7F8::1525:0:1/64 |
| LoNAP, London (Redbus Harbour Exchange) | 10GE | 193.203.5.14 | |
| LoNAP, London (Redbus Harbour Exchange) | 1g | 2001:7F8:17::1525:1/64 | |
| LINX PI, London (Telehouse North or Redbus HEX) | 10GE, GigE | private peer | |
| PI, London (Telehouse North/East, Redbus HEX) | 10GE, GigE | private peer |
| * | Each peer must establish and maintain links to facilitate mutually acceptable performance | |
| * | All BGP sessions require MD5 passwords | |
| * | All BGP sessions will be configured with ttl-security where possible | |
| * | Each peer must operate a 24x7 Network Operations Centre or Monitoring Centre or provide a mechanism to report and action faults 24x7 | |
| * | Each peer must set next hop to be itself and must not set route of last resort pointing to GX Networks | |
| * | Each peer shall advertise consistant route announcements at all public peering points | |
| * | Hot-potato routing is implied, (we will choose our exit best for GX Networks, we will not normally honour meds) | |
| * | GX Networks will 'set community none' on all received routes (including routes received with no-export/no-advertise) | |
| * | Each peer with a total minimum busy hour traffic exchange of 100mb shall be present at two or more public peering points and shall assist with quarterly capacity planning reviews to accommodate traffic growth and ensure least latency and packet loss path | |
| * | Willingness to enter into a Bilateral Interconnect Agreement and Non-Disclosure Agreement with GX Networks | |
| * | Each peer will maintain accurate prefix and routing information in a publically accessible Internet Routing Registry (IRR). | |
| * | Each peer and GX Networks shall announce only their infrastructure and own customer routes | |
| * | Each peer shall achieve a minimum busy hour traffic exchange of 50mb |
| * | Each peer must establish and maintain links to facilitate mutually acceptable performance and shall be liable in most cases for half the costs of the interconnect | |
| * | All BGP sessions require MD5 passwords | |
| * | All BGP sessions will be configured with ttl-security where possible | |
| * | Each peer must operate a 24x7 Network Operations Centre or Monitoring Centre or provide a mechanism to report and action faults 24x7 | |
| * | Each peer must set next hop to be itself and must not set a route of last resort pointing to GX Networks | |
| * | Each peer shall advertise consistant route announcements at all public peering points | |
| * | Each peer shall have a total minimum busy hour traffic exchange of 100mb | |
| * | Each peer shall provide a backup session over a public exchange to protect against service interuption on single private interconnect | |
| * | Hot-potato routing is implied, (we will choose our exit best for GX Networks, we will not normally honour meds) | |
| * | GX Networks will 'set community none' on all received routes (including routes received with no-export/no-advertise) | |
| * | Each peer shall assist with quarterly capacity planning reviews to accommodate traffic growth and ensure least latency and packet loss path | |
| * | Willingness to enter into a Bilateral Interconnect Agreement and Non-Disclosure Agreement with GX Networks | |
| * | Each peer will maintain accurate prefix and routing information in a publically accessible Internet Routing Registry (IRR). | |
| * | Each peer and GX Networks shall announce only their infrastructure and own customer routes | |
| * | GX Networks will prefer the private interconnect for best path. GX Networks expects the peer to do the same unless agreed otherwise |
If you wish to peer with GX Networks AS5413, please ensure you can commit to our peering requirements and then complete the Contract Application Form
AS5413 maintains records in peeringdb.com
PLEASE COMPLETE ALL SECTIONS OF THE CONTRACT APPLICATION FORM IN FULL IF YOU WISH TO BE CONSIDERED FOR PEERING WITH GX NETWORKS SOLUTIONS
For any further queries about peering with GX Networks please contact
peering@as5413.net
GX Networks 24x7 NOC is available on +44 1865 381647 or by
e-mailing noc@gxn.net
|
Legal Information |