About UL

  • Business
  • 24x7 Live support backed by our Technocratic Oath
  • Flexible options for managed hardware
  • Variety of business-centric services available
  • Multiple colocation facilities in key markets
  • Best of breed security and redundancy in all of our facilities
  • Blended Transit from multiple Tier-1 bandwidth providers
  • Extensive peering fabric

10 Gb Connectivity

  • San Francisco: 365 Main, 200 Paul
  • San Jose: PAIX, 55 South Market, 11 Great Oaks
  • Los Angeles: One Wilshire, 530 W 6th St.

Peering with UnitedLayer

UnitedLayer (AS23342) encourages settlement-free peering arrangements with other ASNs. If you would like to peer with UnitedLayer, please read the policy section below.

UnitedLayer Peering Locations

UnitedLayer connects at the following public peering fabrics:

  • Equinix Ashburn : 206.223.115.154/24
  • Equinix Chicago : 206.223.119.108/24
  • Equinix San Jose : 206.223.116.45/24
  • Equinix Los Angeles : 206.223.123.108/24
  • Any2 Los Angeles : 206.223.143.17/24
  • SFMIX San Francisco : 206.197.187.3/24

In addition to public peering, UnitedLayer will private peer at:

  • 365 Main / San Francisco
  • 200 Paul / San Francisco
  • 1 Wilshire / Los Angeles
  • 530 West Sixth / Los Angeles

As there are cross-connect and port costs at these locations, private peering will have to be cost justified to establish sessions. Likely, at the minimum, we will need to see at least 20Mbps going over private peering sessions.

UnitedLayer uses AltDB for our AS-SET and PREFIX updates. Our AS-SET is AS-UNITEDLAYER.

Peering Policies

UnitedLayer peers must:

  • Support a Network Operations Center that can escalate to network engineers that can resolve network issues such as peering and abuse in a timely manner
  • Provide enough capacity to the peering fabric to insure no packet loss
  • Only route to address space announced by UnitedLayer. Default or address space outside of our announced prefixes should not be directed toward us
  • Only announce routes owned by the peering partner and its downstream customers. Default, bogon, transit and other routes should not be announced to UnitedLayer
  • Insure that MAX-PREFIX and route filtering is updated through AltDB and RADDb among other DBs
  • Peering partners cannot be a transit customer of UnitedLayer
  • Peers are expected to announce consistent routes at all peering locations. Exceptions may be made at UnitedLayer's discretion for networks using other methods to ensure that traffic goes to the closest site

Meeting the guidelines above for peering with UnitedLayer is not a guarantee that peering will be established. UnitedLayer reserves the right to not grant peering to an applicant for any reason. Additionally, peering connections should be moved to private interconnects where possible when traffic on a peering session exceeds Mb/s on a regular basis. The peer must pay at least half the cost of any private interconnects

UnitedLayer will:

  • do best exit routing
  • not honor or send MEDs
  • not require MD5 passwords for BGP sessions but will be used if requested
  • reserve the right to exchange traffic only from the portion of UnitedLayer's network in that region for peers who peer with UnitedLayer only in a specific region
  • provide timely communications (via a mailing list) on changes to our peering to our peers

Contacting UnitedLayer

Unitedlayer prefers applications for peering via email. You can contact us at peering@unitedlayer.com. For other contact information, please go to our Contact page.