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.

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.

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.

Send status page url in webhook data

Provide integration for https://www.pagerduty.com/

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.

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.

Longer history than 30 days would be excellent for troubleshooting performance issues.

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).

Validate strings on compressed (GZIPped) pages.

Let us decide what the lower bound of the uptime % needs to be for the check to be green. No SLA has a 100% uptime guarantee.

The current 8 servers available are reasonably spread out, but it would be really great to include a UK server so I can see the experience of my UK audience.

I would also note that visitors from the middle-East and Africa don't get a look-in: perhaps something in Israel?

Hi,
You are providing Slack notifications. It would great to get Matrix notification (matrix.org). Open source. Open API.
Thanks.

Do not give in to feature creep :-)

It would be helpful to create "alert groups" that consist of one or more SMS numbers, Slack channels, etc.

For example, I could create an alert group named "Project X" that consists of two SMS numbers and a Slack channel, and then I could assign that group to any alarms that are related to "Project X". In the future, when the members of "Project X" change I can just make changes to the alert group itself, rather than having to go to each alarm and add/remove recipients.

Thanks!

Hello!
Would be very very interesting to have a restricted read only dashboard with all our monitored webs protected with user password.
It can be very good to give to our bosses or clients, and not being worry about they changing any config.
Today, I make a simple excel dashboard getting times with the API because I dont have this.
Thank you!! :-)

It would be great to have the option to add secure the public status page with a password. Could be as simple as a htpasswd.

The super-powered API key is supposed to stay secret, but it can sometimes go public because of mistakes.
It would be nice to be able to generate a new API key, which will revoke the old one.

How can we improve updown.io?
← General
Weekly reports via Slack

It's wonderful to have weekly reports sent by email. It would be awesome to have the option to send them to Slack as well. If we could choose email and/or Slack for reports (like for the alerts) it would be ideal.

Whitelabled emails!