VIP Go IP Ranges

VIP Go platform specific

This document is for sites running on VIP Go.

Learn more

Overview #

In some situations, it might be necessary to whitelist requests from your VIP Go environment to private resources. For example, you may need to whitelist requests from your VIP Go site to an internal tool that’s behind a firewall.

We provide publicly accessible IP ranges for our origin data centers for these situations.

The IP range for each data center can be found here.

Whitelisting the provided IP range for a given data center will allow your site to communicate with a restricted platform/resource.

↑ Top ↑

Precautions Around IP Range Updates #

VIP Go IP ranges are subject to change at any time, and we do not provide advance warning of IP range updates.

For this reason, we recommend building your application in such a way that unexpected IP range updates are non-breaking either because the ranges aren’t required for vital site functionality, a fallback method is provided, or some other strategy.

There are a few mechanisms to monitor updates to the published ranges:

  • The serial JSON field within the response contains an epoch timestamp of the last change,
  • The updatedAt JSON field within the response contains an ISO 8601 timestamp of the last change,
  • HTTP response of requests made with the If-Modified-Since header. If the last modification date/time is newer than the value provided in the If-Modified-Since request header, the response will be HTTP 200 OK. Otherwise, the response will be HTTP 304 Not Modified.

Ready to get started?

Drop us a note.

No matter where you are in the planning process, we’re happy to help, and we’re actual humans here on the other side of the form. 👋 We’re here to discuss your challenges and plans, evaluate your existing resources or a potential partner, or even make some initial recommendations. And, of course, we’re here to help any time you’re in the market for some robust WordPress awesomeness.