The only known route limitation I am aware of on a CF org is the route
quota associated with the org. If you type 'cf org [ORG_NAME]' you
should see how many routes are allowed. You can also view quotas directly
using 'cf quotas'. We're running thousands of routes and haven't seen an
issue as long as the route quota is set high enough.

On Wed, Feb 3, 2016 at 11:40 AM, Filip Hanik <fhanik(a)pivotal.io> wrote:

hi Siva,
can't you just register *.uaa.test.com as a route?


https://github.com/cloudfoundry/cf-release/blob/master/templates/cf-jobs.yml#L173-L182



On Wed, Feb 3, 2016 at 10:05 AM, Siva Balan <mailsiva(a)gmail.com> wrote:

Hello,
We have an implementation of UAA using Identity zones where each zone in
UAA is represented by a unique route and this route is bound to that UAA
app in our cloudfoundry implementation. Eg:
If UAA is deployed at uaa.test.com, then the routes for the zones are
represented as:
zone1.uaa.test.com
zone2.uaa.test.com
zone3.uaa.test.com
We have a requirement to test for 10,000 identity zones which translates
to 10,000 routes bound to a single UAA app.
We would like to know if there are any known limitations to the number
of routes that can be created per org or number of routes that can be bound
to a single app.

Thanks
Siva Balan

--
http://www.twitter.com/sivabalans