Skip to main content
Adding Uptime.com as an alert source

Follow step-by-step instructions to connect your Uptime.com checks to incident.io and start receiving alerts.

incident.io Engineering Team avatar
Written by incident.io Engineering Team
Updated over 8 months ago

🛠 Instructions

⏩ To open the alert source creation form directly, simply follow this link, and skip to step 4.

1️⃣ Head over the the Alerts section in your incident.io dashboard

2️⃣ Select the Sources tab at the top of the page

3️⃣ Press the 'New alert source' button

4️⃣ Search for 'Uptime', select it and customise the name if desired. Click continue to create the alert source.

5️⃣ Switch to your Uptime.com dashboard and navigate to Notifications: Integrations.

6️⃣ Click 'New Profile' in the top right, and select 'Custom Postback URL (Webhook)' as the provider type.

7️⃣ Assign the integration to an existing Uptime.com contact or create a new contact for the integration.

8️⃣ Grab the webhook URL and Authorization token provided to you on the incident.io alert source and paste them in to 'URL' and 'Custom HTTP Headers' field.

9️⃣ Once you've clicked save, Uptime will prompt you to test the integration. Click 'Start Test' and make sure the test alert arrives.

1️⃣0️⃣ Navigate to 'Monitoring' to select the Uptime.com check(s) for which you want to receive alerts in incident.io and assign them to the contact you've assigned the Integration Profile to.

✅ And you're done! Next time an Uptime.com monitoring check fails, you'll receive an alert within incident.io.


Frequently Asked Questions

  • How are Uptime.com monitoring alerts deduplicated in incident.io?

    • When an Uptime.com monitoring check starts firing, you'll receive an alert in incident.io. If you receive additional failing checks from the monitor, these will be deduplicated in incident.io them to limit alert noise.

  • How do Uptime.com monitoring alert events map to incident.io alerts?

    • Uptime.com 'test' and 'alert_raised' events map to the incident.io 'firing' status. 'alert_cleared' events map to the incident.io 'resolved' status.

Did this answer your question?