Probe Server IP Address Changes – [NV, KS] and an addition – [PY]

The following probe servers will be changing IP addresses on 2015/07/20:
Las Vegas, Nevada (NV) will change from 5.226.169.94 to 64.235.39.44
Kansas City, Missouri (KS) will change from 173.208.220.194 to 172.86.180.18

We’re also adding one new probe on 2015/07/20:
Philadelphia, Pennsylvania (PY) – 76.72.172.156 in the North America region (NAM)

Please adjust your firewalls appropriately so your checks do not fail because of the probe IP address changes and addition.

An always current and updated list of all the IP addresses for our probe servers can be found in the FAQ

[UPDATE – 2015-07-20 11:55GMT-6] – IP changes and addition for PY complete.

Probe Server IP Address Change – [NV] and additions – [OT, UK]

Our probe server in Las Vegas Nevada (US) will be changing IP addresses on 2015/03/18:
NV will change from 208.66.75.231 to 5.226.169.94

As NodePing continues to grow, we’ll also be adding two new probes on 2015/03/18:
Ottawa, Ontario (CA) – OT (199.167.130.19) in the North America region (NAM)
Bristol, England (UK) – UK (37.9.59.21) in the Europe region (EUR)

Please adjust your firewalls appropriately so your checks do not fail because of the probe IP addresses change and additions.

An always current and updated list of all the IP addresses for our probe servers can be found in the FAQ

[UPDATE – 2015-03-18 16:05GMT-6] – IP change for NV and additions for OT and UK are complete.

Probe Server IP Address Changes – [LD, TX]

Our probe servers in the following locations will be changing IP addresses on 2015/01/08:
LD will change from 87.117.200.68 to 5.2.16.148
TX will change from 23.92.75.43 to 107.155.78.66

Please adjust your firewalls appropriately so your checks do not fail because of the probe IP addresses changes.

An always current and updated list of all the IP addresses for our probe servers can be found in the FAQ.

[UPDATE – 2015-01-08 11:25GMT-7] – IP changes for LD and TX are complete.

Follow redirects for HTTP checks

We’re happy to announce a new optional feature for our HTTP checks – follow redirects.

Until today, NodePing website monitoring only supported the single HTTP request/response.  An often requested feature was the ability to follow HTTP redirect codes in the 300s and evaluate the check on the final page of the redirects.

redirect

We believe you should monitor everything, including your redirect pages. We recommend you create a separate check for the redirect and ensure the 301 or 302 status code and the header ‘Location’ is to the destination URL you expect and then create another check to monitor that destination URL. We still think this is a best practice for website monitoring and will help you pinpoint a failure more quickly should something happen to your redirect or destination URL.

We realize there’s a use case for monitoring HTTP responses that includes following redirects and we’re happy to include that option in our HTTP checks. The default behavior remains the same – that is we do not follow redirects but rather evaluate an HTTP status code in the 300 range as a successful response.

To activate this option in your HTTP check, set the “Redirects:” drop down to “Follow redirects” or, if you’re using the API, set a ‘follow’ parameter to true. Our probes will follow up to 4 redirects and per the RFC, will only redirect on HTTP GET requests.

For more information, please see our documentation on the supported HTTP checks:
HTTP – Simple website monitoring for 200-399 HTTP status codes
HTTP Content – Verify content exists (or doesn’t exist) in the returned HTML
HTTP Advanced – The swiss-army-knife of HTTP checks. Set request headers, verify response headers, send JSON, XML, or form data, use GET/POST/PUT/HEAD/DELETE/TRACE/CONNECT methods, verify content, and expected returned HTTP status codes. You can even monitor a 404 page.

 

Adding Probes to North America and Europe along with an IP Change [DE]

We’re adding three new probes in the North America region and two to the Europe region.
These changes will take place 2014-12-02. Please update your firewalls appropriately.

Phoenix, Arizona (US) – AZ (198.20.67.72)
Kansas City, Kansas (US) – KS (173.208.220.194)
New York City, New York (US) – NY (168.235.67.200)

Paris, France (FR) – FR (5.196.125.25)
Budapest, Hungry (HU) – HU (79.120.211.210)

In addition, we have one IP change to our current probe in Germany:
DE will change from 94.249.196.145 to 62.113.242.111

As always, a current list of all the IP addresses for our probe servers can be found in the FAQ.

[UPDATE – 2014-12-02 11:28GMT-7] – New probes are online and IP change for DE is complete.

Probe Server IP Address Change – [WA]

Our probe server in Seattle Washington, USA will be changing IP addresses on 2014/10/30:
WA will change from 162.210.249.48 to 107.161.26.116

No data loss is expected.

Please adjust your firewalls appropriately so your checks do not fail because of the probe IP addresses change.

An always current and updated list of all the IP addresses for our probe servers can be found in the FAQ.

[UPDATE – 2014-10-30 11:55GMT-6] – IP change for WA is complete

Disabling SSLv3 on NodePing website and API

In response to the recently announced vulnerability in SSLv3, we are disabling this version on our web site today, and for our API tomorrow. We do not anticipate that this will negatively impact any of our users. However, if you use our API with an older implementation of a library or scripting language, you may want to check to make sure that it supports newer protocols.

Follow

Get every new post delivered to your Inbox.

Join 60 other followers