Peering‎ > ‎

Peering Policy

Nobis Technology Group, LLC (hereinafter referred to as "Nobis") seeks to interconnect its IP network with other IP networks on a settlement-free basis when such interconnection would provide a tangible benefit to Nobis and its customers, and would be in compliance with the guidelines set forth in this policy. Nobis operates multiple, geographically diverse networks under the Autonomous System Number (ASN) 15003.

Technical Requirements 
  • Traffic Levels: All peers must have a minimum of 100 Mb/s (megabits per second) of peak-hour bi-directional traffic between their network and a single Nobis network that will instead be exchanged under the proposed peering relationship. All peers must agree to direct any traffic destined to Nobis' network via the peering session.
  • BGP: All peers must have the capability to establish a BGP4 session with Nobis over which full routing information about the peer's network will be sent to Nobis.
  • Route Filtering: All peers must implement prefix-based filtering technology to ensure that only IP addresses that they are authorized to use are sent to Nobis. All peers will engage in generally accepted best practices for ensuring that their customers are using only authorized IP address space.
  • Transit Routes: No transit or other 3rd party routes are to be announced over the peering session. All routes exchanged must be the peer's and the peer's customer's routes.
  • Default Routes: No peer may establish a "default route" or "route of last resort" destined for the Nobis network. 
  • Prefix Aggregation: All peers agree to make a good-faith effort to announce the most aggregated route set possible.
  • Internet Routing Registry: It is highly recommend that all peers utilize an Internet Routing Registry (IRR) such as RADB (www.radb.net) for registering route objects associated with their network. This will allow Nobis network administration to easily create and verify configuration information for the peering BGP session.
Operational and Administrative Requirements
  • 24 Hour NOC: All peers must operate a professionally managed Network Operations Center (NOC) or equivalent contact center which opened 24 hours a day, 7 days a week. All peers must provide and maintain accurate telephone and electronic (i.e. e-mail) contact information.
  • Resolution of Issues: All peers must agree to fix or otherwise remedy any issues within a reasonable timeframe. All peers must agree to actively cooperate with Nobis to resolve any security, abuse, or other operational issues.
  • Current or Former Customers: No current Nobis customers, including those of any Nobis brand or subsidiary  are eligible for peering. No former customer of Nobis, including those of any Nobis brand or subsidiary, are eligible for peering within 6 months of the termination of their relationship with Nobis or any Nobis brand or subsidiary. 
General Provisions
  • Trial Period: All connections will be considered "trial connections" for the first 90 days. Nobis reserves the right to suspend or terminate any trial connection at any time, for any reason or for no reason at all, with or without notice to the peer.
  • Right to Suspend or Terminate for Convenience: Either party may choose to suspend or terminate the peering relationship at any time. With the exception of incidents involving security or abuse related matters, both Nobis and the peer must agree to give each other not less than 30 days notice of their intent to suspend or terminate the peering relationship. During incidents involving security or abuse related matters, either Nobis or the peer may temporarily suspend the peering session until such time that the other party can remedy the situation.
  • Right to Terminate due to Traffic Levels: All peering relationships require that peers must have a minimum of 100 Mb/s (megabits per second) of peak-hour bi-directional traffic between their network and Nobis' network that will be instead exchanged under the proposed peering relationship. Should traffic fall below that level for a period of 30 days, Nobis  may terminate the peering relationship upon 15 days notice to the peer.
  • Guidelines Only: The restrictions on peers imposed on this document are to serve only as guidelines for Nobis when deciding whether or not to engage in a peering relationship. Meeting the requirements and compliance with the conditions set forth herein does not necessarily mean that a peer will be accepted. Nobis may decline to enter into a peering relationship with any party for any reason or for no reason at all.
  • Peering Agreement Required: All peers must enter into a Peering Agreement with Nobis before a peering relationship will be established. This agreement may define additional terms not set forth in this document or otherwise disclosed, and may be modified with each peer. A copy of our standard Peering Agreement can be obtained by contacting peering@nobistech.net. 
Peering Application
Any parties wishing to establish a peering relationship with Nobis should complete a Peering Application

Comments