We’ve updated our Private Location image to version 4.2.The updates are as follows:<ul><li aria-level="1">Image Vulnerability Fixes: We have addressed several vulnerabilities to ensure a more secure image.</li><li aria-level="1">Kubernetes Support for Non-Privileged Mode: We now support running in non-privileged mode on Kubernetes.</li><li aria-level="1">High CPU Issue Resolved: We have resolved a high CPU usage issue that occurred in specific cases due to the Nagios check_update function.</li></ul>We suggest upgrading to ensure that you are using the most secure and efficient version of our service.To pull the latest image use docker pull uptimecom/uptime-private-location:4.2 to pull the Private Location probe server 4.2 image.For more information on Private Locations, check our documentation <a href="https://support.uptime.com/hc/en-us/articles/360012622239-Getting-Started-with-Private-Location-Monitoring">here</a>.If you have any questions, email support@uptime.com.

Private Location 4.2

Help Center

Improved

Fixed

API Changes

uptime

Product Review

Planned

In Progress

Completed

Rejected

Technical Review

Terraform

Transaction Checks

User Dashboard

Checks

Status Pages

General

Reporting

Alerting

Cloud Status

Mobile Apps

Public Roadmap

At <a target="_blank" rel="noopener noreferrer nofollow" href="http://Uptime.com">Uptime.com</a>, we are dedicated to constantly enhancing our product to better serve your needs. Your feedback is invaluable in guiding our development. We invite you to share your feature requests below, as your input directly influences our product roadmap.

Have something to say?

Hey {name|there}! 👋

Uptime.com - Unified Availability

Private Location 4.2