, we want to make the cloud accessible to everyone, everywhere.
Whether you live in Jakarta or Honolulu, your location should not affect your cloud experience.
We are continually expanding our ZEIT Network to include new regions — just last week, we added
Today, we are adding another Origin and CDN region in Asia: ICN1 (Seoul, South Korea).
SFOConnecting... LHRConnecting... HNDConnecting... ICNConnecting... IADConnecting... GRUConnecting...
ZEIT Now CDN latency for some of our regions, from your current location.
means that we can now run and host your deployments in Seoul.
is also a CDN node
, we can cache your content and immediately make it available
across our network, to deliver a faster experience globally.
Combined with HND1 (Tokyo)
and SIN1 (Singapore)
the announcement of ICN1 means that our users in Asia
will benefit from significant performance improvements. Specifically, if you
access from within or near Seoul:
- Full Origin: lightning quick access to content, and greater redundancy
- Improved Latency: over 5x improvement over our previous options
Smaller is better. The average latency (in ms) for a connection to ICN1, HND1, and SIN1 from an office connection in Seoul.
Following this announcement, ICN1
will be made available to
all deployments. All your customers in or near Seoul are already enjoying faster speeds
The Origin node geographically closest to you will be made your new default region, automatically.
For example, if you are deploying from Beijing, which is closer to Seoul
than to Tokyo or Singapore, your default node will automatically be ICN1.
As always, you retain full control over your Origin regions. If your APIs
or datasources are in or near Seoul, you can choose to deploy and serve your app from Seoul:
now --regions icn
To deploy and serve your app from multiple regions, you can specify all of them:
now --regions icn,sfo,cdg
The primary use case for
--regions is deploying functions close to your datasource.
Even if you decide to only deploy to Seoul, 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 ICN1 for all your applications using version
(or newer) of Now CLI
. For more information
on scaling, refer to our documentation
The introduction of ICN1 increases our coverage within Asia. Along with greater redundancy,
it enables us to make the web experience better for our patrons in the region.
By adding more regions to our network, we are able to make the web experience faster and more reliable for Now users everywhere.
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 without much configuration.
We welcome your feedback and suggestions on Twitter
or over Chat