Whether you access content from Palo Alto or Tallahassee, your location should not be a barrier to a fast cloud experience. To provide you with the fastest possible load times, we are always expanding our ZEIT Network. In the last week alone, we announced 5 new regions — DUB1 (Dublin), ARN1 (Stockholm), SYD1 (Sydney), BOM1 (Mumbai), and ICN1 (Seoul).
We are starting this week by announcing another new Origin and CDN region in the United States: CLE1 (Cleveland).

SFOSFO
Connecting...
CLECLE
Connecting...
LHRLHR
Connecting...
SINSIN
Connecting...
IADIAD
Connecting...
GRUGRU
Connecting...
SYDSYD
Connecting...


ZEIT Now CDN latency for some of our regions, from your current location.


Being an Origin region means that we can now run and host your deployments in Cleveland. Since CLE1 is also a CDN node, we can cache your content and make it immediately available across our network, to deliver a faster experience globally.
Combined with SFO1 (San Francisco) and IAD1 (Washington DC), the announcement of CLE1 means that your users in the United States will benefit from significant performance improvements. Specifically, if they access from within or near Cleveland:
  • Full Origin: lightning quick access to content, and greater redundancy
  • Improved Latency: further reduced latency over our previous options
CLE1 (Cleveland)
United States
25ms
IAD1 (Washington DC)
United States
31ms
SFO1 (San Francisco)
United States
68ms

Smaller is better. The average latency (in ms) for a connection to CLE1, IAD1, and SFO1 from an office in Cleveland.

Following this announcement, CLE1 will be made available to all deployments. All your customers in or near Cleveland are already enjoying faster speeds.
The Origin node closest to you will be made your new default region, automatically. For example, if you are deploying from Detroit, which is closer to Cleveland than to San Francisco or Washington DC, your default node will automatically be CLE1.
As always, you retain full control over your Origin regions. If your APIs or datasources are in or near Cleveland, you can explicitly choose to deploy and serve your app from Cleveland:
now --regions cle
To deploy and serve your app from multiple regions, you can specify all of them:
now --regions cle,sfo,sin
The primary use case for --regions is deploying functions close to your datasource. Even if you decide to only deploy to Cleveland, your static assets and dynamic responses will always be cached globally across all CDN regions in our network, ensuring the quickest response time for all of your users.
You can start deploying to CLE1 for all your applications using version 14.2.4 (or newer) of Now CLI.
We are proud to be able to offer a faster web experience to our patrons in and nearby Cleveland, in addition to greater redundancy.
Not only do we want to make a truly global infrastructure available, we also want it to be easily accessible. With our default global CDN, we are enabling every developer to improve the experience for their users with minimal to no configuration.
We welcome your feedback and suggestions on Twitter or over Chat.