The Amsterdam Internet Exchange (AMS-IX) is one of the fastest growing Internet Exchanges. Learn more about it in the About AMS-IX section.
The Internet is a worldwide network of networks. These different types of networks are connected together using the Internet protocol (IP). An Internet Exchange is a place where Internet Service Providers (ISPs) can interconnect these independent networks and exchange Internet traffic with each other. This exchanging of national and/or international IP traffic on an Internet Exchange is generally known as ’peering’.
Peering is the exchange of traffic between ISPs. In order to settle the terms to which this exchange takes place, ISPs use peering agreements that often do not include an exchange of money. This helps to reduce the costs of IP Traffic in a significant way. One of the largest costs facing any ISP nowadays are the upstream capacity costs of connections. Peering arrangements at an exchange reduce the need to send IP traffic through a bandwidth upstream provider. One single connection to an exchange point (such as AMS-IX) may reduce the need for multiple connections. Here at AMS-IX, members or customers are easily able to connect up with each other and enjoy the full benefits of peering. Every member or customer at AMS-IX is in the position to peer with any or all other connected ISP's although they are not required to. Each network might have a different peering policy, and this policy may differ depending on the ISP that is negotiating with them.
At present all major Dutch Internet companies and many international ISPs (30 % NL, 70% international) have established connections with AMS-IX. Organisations such as RIPE NCC and NL Domain Registry System have also decided to connect to AMS-IX. A look at the List of Connected Networks page will inform you of who is actually connected to AMS-IX and what their peering policy is or a link to find out more about their policy.
In order to connect to AMS-IX, you must meet the following 4 requirements:
By following the instructions pointed out in the “Connect to AMS-IX” section.
Once you have been approved by the executive board, you will be informed by e-mail.
The AMS-IX NOC works hard to put up connections at the envisioned date you provide us with via the Enty Form. Our engineers will inform the engineers at your side by e-mail on the day you prefer to put the connection up.
Please take a look at the AMS-IX Partner Program for more information about how to join the Partner Program.
AMS-IX does not charge for anything else except the physical connection to the switch. The costs of housing your equipment is a separate concern, which needs to be directed towards the co-location(s) that you choose. If applicable, the costs of the leased line from your network to the chosen co-location(s) is also your responsibility.
No. AMS-IX does not give discounts for multiple connections.
The billing will start on the Production Date*, with a maximum of 30 days after the Assignment Date**.
*Assignment Date - the date when AMS-IX communicates the connection details to Customer.
**Production Date - the date when AMS-IX defines the connection in production in consultation with Customer.
No. Even though AMS-IX works in close partnership with the co-locations, they are still separate entities from AMS-IX. Full details on the co-locations can be found on the co-locations page.
Full details on the co-locations can be found on the colocations page.
The NOC contact page shows clearly who to contact in case of technical issues.
At the AMS-IX switches port security is used to protect its infrastructure against unwanted packets and network loops. It prevents MAC addresses other than the locked MAC address from sending packets onto the AMS-IX platform.
Ingress (from the switch's point of view) traffic with a non-allowed source MAC address will be dropped. If an actual loop is detected (i.e. the source MAC addresses are known on the platform), the port will be physically shut down until the AMS-IX NOC has received confirmation that the loop is gone and the connection has been restored.
When carrying out maintenance that results in a change of MAC address (such as swapping equipment), a new MAC address must be learned or set for the switch port, and the old MAC address must be removed. The AMS-IX NOC will allow extra MAC addresses at the port until the maintenance has been completed. This should be done before starting the maintenance to prevent outages for the customer.
The procedure for this is:
We urgently request that factory-default MAC addresses are used. AMS-IX staff would like to be able to register changes and see the OUIs in order to correlate new issues to certain changes or certain router vendors.
Please send an e-mail to the AMS-IX NOC, whenever you are IPv6 ready. Please include the port numbers (if you have more than one), your AS number and the IPv6 address(es) you plan on using. To determine which IPv6 address(es) to use, see our numbering scheme.
We can also register reverse DNS (PTR) mappings for the IPv6 addresses on the peering LAN. Just include the required mappings in your mail, or request a change from your my.ams-ix.net pages.
Also known as "trunking" (Foundry), "EtherChannel" (Cisco), or the official IEEE term "LACP / 802.3ad". Link aggregation bundles multiple parallel links between a pair of devices forming a single high-performance channel. See also the Link Aggregation page in the Specifications & Descriptions section.
At AMS-IX, link aggregation is available for 1Gb/s and 10Gb/s connections at all locations.
Yes. Members/customers can upgrade their connection(s) or apply for an additional connection at any time. Of course the costs will also differ depending on the upgrade required. See the Services & Pricing page. There are no additional costs applicable for the upgrade itself.
After assignment, AMS-IX allows ten days transition time in order to migrate port traffic from the old connection to the new demanded connection.
AMS-IX keeps three (main) mailing lists:
firstname.lastname@example.org (for members) and email@example.com (for customers) - non-technical lists, include the ACP and the CCP which you initially listed on the AMS-IX Application Form,
firstname.lastname@example.org - technical list, includes the TCP and the NOC that you initially included on the AMS-IX Application form.
You can at any time contact the AMS-IX Office and request a change to any of the AMS-IX mailing lists.
Note that you can have more than one person on any of these lists.
In general, it is rude to send auto-replies in response to messages that are not explicitly addressed to you. This applies to out-of-office assistants as well as ticketing systems.
Please ensure that autoresponders do not send any mail in response to messages sent to a mailing list.
Please configure your software to watch for typical mailing list headers and suppress auto-replies:
List-Id: List description <email@example.com> List-Post: <mailto:firstname.lastname@example.org> Precedence: list Sender: email@example.com
Alternatively, consider subscribing an address that is not connected to an auto-responder.
Failure to comply may result in your subscription being disabled.
As of 2013-12-02 we no longer send periodic mailing list password reminders as to reduce automated email traffic. Should you need help with your username and/or mailing list passwords, please contact the AMS-IX NOC.
Before sending a complaint, please take note of the following:
The AMS-IX systems are part of the 126.96.36.199/21 network. If no system from that subnet appears in the message's Received headers, it did not originate from our systems.
AMS-IX B.V. itself does not knowingly send out unsolicited advertising.
If systems from the abovementioned network (188.8.131.52/21) do show up in the Received headers, there are two possibilities:
1)The header is faked; we can easily check this by checking our mail logs.
2)We have been hacked or used as a relay; in that case, we will take immediate steps to fix the problem.
If you think the above applies to the spam you received, please forward the complete spam message, including all headers to: firstname.lastname@example.org .
Remember to forward the full spam message, not just Outlook's idea of a message!
See the diagram below. Given the likely multiple paths between you and a typical spammer, the largest chance of success is to cut off the spammer at his ISP.
We're not, honestly. Before complaining about a port scan, please take note of the following:
These packets are sent to your system because you are trying to contact another system that is unreachable for some reason. Change your firewall setup to allow these packets. If you are convinced that you didn't initiate a connection to the other (unreachable) system, check your firewall. Some firewalls try to gather information from the RIPE database using an IP address that is unreachable, and hence they receive the (valid) ICMP error code. Otherwise, update your virus checker and run a scan -- you may be harbouring a virus.
If you still think you are being attacked, send a message to email@example.com containing at the very least the following information about the suspicious packets:
If your firewall is capable of creating plain text log files, please attach the log file (or relevant parts thereof) to your mail.
Remember to include the above items in your message! We cannot do anything without this information.