Amsterdam Internet Exchange

From Infogalactic: the planetary knowledge core
Jump to: navigation, search

Lua error in package.lua at line 80: module 'strict' not found.

Amsterdam Internet Exchange
220px
Full name Amsterdam Internet Exchange
Abbreviation AMS-IX
Founded 1997 (unofficially 1994)
Location  Netherlands, Amsterdam
Website www.ams-ix.net
Members 750[1]
Ports 1406[1]
Peers 625[1]
Peak in 4.270 Tb/s[2]
Peak out 4.249 Tb/s[2]
Daily in (avg.) 2.481 Tb/s[2]
Daily out (avg.) 2.481 Tb/s[2]

The Amsterdam Internet Exchange (AMS-IX) is an Internet exchange point situated in Amsterdam, in the Netherlands. AMS-IX started in 1994 and is a fast-growing, non-profit, neutral and independent peering point. The AMS-IX is one of the largest Internet Exchanges in the world.

History

Year Peak traffic
2002 12 Gbit/s[3]
2003 21 Gbit/s[3]
2004 48 Gbit/s[4]
2005 120 Gbit/s[5]
2006 220 Gbit/s[5]
2007 374 Gbit/s[6]
2008 440 Gbit/s[7]
2009 610 Gbit/s
2010 1 Tbit/s[8]
2011 1.2 Tbit/s
2012 2 Tbit/s
2013 2.5 Tbit/s
2014 3.3 Tbit/s[2]
2015 4.2 Tbit/s[2]

In February 1994, a layer 2 shared infrastructure, used between academic institutes, was connected with CERN to exchange traffic. Other internet service providers were allowed to connect and the name AMS-IX was first used. In 1997, the AMS-IX Association was founded by twenty of the connected internet service providers and carriers.[5]

In 2002, the Neutral Internet Exchange was founded as an alternative or backup for the Amsterdam Internet Exchange.[9]

As of 5 January 2011, AMS-IX connected 396 members on 684 ports.[10] The all-time peak of incoming traffic was 1.513 Tbit/s and of outgoing traffic 1.512 Tbit/s compared to 0.833 Tbit/s average incoming and outgoing, in January 2012.[11]

The total amount of data transferred by month was (Avg. incoming and outgoing) 75,940 TB in November 2008. By April 2009, it had grown to 124,550 TB, 64% more traffic in a 5-month period.

These traffic speeds make the Amsterdam Internet Exchange the second largest internet exchange in the world, when measured by number of connected members and by internet traffic, placing it second to the Deutscher Commercial Internet Exchange[12] (traffic).

In September 2013, the board voted to create a legal framework to facilitate an expansion into the United States.[13] An AMS-IX press release said that <templatestyles src="Template:Blockquote/styles.css" />

The chosen structure will need to protect AMS-IX's current operation and the AMS-IX Association's customers and members from commercial, legal, financial and technical risks and, more specifically, from interception activities by US government agencies.[14]

SURFnet, a member of the exchange, had expressed its objection to the proposal, citing the possibility that such interception would be demanded.[15]

An optical fiber photonic switch at the AMS-IX
The AMS-IX core cage at euNetworks

Co-locations

AMS-IX members are able to connect at ten locations, all located within the greater Amsterdam area:[16]

Third-party network transport links also offer access to AMS-IX peering VLAN via "Reseller Program". Under the program, reseller could arrange one physical connection toward AMS-IX platform (now solely a 10G connection, but in prospect of going to 100G), and multiplexes "virtual-link" of other parties that connect to AMS-IX peering VLAN.[17]

Network

The AMS-IX platform is continually evolving due to its rapid growth in traffic and number of connected member ports. Up until end of 2009, it is using a redundant hub-spoke architecture using a core switch and multiple edge switches.[18] This double-star topology brings the advantage of being able to perform maintenance on the network without any impact on customer traffic, and to anticipate on fiber and equipment problems by (automatically) switching to the backup topology as soon as a failure in one of the active components occurs. The active switching topology star is determined by means of the VSRP protocol. This topology is AMS-IX version 3.

However, since 2009; AMS-IX platform has migrated from a pure Layer2 network to a VPLS/MPLS network (using Brocade hardware) in order to cope with future growth (this is AMS-IX version 4).[19]

AMS-IX members connect to the platform with 1, 10, 100 Gbit/s Ethernet connections, or using multiple gigabit or 10 gigabit aggregated ports, utilizing the 802.3ad standard. Gigabit Ethernet and lower speed ports are directly connected to Brocade - Foundry Networks BigIron 15000 or RX-8 network switches. 10 gigabit member ports are connected to Glimmerglass Systems photonic switches which maintain an optical connection to the stub switch on the currently active side of the network, following the VSRP protocol. For each 10-gigabit port there is an active and a backup stub switch, for which BigIron RX-8, RX-16 or NetIron MLX-16 switches are used. The core consists of two Brocade NetIron MLX-32 switches, to which all edge switches are connected using 10 gigabit aggregated connections and WDM technology.

With the new VPLS/MPLS setup; the BigIron RX and legacy BigIron 15000 are no longer in-use. AMS-IX has migrated all the hardware to the MPLS-capable MLX platform. Stub switch is either MLX-8, MLX-16 or MLX-32.

Since May 2011, AMS-IX engineers have started testing 100GE along with LimeLight Network.


Canon of Amsterdam

See also

References

  1. 1.0 1.1 1.2 Lua error in package.lua at line 80: module 'strict' not found.
  2. 2.0 2.1 2.2 2.3 2.4 2.5 Lua error in package.lua at line 80: module 'strict' not found.
  3. 3.0 3.1 Annual Report 2003. Retrieved on 2008-02-10.
  4. Annual Report 2004. Retrieved on 2008-02-10.
  5. 5.0 5.1 5.2 Annual Report 2006. Retrieved on 2008-02-10.
  6. Annual Report 2007. Retrieved on 2008-10-01.
  7. Annual Report 2008. Retrieved on 2009-07-08.
  8. Lua error in package.lua at line 80: module 'strict' not found.
  9. Lua error in package.lua at line 80: module 'strict' not found.
  10. Lua error in package.lua at line 80: module 'strict' not found.
  11. Lua error in package.lua at line 80: module 'strict' not found.
  12. Deutscher Commercial Internet Exchange Traffic. Retrieved on 2010-03-12.
  13. Lua error in package.lua at line 80: module 'strict' not found.
  14. Lua error in package.lua at line 80: module 'strict' not found.
  15. Lua error in package.lua at line 80: module 'strict' not found.
  16. Co-locations, AMS-IX, retrieved on 2014-01-26.
  17. Partnerpage AMS-IX site visited on 26 feb 2015
  18. Lua error in package.lua at line 80: module 'strict' not found.
  19. Lua error in package.lua at line 80: module 'strict' not found.

External links