In order to qualify for peering with SquareFlow Global Backbone, the following policies should be met:
- Peering partner must maintain a 24x7 network operations center to escalate issues quickly.
- Peering partner must peer in at least two distinct datacenters, given there is mutual presence.
- Peering partner must exchange traffic at the geographically closest hand-off.
- Peering partner must have an Autonomous System Number assigned by one of the five common Regional Internet Registries.
- Peering partner MUST NOT point a static route, or otherwise force traffic over peering, and strictly follow BGP advertised paths.
Please note that this peering policy is a general guideline, and we still may reserve the right to refuse peering at our sole disrection.
SquareFlow Global Backbone only establishes peering where it makes engineering-wise sense. A minimum traffic volume of 100 Mbit/s should be exchanged.
SquareFlow Global Backbone happily peers privately in one or all of our Points of Presence. A minimum traffic volume of 5000 Mbit/s should be exchanged to discuss private peering options.