Indeed that's an idea but unfortunately there's no notion of "connection" for UDP so it's not possible to know if a port is filtered or if a service is simply not responding because it waits for a specific message for example. There is just one obvious case when the port is "officially" closed and so a response is sent to tell you that. Which kind of service would you like to monitor? would it require to send a specific packet? would it need to check for a response? Is just knowing that no response is received (not knowing if it's filtered or open) enough for your use-case?

One important thing to note here is that having an invalid certificate does NOT prevent the expiration notifications. This is independent so you can keep an "invalid" certificate forever (updown will not notify you again about this) and still benefit from expiration warnings. This way we already kind of "tolerate" this use-case of running a non-publicly trusted certificate.

About the suggested changes, I would like to avoid the custom cert/CA UI because that's a lot of added complexity for a very small use-case among my clients. It'll generate more support also as people will wonder what this do, try to upload other certificates, it'll be annoying for self-signed certificates, etc... The UI to manually "acknowledge" that one cert should be considered valid though sounds more doable for me, I'll keep this suggestion to track the demand and will probably add this someday.

Thanks for the suggestion, this is something which have been asked a couple times in the past and is under review for the roadmap.

Quick question: if this is for website which have a public status page, how would you feel about a public (no api key) read-only API for them?

Or do you prefer one read-only API key per check?

Good suggestion, that is definitely a pain point. But I have a little hack for this (which I personally use), not very pretty but efficient: Add an anchor at the end of the URL to indicate an alias of your choosing. This anchor will not be sent to your server (it’s a client-side HTTP feature) but it’ll show in your recipient list and bulk edit screen so it makes it easier to distinguish URLs, example:

https://example.com/xxxxxxx#project-A
https://example.com/yyyyyyy#project-B

Thanks for your offer, I just sent you the translations by email.

Hi, 2 months ago we started providing canonical URLs so search engines would only display a single result (without the localized version) but it looks like this is not enough and multiple versions are still indexed. We’ll probably add some noindex to help with that.
On the other end we’re not gonna totally block the indexing of the main status page because this is a feature, being able to lookup a status page when the monitored service is down can be useful.

Thanks for the suggestion, I’ve just merged this with another one about DNS check. This is something we’re thinking about but is not planned yet.

In the meantime what you made is a great workaround, if other users are interested I encourage them to leave a comment here with a way to contact them so you may give them the URL of your service if you want.

Hello,

Actually 14, 7, 1 is already the special schedule for let’s encrypt certificates. This is automatically detected by updown.io so you don’t have to, normal 1-year certificates get an additional 30 days reminder.

The threshold for let’s encrypt certs starts at 14 days because the default renew delay is 30 days before expiration: https://certbot.eff.org/docs/using.html. This can be down to 23 days with a weekly cron for example (pretty common) so that’s why we chose 14 days, so you have plenty of time to renew but still have time to investigate and fix any potential auto-renew issues.

If you’d rather renew your cert only 5 days before expiration that’s up to you but we won’t recommend or support this configuration as we consider it dangerous ☺

I’ll mark this suggestion as “Under Review” to measure the need for this.

Yes, I want to do it for a long time but the Qualys API is not free to use for commercial projects so I need to discuss with them (this is currently in discussion).

Ok I’m moving this back to “under review” as it’s gathering a lot of interest, but this would require first https://updown.uservoice.com/forums/177972/suggestions/16982392 and https://updown.uservoice.com/forums/177972/suggestions/15589635 to be implemented to provide a decent UI for this.

Hi all, there’s now an option for that which is through Zapier (we just added native Zapier integration): https://updown.uservoice.com/knowledgebase/articles/1911991

Using this you can connect PagerDuty and receive alerts from updown.io. I’m keeping the suggestion “under review” because we might provide a native integration later.

I like the idea ☺

Hi all, there’s now an option for that which is through Zapier (we just added native Zapier integration): https://updown.uservoice.com/knowledgebase/articles/1911991

Using this you can connect pushover.net and receive alerts from updown.io. I’m keeping this suggestion “under review” to gather interest about a native integration with pushover.

This was planned for a while because initially with only the individual status pages there was no way to specify any text. But now that we have the multi-site status pages (e.g. https://demo.updown.io/), there is a free text "description" at the top, which supports links, newlines and emojis. This allows for this kind of use-case (roughly) as you can edit this field to indicate incidents, times, some emoji to catch attention on current status, link for more details, etc..

Now that we have this, I prefer to wait before implementing more specific status page features because we don't really want to become a full-fledged status page provider otherwise people will ask for MUCH more (notifications to clients, RSS, integrating other metrics, custom design, etc..) and we have enough work to spend our time on the core product (the monitoring) already ☺

While I understand the need, being in China is a lot of work (mainly support and maintenance) as the network conditions are erratic and with out current double check policy would not actually notify if your website is unreachable in China (unless we have two servers here and become a regional monitoring service but that’s not the objective and we can’t just do that in every country). I’ll keep the idea open to measure interest. Also if some of you have recommendations for a dependable and affordable hosting provider in China I’m interested.

There’s no UI for this yet but feel free to ask support if you need, we can bulk add for you.