Child pages
  • INX FAQ
Skip to end of metadata
Go to start of metadata



Getting Connected

Q: Who is eligible to connect to the exchanges? 

A: The INXes are 100% community operated, and open to any organisation that has their own Internet number resources (ASN + IPV4/IPV6 address space).  

 

Q: Where and how should I connect?

A: All of the exchanges are multi-site, meaning that you can connect to any one of the locations for that specific exchange, and still get access to all peers, at all locations, for that exchange, with zero additional complexity.  Choosing which site to connect to, should be done on the basis of what makes best sense for your network, or which is likely to be cheaper for you to interconnect at.    

 

Q: What equipment is required for connecting to an INX?

A: You can connect to the INX switch fabric using either a suitable router, or a MetroEthernet service.  You require a router that supports BGP4 since all peering is done using BGP.  It is common to have dozens of BGP sessions with other members at the exchange and your hardware should be powerful enough to handle this, and the related traffic. If you're in doubt, speak to your router vendor, or ask our helpful Ops team.


Q: From whom can I get backhaul links to an INX ?

A: You can approach any licensed ECNS holder to provide you with these services. A number of ISPA’s large and medium members will already have a point-of-presence (PoP) at, or near the INX environments and may be able to provide these services.

For larger capacity circuits it may be feasible to obtain dark fibre pairs or DWDM wavelengths into the INX environment.

 

Q: Can I get wireless access to an INX?

A: Yes, although roof or tower space near the INXs is normally limited and it is preferable to connect to an INX via a fibre based circuit. Ultimately, it would be up to the facility provider to determine the rules and processes for installation of radio equipment.


Q: Who should i contact to get connected? 

A: Our single point of contact is ops @ inx.net.za   

 

Costs

Q: Why is there a port fee for the INXes?   Surely IXP-x is better because it's free? 

A: Aside from the regular operating costs of operating the Exchanges, INX-ZA uses the port fees collected to subsidise many community projects, all geared towards sustaining, and improving the Internet ecosystem in South Africa.  These include the provision of Critical Internet Services (eg. DNS Roots), training and capacity building, building infrastructure to span across a city, and advocacy for a continued open Internet environment in South Africa.  Port fees are set by the community-elected management committee, so, if you think that these fees are erroneous, please step up and volunteer for the committee.  Additionally, If you're a rich for-profit organisation and want to sponsor our work, to help drop/lower port costs, please contact us!

 
Q: What are the port costs? 

A:  Please see the table below.  

Port SizePort FeeISPA member discount
100Mb/sZAR 1,095none
1Gb/sZAR 6,225Up to 60%
10Gb/sZAR 12,450Up to 60%

Members of the South African ISPA are eligible for discounts on all INX ports;  please raise this with our ops team, or the ISPA secretariat.

The INXes have a long history of supporting Internet development, and port fees are generally waived for ports used by Critical Infrastructure (such as DNS Root Servers), and other not-for-profit associations located at an INX.  The community-elected management committee remains responsible for determining which services it is appropriate to have hosted at the INXes, and when port fees should be waived.  

The INX Management committee has waived port fees for DINX.


Q: What about cross-connects charges? 

A:  INX-ZA does not levy cross-connect charges.  Where applicable this is done by the colocation provider.  We've negotiated agreements for zero recurring charges if you connect to the INX fabric at any Internet Solutions, Hetzner, or Liquid Telecoms facility.  Thusfar, the only colocation provider that charges for cross-connects on a recurring basis is Teraco.

LocationSite CodeColocation ProviderOnce-off InstallationMonthly recurring cost
JINXPKLInternet SolutionsZAR 2400waived
SMR*HetznerZAR2400waived
HWHLiquid TelecomsTDBwaived
ISOTeracocolo-setcolo-set


LocationSite CodeColocation ProviderOnce-off InstallationMonthly recurring cost
DINXUMHInternet SolutionsZAR 2400waived
RHVTeracocolo-setcolo-set
LocationSite CodeColocation ProviderOnce-off InstallationMonthly recurring cost
CINXBREInternet SolutionsZAR 2400waived
 DPRLiquid TelecomsTBDwaived

* waived if you are pre-cabled to the MMR


Services

Q: Can I get international bandwidth/transit via an INX?

A: A connection to an INX merely provides you with the opportunity to exchange traffic with the other networks connected to the same INX.  Exactly what traffic you exchange depends on the arrangements you make with those other networks.  Some of the other participants may be willing to provide you with an international transit service. There is nothing in the INX policies preventing a member from offering such a service, but it is not a service that the INX provides.

 

Q: What are some of the value add services that the INX provides?

A: Please see the INX Services page for a non-exhaustive description of the services that you can get access to. 

Hosting equipment

Q: Why can’t I host my server at an INX?

A: INX-ZA is not in the server-hosting business. Most of the INX participants provide hosting services, and INX-ZA does not compete with its membership. Technically, while it may seem appealing to host a server at a central location, there is negligible difference in performance if the server is hosted on the network of a peering participant with a high-speed connection to the INX.  We make exceptions for operators of critical Internet infrastructure, like DNS server operators.

BGP and Peering

Q: Is there a looking glass available? 

A: Yes, INX-ZA operates https://lg.inx.net.za that will show you a unified view across all INXes.  Packet Clearing House operates  https://lg.pch.net that is connected to DINX, JINX and CINX.  Routeviews.org provides similar services for CINX and JINX.

 

Policy

Q: Who sets the rules/policy for the INXes?

A: INX-ZA's Management Committee is in charge of INX policy. This committee is elected by the peering community and is responsible for developing and implementing policy, for the benefit of the peering community at the INXes.  INX-ZA is proud to be 100% community managed.

 

Contact & Administrative 

Q: How do I get hold of someone at the INXs?

A: All correspondence can be directed to ops [at] inx.net.za.  Additionally, we have a public chatroom interface that's available for you to interact with us.


An exchange in other locations

Q: Why isn’t there an INX in location X?

A: INX-ZA is constantly on the look out for additional data centre facilities in order to either expand one of our existing INXs within a particular city or to develop new peering points in other towns and cities to encourage the local exchange of traffic. Please contact us to discuss any opportunities.