Changelog

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.

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.

We have added the following services to our Cloud Status Check:

• TingleFlow

• ePayPolicy

• Vularo

• Algolia

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

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

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. 

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 .

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.

We’re happy to announce that we’ve added two new integrations with Grafana. This allows you to push response time metrics from your Uptime.com checks to Grafana Cloud via Graphite ingestion and the Prometheus service.

Grafana is used for monitoring, observability, and incident response. Use this integration to have your Uptime.com metrics displayed directly in your Grafana cloud instance for a unified performance view.

For more information see our documentation on these two integrations:

• Configuring Grafana Graphite

• Configuring Grafana Prometheus

We have added four new services available for monitoring in Cloud Status checks:

• Auth0

• CurrencyLayer

• Elastic Email

• Checkmarx

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