Changelog

Follow new updates and improvements to Uptime.com - Website Monitoring.

September 16th, 2026

We’ve added management buttons to more quickly access common check actions when viewing a check report.

To view the new buttons, click the check’s name in your Monitoring view to see its report. You can now Edit, Pause, set Maintenance, and more directly from the report:

For more information, see our documentation on Uptime.com Reporting.

September 9th, 2026

We have added Five9 to our Cloud Status Check:

For more information on Cloud Status checks, see our documentation here.

September 2nd, 2026

We have added the ability to set a custom title for each step in your Transaction Checks.

You can now add a custom title to each step, making it easier to identify them on alerts and organize them at a glance.

To use this feature, navigate to your Transaction Check, open the Check Steps tab, and expand any step to fill in the Step Title field.

For more information on the Transaction Check, see our synthetic monitoring documentation here.

August 19th, 2026

We have made a small improvement to the way you select date ranges for check analysis and reporting in the UI. It is no longer necessary to click an “Apply” button after selecting the range. You can now simply click outside the selector window, or click Done, to accept the date and update the graph.

For more information on selecting date ranges, see our documentation.

August 14th, 2026

We have updated our Private Location image to version 5.5, which includes a bug fix.

We suggest upgrading to ensure you are using the most stable version of our service.

To pull the latest image, use the following command: 

docker pull uptimecom/uptime-private-location:latest

For more information on Private Locations, check our documentation here. Or for more technical details, see our GitHub.

If you have any questions, contact us at support@uptime.com.

July 31st, 2026

We have added a new ServiceNow integration to Uptime.com.

Once connected, our integration can automatically create an incident in ServiceNow when an alert happens, and resolve it when the alert is resolved.

To set it up, navigate to Settings > Integrations and select ServiceNow from the integrations library.

For more information on our ServiceNow integration, see our documentation here.

July 29th, 2026

An upcoming release will include a significant improvement to Status Pages, with more features and customization options available. The Inspire 2.0 theme will provide a sleek, updated appearance for your Status Pages, along with additional customization options.

To preview the new version:

  • Navigate to Status Pages > All Status Pages

  • In your All Status Pages view, click More Actions > Preview Inspire 2.0

We highly recommend reviewing the appearance of your page under the new theme to make any adjustments ahead of time. Custom CSS and headers/footers may display differently on the new version.

July 15th, 2026

We have updated the default sort order of the Alerts table. Ongoing alerts are now displayed at the top, followed by alerts with an end date and time. This makes currently active downtime more easily visible and places higher visual importance on issues that should be prioritized.

For more information on Alerts, see our documentation here.

July 15th, 2026

As part of our commitment to continuously expanding our coverage of third-party services in Cloud Status checks, we have added a new monitoring option: Citrix Cloud.

For more information on Cloud Status checks, see our documentation here.

July 10th, 2026

We have added a new Check Visibility option to the Element exists step in Transaction Checks.

Wait for Element To Exist/Not Exist
Wait for Element To Contain Text/Not Contain Text
Element Should/Should Not Exist
Element Should/Should Not Contain Text

Previously, a step would pass as long as the element was found in the page, even if it was not visible to the user. Now with the update, you can now choose to also validate that the element is actually visible.

To use this option, in the Transaction Check, tick the Check Visibility box.

Transaction Check with the step Element Should Exist
Transaction Check with the step Element Should Exist

An element is considered visible when all of the following conditions are met:

  • It has computed styles.

  • It has a non-empty bounding client rect.

  • Its visibility is not set to hidden or collapse.

For more information on our Transaction Check, check our documentation.