Probe Server Changes [NY] and Addition [MO]

The following probe servers will be changing IP addresses on 2018/05/09:

New York City, New York (NY) – USA is changing from
(168.235.67.200 / 2604:180:2:38f::928a)
to
(66.23.202.26 / 2605:9f80:c000:127::2)

We’re also adding a new probe to the North America region on 2018/05/09:
Kansas City, Missouri (MO) – USA
(63.141.244.242 / 2604:4300:a:9d:202:c9ff:fec0:da0e)

Please adjust your firewalls appropriately if you whitelist 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, a text file, and via DNS query, probes.nodeping.com.

 

[UPDATE – 2018-05-09 19:00GMT-6] – IP changes and probe addition complete.

Update to TOS and Privacy Policy – NodePing and GDPR

Part of the benefit of being a relatively small distributed company in the Internet cloud age is that we can have a global reach without requiring a lot of infrastructure and overhead. We have customers all over the world, but we have almost no presence anywhere beyond our home office. Our people can work from anywhere with a good Internet connection. Since we work in the cloud, most of our computer systems are in places we have never been. We don’t even handle payment information directly in any of our workplaces. Payment information is passed directly to our payment processors. Working in the cloud age helps all of this work smoothly and safely with very little physical infrastructure required.

The downside of all of that is that our customers are all over the place, including legal jurisdictions all over the world. The regulatory world hasn’t really caught up with the idea of cloud based distributed companies. We want to comply with all applicable requirements, but understanding what requirements apply to us in various locations isn’t always easy.

The GDPR has brought this challenge front and center for us. We do not have any actual presence in any European countries. However, we do have customers in nearly all European countries, and are subject to some data privacy protections where those customers are located. That makes sense, and we want to be good citizens, but as with many other Internet based companies it can be daunting to figure out how the regulations apply to us.

Fortunately for us, the principles established in the GDPR are principles that we were already following in our normal practices. Our customers are businesses and providers of Internet based services, and for the most part we don’t provide services to individual end users. Additionally, our customers manage their own data, have full access to the information in our systems, and we don’t process or use the information they set up in our service beyond what they configure for their own use.

We did find that there were a few requirements related to the GDPR that, while our prior practices were basically already in compliance, weren’t clearly articulated in our Terms of Service or Privacy Policy. So, we’re updating both documents to more clearly set out how our policies and practices address these areas.  The updates will take effect on 2018-05-18

This includes more clearly stating that we are not collecting or processing data beyond what our customers configure to use for their monitoring. We only use contact information in our system to provide the monitoring you configure, and send the notifications you set up in the way you configure them. Our customers can download their own data whenever they want to. Beyond that, we don’t use or process information from our customers.

This is our normal practice, and applies to everyone. We don’t maintain a separate policy for customers in Europe.

Since we are a data processor, and the data is under the control of our customers who are themselves businesses providing services to others, for GDPR purposes we are a Processor rather than a Controller. Since we don’t have a presence in any EU countries, and we provide processing services to controllers in several EU countries, according to the guidelines published by the Article 29 Working Party, the lead supervisory authority will be the supervisory authority that is competent to act as lead for the controller.

If you are a data controller in a European country, or even if you aren’t, you may have questions about our systems that are necessary for you to comply with obligations you have in your location, and for your customers. If you have questions or concerns that aren’t addressed in our updated policies, please let us know.

Probe Server Changes [PY,NC]

The following probe servers will be changing IP addresses on 2018/04/03:

Cary, North Carolina (NC) – USA is changing from
(104.225.1.48 / 2607:fc50:0:15::3a0)
to
Charlotte, North Carolina (NC) – USA
(192.154.255.88 /2604:9980:0:12c:ec4:7aff:fecb:776c)

Philadelphia, Pennsylvania (PY) –  USA is changing from
(154.16.159.242 / 2604:bf00:210:1d::2)
to
(208.82.130.170 /2604:bf00:214::10)

Please adjust your firewalls appropriately if you whitelist 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, a text file, and via DNS query, probes.nodeping.com.

 

[UPDATE – 2018-04-03 11:35GMT-6] – IP changes complete.

Probe Server Changes [UK,NL,NC,NJ,SG] and removal [ES]

The following probe servers will be changing IP addresses on 2018/02/07:

Manchester, England (UK) – GB is changing from
(185.116.237.211 / 2a06:8181:a0:bfaf::1)
to
Leeds, England (UK) – GB
(109.75.172.133 / 2a00:f9c0:0:405::12)

Amsterdam, Netherlands (NL) – NL is changing from
(176.56.238.119 / 2a00:d880:5:a0f::2)
to
(37.252.125.64 / 2a02:2770:5:0:21a:4aff:fe1a:c131)

