Check Availability MENU
MyOzarks

Peering Guidelines

OzarksGo (AS395662) has a selective peering policy and actively peers with networks that provide or host content.

General requirements

  1. The ISP must be able to interconnect at a peering location shared with the OzarksGo network (AS395662).
  2. All peers must supply a contact that is available on a 24x7 basis, such as a Network Operations Center (NOC) or equivalent.
  3. Neither party shall establish a static route, a route of last resort, or otherwise send traffic to the other party for a route not announced via BGP.
  4. Neither party shall announce to the other the more specific routes of prefixes learned via a third-party transit customer.
  5. Use of the Internet Routing Registry (IRR) is required for prefix filtering. (RADB is preferred)
  6. Peers should provide access to a looking glass or traceroute server to facilitate troubleshooting.
  7. All announcements are to be consistent across all interconnect locations.
  8. OzarksGo reserves the right to suspend peering for an indefinite period of time should any form of network abuse be verified to take place via the peering interconnect such as denial of service attacks (DOS), unsolicited bulk email (SPAM), or setting default-route to OzarksGo.
  9. OzarksGo will not accept any announcement smaller than /24.
  10. Dual stack IPv4 and IPv6 BGP peering is required.
  11. OzarksGo's final decision on peering is based upon a mutually agreeable decision to peer based upon operational needs. If OzarksGo's operational needs cause a peering arrangement to conflict with the best interest of OzarksGo, OzarksGo reserves the right to terminate the peering agreement with reasonable advance notice.
  12. A network that is a customer of AS395662 for any dedicated IP transit services may not simultaneously be a peer.
  13. OzarksGo will send and honor MED attributes by request only.
  14. All potential and current peers must have and maintain valid PeeringDB.com records.
  15. PNI capacity upgrades should occur in a timely manner to ensure a high end-user quality of experience.

Questions?

Contact OzarksGo_Tech@ozarksgo.net for peering inquiries.

Peering Guidelines

OzarksGo (AS395662) has a selective peering policy and actively peers with networks that provide or host content.

General requirements

  1. The ISP must be able to interconnect at a peering location shared with the OzarksGo network (AS395662).
  2. All peers must supply a contact that is available on a 24x7 basis, such as a Network Operations Center (NOC) or equivalent.
  3. Neither party shall establish a static route, a route of last resort, or otherwise send traffic to the other party for a route not announced via BGP.
  4. Neither party shall announce to the other the more specific routes of prefixes learned via a third-party transit customer.
  5. Use of the Internet Routing Registry (IRR) is required for prefix filtering. (RADB is preferred)
  6. Peers should provide access to a looking glass or traceroute server to facilitate troubleshooting.
  7. All announcements are to be consistent across all interconnect locations.
  8. OzarksGo reserves the right to suspend peering for an indefinite period of time should any form of network abuse be verified to take place via the peering interconnect such as denial of service attacks (DOS), unsolicited bulk email (SPAM), or setting default-route to OzarksGo.
  9. OzarksGo will not accept any announcement smaller than /24.
  10. Dual stack IPv4 and IPv6 BGP peering is required.
  11. OzarksGo's final decision on peering is based upon a mutually agreeable decision to peer based upon operational needs. If OzarksGo's operational needs cause a peering arrangement to conflict with the best interest of OzarksGo, OzarksGo reserves the right to terminate the peering agreement with reasonable advance notice.
  12. A network that is a customer of AS395662 for any dedicated IP transit services may not simultaneously be a peer.
  13. OzarksGo will send and honor MED attributes by request only.
  14. All potential and current peers must have and maintain valid PeeringDB.com records.
  15. PNI capacity upgrades should occur in a timely manner to ensure a high end-user quality of experience.

Questions?

Contact OzarksGo_Tech@ozarksgo.net for peering inquiries.

Peering Guidelines

OzarksGo (AS395662) has a selective peering policy and actively peers with networks that provide or host content.

General requirements

  1. The ISP must be able to interconnect at a peering location shared with the OzarksGo network (AS395662).
  2. All peers must supply a contact that is available on a 24x7 basis, such as a Network Operations Center (NOC) or equivalent.
  3. Neither party shall establish a static route, a route of last resort, or otherwise send traffic to the other party for a route not announced via BGP.
  4. Neither party shall announce to the other the more specific routes of prefixes learned via a third-party transit customer.
  5. Use of the Internet Routing Registry (IRR) is required for prefix filtering. (RADB is preferred)
  6. Peers should provide access to a looking glass or traceroute server to facilitate troubleshooting.
  7. All announcements are to be consistent across all interconnect locations.
  8. OzarksGo reserves the right to suspend peering for an indefinite period of time should any form of network abuse be verified to take place via the peering interconnect such as denial of service attacks (DOS), unsolicited bulk email (SPAM), or setting default-route to OzarksGo.
  9. OzarksGo will not accept any announcement smaller than /24.
  10. Dual stack IPv4 and IPv6 BGP peering is required.
  11. OzarksGo's final decision on peering is based upon a mutually agreeable decision to peer based upon operational needs. If OzarksGo's operational needs cause a peering arrangement to conflict with the best interest of OzarksGo, OzarksGo reserves the right to terminate the peering agreement with reasonable advance notice.
  12. A network that is a customer of AS395662 for any dedicated IP transit services may not simultaneously be a peer.
  13. OzarksGo will send and honor MED attributes by request only.
  14. All potential and current peers must have and maintain valid PeeringDB.com records.
  15. PNI capacity upgrades should occur in a timely manner to ensure a high end-user quality of experience.

Questions?

Contact OzarksGo_Tech@ozarksgo.net for peering inquiries.