The network
Ten regions. Every project on all of them.
This page is live: region status and machine uptime come from the edges themselves, checked from your browser right now.
| sfo.surge.sh | US, San Francisco | — | ||
| jfk.surge.sh | US, New York | — | ||
| yyz.surge.sh | CA, Toronto | — | ||
| lhr.surge.sh | GB, London | — | ||
| ams.surge.sh | NL, Amsterdam | — | ||
| fra.surge.sh | DE, Frankfurt | — | ||
| blr.surge.sh | IN, Bangalore | — | ||
| sgp.surge.sh | SG, Singapore | — | ||
| nrt.surge.sh | JP, Tokyo | — | ||
| syd.surge.sh | AU, Sydney | — |
Refreshed every minute. The same data drives the region table in every surge publish.
Publishing, right now
Every publish, as it happens.
Anonymized—file counts, sizes and speeds only. Each one was cut over and served from every region before its command finished.
Nearest region
For surge.sh names, CNAMEs to geo.surge.world and delegated domains, DNS answers with the region nearest the visitor.
Invalidated on publish
A publish tells every region to drop its cached copy of the domain, so the next request anywhere gets the new revision.
Serving is sacred
Limits pause publishing, never serving. A project that's live stays live, and nothing about serving is metered.
Built to be shipped to.
Free, including custom domains. Publish to every region in seconds.
$ npx surge