Summary of our Peering policies

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. We understand that due to submarine cable faults or other reasons you may need to temporarily vary your announcements.

  • Bamboozle Web Services expects you to peer at all exchange fabrics we have in common if we peer with you via public exchanges or all facilities we have in common if we peer via private interconnect with you. In other words, if you are peering in the North America, South America, Europe, Middle East, Africa, Asia, or Oceania at the same locations as Bamboozle you must peer with Bamboozle at all those locations. 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 (Registered at PeeringDB and RADb)

Any network is welcome to contact Bamboozle Web Servicesvia email at to discuss peering. Please include your ASN and peering point locations. An up-to-date peeringDB entry is nearly always required.

Bamboozle Web Services 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. The network is upgraded constantly and in some case very large peers are moved onto private peering sessions.

When requesting peering with Bamboozle Web Services at multiple locations, we also request that backbone operators provide enough backhaul bandwidth to handle their peering bandwidth needs.

Check back regularly for additional peering exchanges

Last updated


Copyright © 2024 Bamboozle Web Services, Inc. All Rights Reserved.