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.

BGP Community Policy

Receivable Communities

Customers may influence UL routing policies by a number of community tags which may be set on routes which they announce. These tags can control the propagation of routes, adjust the localpref assigned to them, and even null route traffic.

Announced Communities

All routes announced to customers are tagged with the following information: 23342:TCRI

  • T The type of relationship that the route was learned through.
  • C The continent where the route was learned.
  • R The region where the route was learned, if in the US.
  • I Internal usage only.

IRR Filtering

All customers announcements are filtered against Internet Routing Registry (IRR) databases. BGP speaking customers will be expected to maintain current and correct IRR entries.

All UL announcements will be recorded under the as-set AS-UNITEDLAYER.

Receivable UL Communities

  • 23342:1 - Prepend 23342 to Route
  • 23342:2 - Prepend 23342 23342 to Route
  • 23342:3 - Prepend 23342 23342 23342 to Route
  • 23342:510 - Export to Peers Only
  • 23342:530 - Export to Transits, Peers and Customers
  • 23342:530 - Export to Transits, Peers and Customers (prepended in LAX)
  • 23342:555 - BLACKHOLE
  • 23342:666 - NO EXPORT
  • 23342:777 - Do not Export to Transits
  • 23342:888 - Do not Export to Peers
  • 23342:999 - Do not Export to Customers