Skip to main content

Peering

Bamboozle Web Services Peering Requirements​

Bamboozle Web Services is willing to peer (IPv4 and IPv6) with networks which are connected to one or more exchange points which we have in common.

If you require a more formal agreement, contact us and we will make arrangements. We will announce to you via BGP4 any routes which we carry and will listen to any routes that you carry. Our peering policy is simple, if you peer with Bamboozle, we expect the following:

  • Only send us traffic that is destined for the prefixes we announce to you. Do not point default at us or use static routes to send us traffic that does not match the routes we announce to you.
  • Bamboozle Web Services will generally announce consistent routes at each exchange point and expects peers to generally do the same.
  • Bamboozle Web Services expects you to peer at all exchange fabrics we have in common. This is to prevent problems for your and our local market customers so that customer traffic does not cross the Pacific or Atlantic twice to return back to the same continent.
  • Bamboozle Web Services sets up IPv6 peering along with IPv4 peering with all networks that run both protocols.

Network Information​

Any network is welcome to contact Bamboozle Web Services via email at [email protected] to discuss peering. Please include your ASN and peering point locations. An up-to-date PeeringDB entry is nearly always required.

General Peering Information
ASNAS200851
AS-SETAS-BAMBOOZLE
Max Prefix IPv4500
Max Prefix IPv6100
Peering PolicyOpen (for both IPv6 and IPv4)

Exchange Point Information​

Bamboozle Web Services strives to provide uncongested bandwidth at all exchange points. All exchange port bandwidth is monitored and kept within acceptable levels.

ExchangeLocationSpeedIPv4IPv6
UAE-IXDubai, United Arab Emirates10G185.1.8.1132001:7f8:73:0:3:1093:0:1
SH-IXDubai, United Arab Emirates10G185.1.15.632001:7f8:7a::200:851:1
VIXVienna, Austria10G193.203.0.502001:7f8:30:0:2:1:20:851
Was this page helpful?