June 23rd, 2026
We are happy to announce that the new version of our Private Location image, v5.4, is now available for update!
As always, new PLM releases bring enhancements and features designed to improve your experience and ensure the highest level of performance and security.
Included in this release:
System cron is replaced to remove setuid/root user dependency: running a private location no longer requires root access
Chrome version upgraded to 147
Vault credentials improvements
Please update at your earliest convenience to ensure that you are using the most secure and efficient version of our service.
To pull the latest image, use the following command:
docker pull uptimecom/uptime-private-location:latestTo learn more about getting started with Private Location monitoring, please see our documentation. Or, to dive straight into the technical details and view the update, see our Github.
If you have any questions, email support@uptime.com.
June 22nd, 2026
We have released a new version of our Terraform provider that is now at parity with the REST API in managing all aspects of maintenance schedules and windows. The new scheduling features that were recently released are now supported in Terraform.
For more information, see our documentation on using the uptime_check_maintenance resource in Uptime’s Terraform provider.
June 17th, 2026
We have made some UI updates to the Affected Checks column when viewing the Active and Schedules lists under Maintenance Windows. These improvements allow you to see a more detailed view of the Affected Checks when viewing your maintenance windows and displays a link to quickly view each check.
Up to 3 checks are now displayed directly in the row for each schedule. Click the link to open the Check Analysis view in a new tab.
The Check Names are now directly displayed in the Affected Checks column, up to 3 checks. Schedules with more than 3 affected checks will display a + x more count. Clicking the count opens the full list.
For more information, please see our documentation on Maintenance Windows.
June 17th, 2026
We're excited to announce MCP support and a Claude Code skills plugin for Uptime.com. Using our public server, you can now leverage AI tools to create and manage checks, read alerts and outages, manage status pages, and inspect account usage. The MCP server supports both local clients and hosted streamable HTTP deployments.
For more information and deployment instructions, see our Github pages:
Uptime-mcp: the generalized MCP that can be used with any AI model
Uptime-skills: plugin specifically for Claude Code that simplifies deployment with built-in knowledge on Uptime.com’s monitoring capabilities
If you have any questions, feel free to contact support@uptime.com.
June 12th, 2026
We have released new API endpoints for maintenance windows, bringing the API to full parity with the maintenance scheduling features available in the dashboard.
GET /api/v1/maintenance/schedules/
POST /api/v1/maintenance/schedules/
GET /api/v1/maintenance/schedules/{pk}/
PUT /api/v1/maintenance/schedules/{pk}/
PATCH /api/v1/maintenance/schedules/{pk}/
DELETE /api/v1/maintenance/schedules/{pk}/
For more information, please read our API documentation.
If you have any questions, contact us at support@uptime.com.
June 10th, 2026
There is now the ability to use bulk actions within Maintenance Windows to streamline your usage.
The affected pages are:
Active - End selected Maintenance Windows
Schedules - Delete all selected Maintenance windows
To learn more about the bulk actions, please refer to our documentation on Check Maintenance Windows.
June 10th, 2026
We have added the following services to our Cloud Status Check:
For more information on Cloud Status Checks, see our documentation here.
If you have any questions, contact us at support@uptime.com.
June 3rd, 2026
We are excited to announce a new integration with Make.com. Use this integration to connect your Uptime.com checks with a Make.com account and receive alerts there.
Up/down alerts based on your checks are sent to your Make.com instance
The information contained in the alert can be formatted using payload fields
To set up integrations, navigate to Notifications > Integrations. For more information and instructions on setting up the integration, see our documentation here.
If you have any questions, contact us at support@uptime.com.
June 3rd, 2026
We are pleased to announce the kick off of our migration to a new, improved check execution system.
With over a decade of experience as a leader in the monitoring industry, we have completed a ground up redesign of our check execution engine. This ensures we can continue offering the most competitive prices, efficient executions, and continue expanding our check offerings in both location and type. More information can be found in this support document.
First locations released are as follows:
Japan Tokyo
IPv4: 202.182.105.254 IPv6: 2401:c080:1000:1d2a:5400:05ff:fefa:e743
IPv4: 45.76.97.59 IPv6: 2401:c080:1000:1da7:5400:05ff:fefa:eb7b
Japan Osaka
IPv4: 64.176.63.2. IPv6: 2401:c080:3800:2f13:5400:05ff:fefa:e731
IPv4: 64.176.60.58 IPv6: 2401:c080:3800:31e8:5400:05ff:fefa:eb79
If you rely on our User Agent and use these locations, please update your allow list with IPs mentioned above. We also recommend you subscribe to our status page for future updates .
May 27th, 2026
We have added two new integrations to Uptime.com:
Zendesk: Automatically create and update tickets when an alert is raised or cleared.
Google Chat: Receive alert notifications directly in your Google Chat channels when an alert is raised or cleared.
To set up integrations, navigate to Notifications > Integrations.
If you have any questions, contact us at support@uptime.com.