In some situations, it might be necessary to allow requests from your VIP Go environment to interact with private resources. For example, you may need to allow 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 at this endpoint: https://go-vip.net/ip-ranges.json
Adding the provided IP range for a given data center will allow your site to communicate with a restricted platform/resource.
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:
serialJSON field within the response contains an epoch timestamp of the last change.
updatedAtJSON field within the response contains an ISO 8601 timestamp of the last change.
- HTTP response of requests made with the
If-Modified-Sinceheader. If the last modification date/time is newer than the value provided in the
If-Modified-Sincerequest header, the response will be
HTTP 200 OK. Otherwise, the response will be
HTTP 304 Not Modified.