NetSapiens (SNAPaccel) Peering Policy

Welcome to SNAPaccel's next generation peering information.

SNAPaccel 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 SNAPaccel, 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.
  • SNAPaccel 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.
  • SNAPaccel 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 US, Asia and Europe at the same locations as SNAPaccel you must peer with SNAPaccel at all those locations. This is to prevent problems for your and our US and European customers so that customer traffic does not cross the Pacific or Atlantic twice to return back to the same continent.
  • SNAPaccel is dual-stacked in every one of our pops and will IPv6 along with IPv4 peer with all networks that run both protocols.

Network Information (Registered at PeeringDB and RADb)

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

Repository group
AS 397494
Max Prefix:
IPv4/IPv6: 40/12
Peering Information
Peering Policy
Open (for both IPv6 & IPv4)
Peerin Contact Information