ITRS acquires IP-Label. Read the press release.

What’s new

See the latest features and product updates in Uptrends
View the API changelog and reported issues in the Incident log.

Submit a feature request

UPDATE

APR 2025

#Support for specific HTTP versions is now available in the Multi-step API (MSA) monitor steps

It is now possible to specify the HTTP version for each step of an MSA monitor. This lets you control which HTTP version the checkpoint servers use when making requests:

By default, the HTTP version option is unchecked, meaning the server will automatically use the highest supported HTTP version available, with a fallback back no lower than HTTP/1.1. Currently, HTTP/3 is available at selected checkpoint locations, and support will soon be expanded to additional locations.

On a similar note, the HTTP configuration allows you to select only one version, while the TLS configuration supports selecting multiple versions. This is because TLS supports version negotiation during the connection process, whereas HTTP/3 does not and requires a specific version to be defined.

HTTP version

UPDATE

MAR 2025

#New scripting methods are now available in Multi-step API (MSA) monitors

The following scripting methods can now be used in the Pre-request and Post-response scripting tabs of Multi-step API (MSA) monitors:

  • ut.crypto.cert.parseCrl(bytes) — parses a certificate revocation list and returns its metadata.
  • ut.crypto.md5(value) — generates an MD5 hash of the specified value.
  • ut.crypto.sha1(value) — generates an SHA-1 hash of the specified value.
  • ut.crypto.sha256(value) — generates an SHA-256 hash of the specified value.
  • ut.crypto.sha512(value) — generates an SHA-512 hash of the specified value.
  • ut.response.bytes — returns a byte array containing the response body. Responses are limited to 100 MB.

Note that ut.response.bytes is only available in the Post-response tab of your MSA monitor. The scripting methods for generating MD5 and SHA hashes enable you to store and send values securely, ensuring data protection through hashing.

UPDATE

MAR 2025

#API user overview updates

The API user overview now shows the number of requests for each API user over the last 30 days. This lets you identify which API users are active and which APIs are frequently used.

API requests over the last 30 days

UPDATE

FEB 2025

#Introducing new alerting variables

The following alerting variables are now available for use:

  • @alert.numberOfConsecutiveErrors — contains the total number of consecutive errors (confirmed errors) of the alert. This returns 2 when the API response is {"numberOfConsecutiveErrors": "2"}.
  • @alert.checkpointName — contains the checkpoint’s name or location where the alert was last checked. This returns Ghent, Belgium when the API response is {"checkpointName": "Ghent, Belgium"}.
  • @‌alert.responseHeaders — contains the response headers of the alert in key-value pairs. For example, this returns {"Content-Type": "text/html"} from the API response header, similar to how the values are returned for @alert.responseBody.

Note that the value of the @‌alert.responseHeaders can be empty if the Private location data protection is enabled on a private checkpoint location performing the alert check. For more information, see Alerting system variables.

UPDATE

FEB 2025

#Additional conditions for Check URLs loaded by the page

The Check URLs loaded by the page is an error condition that checks if specific page elements are loaded on your website. These page elements are the URLs displayed in your Waterfall chart, including images, files, and other website resources.

This error condition now allows you to set extra criteria for checking each page element’s metrics. By clicking the new +Add additional condition button, you can now specify the page element’s response size in bytes (B), total time in milliseconds (ms), and status code:

If you want to get errors when your image loads longer than 2 seconds or if a file results in a status code higher than 400, you can add specific criteria for each.

The Check URLs loaded by the page error condition are available for Browser or Full-Page checks and Transaction monitors. Note that for transaction monitors, you need to select the Waterfall option in a step to set the additional conditions.

Additional conditions for Check URLs loaded by the page
By using the Uptrends website, you consent to the use of cookies in accordance with our Cookie Policy.