Probe Server IP Address Change – [PY]

Our probe in Philadelphia, Pennsylvania, USA, will be changing IP addresses on 2016/12/07:
Philadelphia, Pennsylvania (PY) is changing from 162.208.48.232 to 162.208.50.172.

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

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

[UPDATE – 2016-12-07 17:39GMT-5] – IP change complete.

Site update and feature releases Oct 2016

We’ve rolled out some UI and feature updates for NodePing today. We hope you find them helpful. I’ll summarize the changes here. Look here for future posts, which will go into more details for each.

Delayed Notifications:
You can now set a delay on ‘down’ alerts. This will help make your notifications more actionable for frequently flapping services. This new feature can also be used to escalate alerts or notify support/management if services remain offline. This feature has been available for a while in our API, but hasn’t been in our documentation, and has now been added to our UI as well. See the ‘Delay’ drop down in the Notification section of your check.

Check Cloning:
You can now clone an existing check, with all its settings, in our UI to create a new check. This will help reduce “clickty-clickty” syndrome when setting up a lot of checks with similar settings. Click on the label of the check you want to clone to display the details to reveal the ‘Clone Check’ link on the far right.

Notification Dependencies:
When an edge router or server fails, it’s assumed that all the services that depend on them will also fail. It’s not helpful to receive hundreds of alerts for dependent services. You can now set another check as a notification dependency on each check. If the dependent check is already failing, notifications will be suppressed. Use this to avoid alert floods when bottleneck services fail. You can find the ‘Dependency’ drop down in the Notification section of each check.

Disable All Notifications:
There is now a link in the Contacts tab to “Disable notifications”. Use this to suppress all alerts until you re-enable them using the same link. It’s another way to help avoid the distraction of alert floods during big outages.

Disable Checks:
Now you can disable multiple checks with one click. You’ll find the “Disable All Checks” link in the Account Settings – General Settings tab. You can also apply filters based on label, target, or check type to, for example, disable all PING checks or all checks pointing to “example.com”. Use this to disable checks during planned outages/maintenance or to quiet down your logs when troubleshooting.

All the above new features, except check cloning, are also available via our API. If you have any questions about these new features, reach out to support@nodeping.com; we’re happy to help.

Probe Server Changes – [UT,RO,FL,AM]

The following probe servers will be changing IP addresses on 2016/10/04:
Ogden, Utah USA(UT) will change from 192.154.111.10 to 192.154.102.130
Bucharest, Romania (RO) will change from 77.81.108.115 to 89.45.10.135
Miami, Florida (FL) will change from 107.161.178.251 to 162.254.202.35

We’ll also be adding the following new probe in our East Asia/Oceania region on 2016/10/04:
Melbourne, Australia (AM) will be added – 103.207.28.11

We’ll also be removing the following probe in our Latin America region on 2016/10/04:
Curico, Chile (CL) will be removed – 190.114.254.203

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

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

Edit 2016-09-28 – Fixed the incorrectly listed the current IP for the Florida probe FL.

[UPDATE – 2016-10-04 23:15GMT-4] – changes complete.

Probe Server IP Address Change – [NC]

Our probe in North Carolina, USA will be changing IP addresses on 2016/8/9:
North Carolina (NC) is changing from 192.111.152.6 in Lenoir to 104.225.1.179 in Cary.

We had some trouble with the previous data center in Lenoir.  It was intercepting all our SMTP checks causing some SMTP services to appear up when they were really down.

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

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

[UPDATE – 2016-08-09 09:56GMT-4] – IP change complete.

Probe Server IP Address Change and Addition – [RO,SE,HU]

The following probe server will be changing IP addresses on 2016/3/9:
Bucharest, Romania (RO) will change from 89.45.249.16 to 77.81.108.115

We’ll also be adding the following new probe in our Europe region on 2016/3/9:
Goeteborg, Sweden (SE) will be added – 185.86.148.18

We’ll also be removing the following probe in our Europe region on 2016/3/9:
Budapest, Hungary (HU) will be removed – 213.181.208.18

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

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

[UPDATE – 2016-03-09 10:44GMT-7] – IP change and addition for SE complete.

Probe Server IP Address Changes and Addition – [FR, OH, PY, TX, SG]

The following probe servers will be changing IP addresses on 2016/2/2:
Paris, France (FR) will change from 51.254.219.11 to 37.59.86.248
Philadelphia (PY) will be changing from 76.72.172.156 to 162.208.48.232
Dallas, Texas (TX) will be changing from 107.155.78.66 to 107.155.66.30
Singapore (SG) will be changing from 116.251.216.9 to 191.101.242.137

We’ll also be adding the following new probe in our North America region on 2016/2/2:
Columbus, Ohio (OH) will be added – 206.222.22.82

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

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

[UPDATE – 2016-02-02 10:00GMT-7] – IP changes and addition for OH complete.

Probe Server IP Address Changes – [NV, AZ, BR, UK]

The following probe servers will be changing IP addresses on 2015/09/01:
Las Vegas, Nevada (NV) will change from 64.235.39.44 to 199.241.137.152 (we continue to struggle to find a stable host in NV)
Phoenix, Arizona (AZ) will change from 198.20.67.72 to 162.253.177.250
São Paulo, Brazil (BR) will change from 177.67.81.184 to 131.72.55.152
Bristol, England (UK) will change from 37.9.59.21 to 146.185.21.51 (London)

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

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

 

[UPDATE – 2015-09-01 12:20GMT-6] – IP changes 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.