SpinupWP Ping

SpinupWP Ping is the uptime monitoring service behind SpinupWP site monitoring. It checks that WordPress sites hosted on servers managed by SpinupWP are online and alerts the site’s owners when they go down.

This page explains how SpinupWP Ping identifies itself, where its requests come from and how it behaves, so you can recognize its traffic and allow it through your firewall or CDN.

Switching to SpinupWP Ping

SpinupWP site monitoring previously used a third-party service, Ping Ping. We’re moving monitored sites over to SpinupWP Ping in batches, so for a while some sites will still be checked by Ping Ping. You don’t need to do anything for the switch unless your site restricts access by IP address or user agent. In that case, allow SpinupWP Ping’s IP addresses or user agent before your sites move over, or they’ll be reported as down.

Which Sites Are Checked

SpinupWP Ping only checks sites whose owners have turned on monitoring for that site in their SpinupWP dashboard. It doesn’t crawl the web, follow links or discover new URLs. Each monitored site has exactly one URL checked: its homepage.

How to Identify SpinupWP Ping

User Agent

Every request SpinupWP Ping makes to a monitored site sends the following User-Agent header:

SpinupWP-Ping/1.0

IP Addresses

Requests come from the following IP addresses. SpinupWP Ping connects over IPv4, and only uses IPv6 when a site’s domain has no IPv4 (A) record.

Location IPv4 Address IPv6 Address
Toronto, Canada 139.177.199.26 2600:3c04::2000:06ff:fe0d:7f51
Frankfurt, Germany 139.162.142.27 2a01:7e01::2000:56ff:fecd:a16f
Singapore 45.118.133.202 2400:8901::2000:43ff:feaa:284a

The same addresses are available as a plain text list, one per line, at https://spinupwp.com/ping/ips.txt for use in firewall rules and scripts. We’ll update this page and the list before adding or changing an address.

How SpinupWP Ping Checks a Site

  • One request per minute. Each monitored site is checked once every 60 seconds. Checks rotate between the three locations above, so each location requests a site at most once every 3 minutes.
  • A single GET request to the homepage. A query string is added (e.g. https://turnipjuice.media/?nocache=1) so the request bypasses the page cache and confirms PHP is working on the server.
  • Only the response headers are read. The connection is closed as soon as the status line and headers arrive. The page body is never downloaded, and no assets, scripts or links on the page are requested.
  • Redirects are not followed. Any 2xx or 3xx response counts as up.
  • Requests time out after 5 seconds.
  • Failures are confirmed from a second location. When a check fails, one extra request is made from a different location to confirm the outage before the site is reported down. This avoids false alarms caused by a network problem between one location and the site.
  • No cookies, credentials or form submissions. SpinupWP Ping never logs in, submits forms or sends cookies, and it doesn’t execute JavaScript.

Allowing SpinupWP Ping Through a Firewall or CDN

If your site sits behind a firewall, a security plugin or a CDN with bot protection, it may block or challenge SpinupWP Ping’s requests. A blocked or challenged request returns a 403 or similar error, and your site will be reported as down even though it’s working.

To avoid this, allow requests from the IP addresses listed above, or allow the SpinupWP-Ping/1.0 user agent. If you use Cloudflare, see Troubleshooting Cloudflare Issues for help with bot protection settings.

Stopping SpinupWP Ping

SpinupWP Ping stops checking a site as soon as monitoring is turned off for it. To turn off monitoring, open the site in your SpinupWP dashboard, go to the Monitoring tab and switch off the toggle.

If SpinupWP Ping is requesting a site you manage that isn’t in your SpinupWP account, or you have any other questions about its traffic, email us at [email protected] and include the domain. We’ll stop the checks.