Asheville, North Carolina (NC) – USA is changing from
(64.187.224.66 / 2605:a880:0:36::10)
to
Cary, North Carolina (NC) – USA
(104.225.1.48 / 2607:fc50:0:15::3a0)

Newark, New Jersey (NJ) – USA is changing from
(185.35.78.51 / 2001:19f0:1604:3ede:250:56ff:feae:67ec)
to
(23.226.135.34 /2607:fcd0:ccc0:1301::10)

Singapore (SG) – SG is changing from
(103.16.16.30 / 2001:df0:24f:214::10)
to
(172.104.181.238 /2400:8901::f03c:91ff:feb9:fbf4)

The following probe is being removed on  2018/02/07:
Madrid, Spain (ES) – ES
(185.4.92.30 / 2a02:4ac0::2002)

Please adjust your firewalls appropriately if you whitelist 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, a text file, and via DNS query, probes.nodeping.com.

[UPDATE – 2018-02-07 10:35GMT-7] – IP changes and probe removal complete.

Cluster Check

Allow me to introduce our newest check type, Cluster.

The Cluster check allows you to group interdependent NodePing checks in order to get notifications and track availability of the group of checks as a whole. You specify a threshold of how many of those checks must be passing in order for the cluster to be considered ‘up’. If the number of those checks passing drops below your configured threshold, the cluster check will fail and send the configured notifications.

We use it to keep an eye on our Cassandra servers but you can use it for any logical group of services that are interdependent. Some other use cases:

  • DNS services – monitor each DNS server with DNS checks and then a cluster check on those DNS checks to get that very important alert when all DNS servers are offline!
  • Web servers – monitor the backend web servers behind your reverse proxy or load balancer to make sure you have enough of them available to handle the traffic.
  • SMTP – monitor your SMTP checks and know that there’s always at least one server available to receive email for your domains.

Cluster checks are available to all NodePing plans today. If you’re not using NodePing yet, please sign up for our 15-day, free trial today.

 

Banana image Designed by Daviles / Freepik

Probe Server Changes and Addition [IT,UK,CH,JP,CA,OR,GA]

The following probe servers will be changing IP addresses on 2017/12/05:

Manchester, England (UK) – GB is changing from
(194.187.248.8 / 2001:ac8:21::b0)
to
(185.116.237.211 / 2a06:8181:a0:bfaf::1)

Tokyo, Japan (JP) – JP is changing from
(106.186.116.86 / 2400:8900::f03c:91ff:fedb:b594)
to
(180.149.230.17 / 2406:d500:9::7a91:9b75)

Los Angeles, California (CA) – USA is changing from
(184.170.243.202 / 2607:f7a0:3:8:225:90ff:fe51:d0b0)
to
(192.161.172.202 / 2607:fcd0:106:ab01::10)

Portland, Oregon (OR) – USA is changing from
(69.163.39.244 / 2605:ea00:1:1:d267:e5ff:fee7:51c)
to
(100.42.30.2 / 2604:B480:FFF6::10)

Atlanta, Georgia (GA) – USA is changing from
(66.71.251.162 / 2607:f7a0:6:a:225:90ff:fe79:4318)
to
(107.150.22.26 / 2607:fcd0:aa80:2200::10)

We’re also adding a new server to the Europe region on 2017/12/05:
Zurich, Switzerland (CH) – CH
(5.102.145.51 / 2a06:c01:1:1102::9133:51)

The following probe is being removed on 2017/12/05:
Milan, Italy (IT) – IT
(185.93.183.12 / 2001:ac8:24::40)

Please adjust your firewalls appropriately if you whitelist 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, a text file, and via DNS query, probes.nodeping.com.

[UPDATE – 2017-12-05 10:53GMT-7] – IP changes and probe addition/removal complete.

WHOIS Monitoring

Need an alert when your domain is about to expire?

Want to make sure your domain admin contact hasn’t been tampered with?

Need a notification when your configured name servers get changed?

Maybe you’re running your own TLD (you lucky dog, you) and need to verify your WHOIS servers are up and responding properly?

NodePing’s new WHOIS monitoring has got you covered. Our new check will verify the presence or absence in the WHOIS response for any text you specify, helping you ensure your domain information hasn’t been hacked or altered without you knowing.  We’ll also send alerts before the domain expires. You choose how many days ahead of expiration you want to receive the notifications and how you want to be notified (email, SMS, Voice call, Pushover, Slack, etc)

You can optionally configure a specific WHOIS server to query via IPv4 or IPv6.

WHOIS checks are available to all NodePing accounts starting today. If you don’t have an account yet, sign up for your free, 15-day trial today and let NodePing keep an eye on your WHOIS info for you.