INX – ZA update Riaan Vos
INX-ZA 100% Uptime. 100% community driven. JINX was started in 1996 with just 4 ISPs passing 256kb/s between them, in a small single cabinet in Rosebank JNB. It was agreed at the time that the most responsible party to manage this was the then fledgling Internet Service Provider’s Assocation - ISPA - which has continued to manage since inception. CINX (Cape Town) was started 1 few months later, and ran for 3 years before shutting down - it’s since renewed (since 2009) and now passes the second most traffic on the continent. Although the exchange has moved two times, and is scheduled for another move in a few months, INX has had ZERO unplanned outages. Although ISPA “manages” the IX, the policies are set by ISPA members through the INX-wg. The INX-wg sets policy for all three IXes under ISPA’s management.
INX Multisite What is INX multisite? Traffic stats are from 14 Feb - so that’s why the peak is not visible here. However, the point of the graph was to illustrate the dip in day / night traffic when business + most people go to bed. The rapid drop shows that most traffic is indeed “local” to ZA which is great for the local peering environment.
INX Multisite JINX Traffic stats are from 14 Feb - so that’s why the peak is not visible here. However, the point of the graph was to illustrate the dip in day / night traffic when business + most people go to bed. The rapid drop shows that most traffic is indeed “local” to ZA which is great for the local peering environment.
INX Multisite DINX Traffic stats are from 14 Feb - so that’s why the peak is not visible here. However, the point of the graph was to illustrate the dip in day / night traffic when business + most people go to bed. The rapid drop shows that most traffic is indeed “local” to ZA which is great for the local peering environment.
INX Multisite CINX Traffic stats are from 14 Feb - so that’s why the peak is not visible here. However, the point of the graph was to illustrate the dip in day / night traffic when business + most people go to bed. The rapid drop shows that most traffic is indeed “local” to ZA which is great for the local peering environment.
Multisite experience Not all DCs are created equally: Some are easier to work with. Cross-connect prices differ. Some statistics about the IX. ISPA hired it’s first full-time employee - Nishal Goburdhan - in Aug 2012. Up until then work was done by volunteers. Big plans in 2013 to push regional connectivity and distribute the IX to make it easier for peers to get connected.
Multisite experience (2) Some are happy to have INX in DC. Some do charge a co-location fee. Some statistics about the IX. ISPA hired it’s first full-time employee - Nishal Goburdhan - in Aug 2012. Up until then work was done by volunteers. Big plans in 2013 to push regional connectivity and distribute the IX to make it easier for peers to get connected.
Multisite experience (3) Connecting the sites: Bandwidth is still expensive. Covered by portion of portfees. Some statistics about the IX. ISPA hired it’s first full-time employee - Nishal Goburdhan - in Aug 2012. Up until then work was done by volunteers. Big plans in 2013 to push regional connectivity and distribute the IX to make it easier for peers to get connected.
Initiatives Training workshops planned for JHB, CPT and DBN. Automating Route server filtering. Some statistics about the IX. ISPA hired it’s first full-time employee - Nishal Goburdhan - in Aug 2012. Up until then work was done by volunteers. Big plans in 2013 to push regional connectivity and distribute the IX to make it easier for peers to get connected.
http://www.ispa.org.za INX_ZA Go on...tweet us. You know you want to ... http://www.ispa.org.za INX_ZA