peering

requirements

• a publicly routable and visible unique asn

• network router capable of running bgp

• complete, updated, and accurate peeringdb profile

• noc contact provided at the time of session establishment

• peering partner must adhere to the technical requirements of each applicable internet exchange

• only send traffic destined for prefixes announced by andrewnet or downstreams of andrewnet

• not point a default route at andrewnet or use static routes that were not authorized in writing

additionally, we may:

• change our peering policy at any time

• approve or deny a peering request at any time for any reason

• withdraw prefixes from sessions without prior notice

• terminate any peering at any time without prior notice