The PressHarbor network · Powered by WP Cloud

You work here.
Your audience is everywhere.

Keep WordPress close to where you work. Let our global content delivery network bring your pages and media closer to your visitors. Behind it all, automated failover helps keep your origin available.

Find your originExplore the network
One origin, global delivery A conceptual globe connects a WordPress origin with distributed delivery points. This diagram does not depict actual routes or server positions. WP Create nearby. Deliver worldwide.
Origin choices
4
CDN locations
29
Continents represented
6
CDN included
Every plan

One site. Close to you and your audience.

  1. 01A home for your WordPressYour origin runs the site and handles the work.
  2. 02A shorter trip to your readersThe CDN serves eligible cached content near your audience.

Start where you do your best work.

You open WordPress, upload an image, save a draft, or update a product. Those requests go to your origin: the home of your WordPress site. Choosing one near you or your team is a practical starting point for keeping that everyday work responsive.

Four places to call home. Choose yours when you set up your site.

US West

Los Angeles

California, USA

US Central

Dallas

Texas, USA

US East

Ashburn

Virginia, USA

EU West

Amsterdam

Netherlands

How do we choose? The geeky explanation.

Your chosen originWordPress runs here
29 CDN locationsEligible content is cached near visitors
Your audienceAcross the world

The four origins also serve as CDN locations and are included in the 29-location total below. Uncached and personalized requests still go to your origin.

Then your audience shows up. From everywhere.

A reader in London. A customer in Tokyo. A subscriber across town. They don’t all need the same path back to your origin for every piece of content. Our CDN stores copies of eligible content across 29 locations, so cached responses can be delivered closer to them.

Reading a page or loading an image

A nearby copy does the job.

When eligible content is available in cache, a CDN location serves it without fetching that content from your origin again.

VisitorCDN cache
Signing in or checking out

WordPress handles the personal part.

An account, a cart, or another personalized response needs WordPress. These requests, along with cache misses, go back to the origin for the work a cached copy cannot do.

VisitorNetworkOrigin

Caching depends on the request and the site’s configuration. The CDN does not turn every response into a cached response.

29 CDN locations. Global delivery.

This is the network behind that journey. All four origins are included in the location count. CDN delivery is included with every plan.

North America 12

  • Ashburn, Virginia
  • Atlanta
  • Chicago
  • Dallas
  • Denver
  • Los Angeles
  • Miami
  • New Jersey
  • New York
  • San Jose
  • Seattle
  • Toronto

Europe 8

  • Amsterdam
  • Frankfurt
  • London
  • Madrid
  • Milan
  • Paris
  • Stockholm
  • Vienna

Asia 5

  • Hong Kong
  • Mumbai
  • Osaka
  • Singapore
  • Tokyo

South America 2

  • Santiago
  • São Paulo

Africa 1

  • Johannesburg

Oceania 1

  • Sydney

Locations documented by WP Cloud, checked October 1, 2026. Network locations can change.

A little geography.
A little network geekery.

Here’s what goes into the origin finder. Open the hood, check the math, and see what those milliseconds actually mean.

First, we measure the distance.

A US ZIP code gives us an approximate location through Zippopotam.us. Or, with your permission, your browser supplies your location. We calculate the shortest distance around the globe to each origin city using the Haversine formula.

That is geographic distance. It does not trace the cables between you and the data center. ZIP codes and origin coordinates represent approximate locations, too.

Then comes the napkin math.

Our model assumes light travels through fiber at roughly 200,000 kilometers per second. A round trip travels the distance twice. We multiply that ideal travel time by three as a rough allowance for indirect routes and network delays.

Distance in km × 0.03 ≈ round-trip millisecondsExample: 1,000 km × 0.03 ≈ 30 ms

The multiplier is a rule of thumb, not a measured property of our network. Every origin gets the same multiplier, so the recommendation still follows distance. The calculator does not perform a live speed test.

The internet takes detours.

Cables follow actual routes. Networks exchange traffic at particular places. Your provider, routing, and congestion can change the result. A farther origin can sometimes respond faster, and two origins can be effectively tied.

Use the recommendation as a starting point for choosing where you do most of your WordPress work. The milliseconds are approximate round-trip latency, not download speed or page-load time. WordPress processing and the rest of the page still have work to do.

Curious enough to compare?

WonderNetwork publishes measured city-to-city ping times. They are useful context, but measure connections between their servers, not your connection to PressHarbor. Our current calculator does not use those measurements.

For more on the physics, Cloudflare explains how distance affects internet latency.

Your location stays out of your order.

ZIP lookups are sent to Zippopotam.us, which uses GeoNames data. Browser coordinates stay in the calculator and are not sent to that ZIP service. The finder does not store your location.

When you set up your site, choose your recommended origin yourself. The finder does not automatically carry the choice into your order.

Your next post. Your next customer. Your network.

Your first month of Core is free with code 1MONTHFREE. Then $35/month. For new customers on monthly Core hosting.

Try Core free for one month