› AS6908 Peering Policy


While Datahop does not require a signed peering agreement with its peers it expects peers to be in line with the following policy:

  • The total peak-time traffic exchange between Datahop and any applicant should exceed 20Mbps. Datahop does not require any particular traffic ratio.
  • The applicant must neither be an existing transit customer of Datahop, nor a downstream customer of a Datahop customer.
  • The applicant must maintain sufficient backbone capacity to exchange traffic without congestion.
  • Hot-potato routing is implied, Datahop does not honour MEDs.
  • The applicant must have consistent route announcements at all peering locations.
  • Datahop will bear the initial cost of the interconnection (cabling), all subsequent costs shall be equally distributed between the applicant and Datahop. Interface costs are solely those of the respective party.
  • Each interconnection between the applicant and Datahop is required to have no less than 100Mbit/s capacity. Multiple interconnects are preferred, the latest list of Datahop PoPs can be found at http://www.as6908.net.
  • The applicant must operate a 24x7x365 NOC which can be contacted via email or telephone. A clear escalation path from this NOC must be defined in order to quickly identify and resolve network problems.
  • The applicant must be able and willing to quickly trace and mitigate ongoing denial of service attacks, and malicious network activities. A qualified engineer must be available within a reasonable timeframe in order to mitigate attacks over any interconnect between Datahop and the applicant.
  • The applicant must not establish a static route, default route (route of last resort), utilise any other means to send traffic over the interconnection for a route that is not advertised over BGP or otherwise abuse the peering relationship. Neither party shall restrict, or otherwise temper with traffic bound to the other party.
  • Applicant must not sell or give next-hop to any 3rd party (i.e. peer must not re-advertise Datahop routes to any peer)
  • Both parties should be willing to register route, route6 and other related objects in an IRR database. These objects should be maintained in order to ensure they are current for the purpose of filtering.
  • Datahop reserve the right to temporarily suspend any or all interconnections with a peer without prior notice in the event that the peer network is causing operational, or material damage to Datahop. Any interconnect suspended in this manner will be restored as soon as both parties are confident that the operational issues are cured and cleared.
  • Datahop reserves the right to terminate any peering at any time with 60 days notice.
  • Datahop reserves the right to refuse peering with any party based on commercial and/or operational reasons.