Peering with Proxility
Proxility maintains a generally open peering policy. Proxility believes that peering is important for the reliability and quality of its network. Peering usually increases redundancy, reduces latency, and thus improves quality for both parties at reduced costs.
Peering policies/guidelines
Proxility maintains a small set of guidelines concerning peering relations. Please note that this are only guidelines, no hard policies.
- We generally peer with anybody who wants to peer with us on any IXP we're present on (Currently, this limits us to AMS-IX).
- We reserve the right to deny peering, or to end an existing peering agreement at any time.
- We will not peer with customers of our members customers, to avoid conflict of interest. We might be willing to peer with our members customers, but this is up to the Proxility member involved.
- We will not pay for peering, we only pay for transit.
- We require a technical contact that is available 24/7 in case of emergencies.
- Peers may not announce our prefixes to another peer, without rewriting the next-hop. Route-servers we might peer with, are an exception to this rule.
- We do not require MD5 checksums on our BGP sessions, but we support it if you prefer or require to use it.
- We do not require a written peering agreement. If you require one, we are willing to sign it, if we can agree with the contents of this agreement.
- We are open for private peering where it makes engineering sense. If you are interested in private peering, please contact peering@proxility.net.
Traffic pattern
Proxility operates a network for its members, which are currently three independent Internet related businesses.
The Proxility network has a balanced traffic pattern. The Proxility network primarily carries the following traffic:
- DSL subscriber lines (primarily bussiness DSL)
- Broadband Fiber-to-the-Home subscribers
- Live event streaming
- Datacenter/colocation services
- Application hosting services
- Webhosting services
Peering details
General details
| Organisation: | Proxility |
|---|---|
| Address: | Turennestraat 33 6221 AR MAASTRICHT The Netherlands |
| AS number: | 43293 |
| AS macro (RIPE): | AS-PROXILITY |
| NOC e-mail: | noc@proxility.net |
| Abuse e-mail: | abuse@proxility.net |
IXP details
| AMS-IX | |
|---|---|
| IPv4 Address: | 195.69.144.182 |
| IPv6 Address: | 2001:7f8:1::A504:3293:1 |
| Location: | TelecityRedbus-2 Amsterdam The Netherlands |
| Connection type: | 1000Base-SX |
Prefix list
| Prefix | Origin ASN |
|---|---|
| 77.93.64.0/19 | 43293 |
Selling us transit
During aquisition, lists of ISPs connected to a particular IXP are commonly a target for sales people trying to sell bandwith to those ISPs.
Proxility has some strict guidelines for buying transit. Proxility does not make the decision to buy transit from you, this decision is being made by the members of the Proxility foundation. Nevertheless, we evaluate our current and future transit needs quite often. If you want to make us an offer, please have a look at the following guidelines:
- Please send all offers to transit@proxility.net.
- Please do not call Proxility for any offers. Proxility is an operations-only organisation.
- We only buy transit from Tier-1 and Tier-2 carriers.
- We focus more on quality than quantity.
- Peering with us before we buy from you is a big plus.
- If you want to make us an offer, please send us pricing information along with it. Initial offers without pricing information will not be considered.
- If you don't get a reaction, this doesn't indicate we're ignoring you. All offers will be included in the next evaluation of our transit needs.