I use pushover.net for all of my lightweight notifications - it's simple, reliable, cheap and very good so fits well with updown.io :)

At its simplest, integration takes the form of an API call with a couple of tokens and a customised message.

https://pushover.net/faq#technical-ips

Simplified or more concise Slack messages.

Maybe I overlooked it, but is there a log of the incidents available? Simply a text list of the times when a website went down, and when it was up again.

Updown is great for HTTPS checks - loving the cert expiry warnings, and I can also check my mailserver with the TCP checks.

I would like to also check the cert validity on a non-HTTPS ports. (i.e. IMAPS or SMTPS. I'm not asking for any understanding of the protocol for non HTTP(S) ports, just connect and do cert checks.)

Monthly reports

A status page with several checks, showing daily/weekly/monthly stats for all of them.

OS X Safari notifications

Ability to monitor periodic tasks with a simple HTTP call (like https://deadmanssnitch.com/ or http://probyapp.com/)

ex: curl https://updn.io/9jNKL24

Provides integration with statuspage.io, so your status page is updated automatically when updown detects an issue.

I like ordering checks by status having the "down" first.
It would be nice, in this view, to have the disabled checks at the bottom of the list.

I use updown to check a url that is behind a caching CDN. If the origin server goes offline, real users making requests for new URLs will see errors, but I will not be notified of downtime: the updown check will still succeed since the URL it is checking has been cached.

I'd like the ability to add a random string to a URL each time it is checked, so that requests bust through the cache and check that both the CDN and origin server are online

Right now I have about 20 subdomains across 3 top-level domains.

The current "domain-suffix-oblivious" lexical ordering is kind of a mess.

I really wish all my "hexstreamsoft.com" subdomains were grouped together, and same thing for my "hexstream.net" and "hexstream.xyz" subdomains separately. Right now those are all "randomly" jumbled up together based on the lexical order of their lowest subdomain components.

We would love to be able to post alerts to Google Chat using the incoming webhooks (cf. https://developers.google.com/hangouts/chat/how-tos/webhooks). A similar integration to the one already existing for Slack would be wonderful!

When we add new monitors or edit existing monitors, prevent ajax to reload page, I think this will improve UX, especially those who have a lot of monitors.

It would be nice to be able to choose which notification recipient (email, sms, ...) to activate/deactivate when creating a check through the API.
For now all recipients are activated by default.

Instead of making the Slack webhook integration via the API, just allow users to put in a Slack URL. That way any other service which can emulate the Slack webhook schema can use the webhook feature.

As an example Discord has webhooks and if you add "/slack" to the end of a Discord webhook URL then it will parse the data as Slack does.

Currently I cannot use Updown with Discord. I also suspect that many other programs have an option to parse data like Slack so you could knock out a few webhook integrations in one simple step.

It would be nice to have either page specific or account wide custom stylesheet applied to the public status pages. Specifically, I'd use it to draw more attention to the translation dropdown and to eliminate some whitespace.

Pretty simple, when you add a webhook there should be a "test" button which fires an example event to the webhook URL so the user can test it to ensure it works.

Validate strings on compressed (GZIPped) pages.

Notifications about expired certificates can be improved (made more noticable) in 2 ways:
1. Display expired certificates as downtime (or use some other highlighting) in weekly reports (and other periodic reports).
2. Send repeated notifications for expired certificates (as it is done for downtime).