General
89 results found
-
Add a timestamp when the service was lastup when it´s down
It wold be great to have a timestamp when the service/check was last up when it´s reported as down, it might be it´s already there but I have missed it?
1 vote -
Split channels for up and down notifications
We would like to be able to have different notifications for up alerts than we do for down alerts.
3 votes -
Passkey or MFA
Adding passkey support would both simplify logins as well as make the account much more secure. Since passkey can take some time to implement, adding support for MFA such as TOTP would also be a great boost to security.
1 vote -
Add Indicator for HTTP/3
There is new kid on the block. Would be nice to have HTTT/3 indicator or test:
1 voteThis is planned of course but not in the near furture because support is still experimental in libcurl and not enabled in standard builds (as of 2023-09). We'll definitely add support for it when it becomes more mainstream in curl builds.
-
How about a dark theme?
How about having a dark theme? I find it a bit aggressive to the eyes after few minutes. Having a toggle button and choose between original or website in a dark theme would be amazing!
3 votesThis is not planned at the moment but kept open to gather interest. updown value being in alerts more than in the website this is not high priority. The less time you spend on the website the better if it's done well :)
-
Add blacklist monitoring
Having a blacklist monitor to check for IP / domain / mail blacklisting would be great.
Some big web companies are hosting thousand of users and shared IPs are regularly blacklisted due to phishing or malware distribution.Similar services:
https://www.site24x7.com/tools/blacklist-check.html
https://www.inmotionhosting.com/support/tools/blacklist-check/6 votes -
International pricing
Pricing in euros is probably not intuitive to most people outside of Europe.
It would be great if we could choose to display pricing info in other popular currencies.
4 votes -
0 votes
Applied a couple week ago, no response so far.
-
Onion service support (Tor hidden service)
It would be cool to have support for Onion services, also known as Tor hidden services. These are services with domains ending in
.onion
, which are routed through the Tor network.https://community.torproject.org/onion-services/
A single location would likely be enough since the Tor network routes traffic through many nodes that may be in different countries. This location would need to run a Tor proxy, and connect through the proxy to check the status.
I've recently started running my blog as an onion service along with the regular web version, and many websites like the BBC and DuckDuckGo also have Onion…
4 votes -
Signal as an alert channel
It would be great to have Signal (https://signal.org) as an Alert Channel. Other services support this so it might be possible (e.g. https://healthchecks.io/). I find this very convenient as Signal is very popular here (and also cheaper than SMS I suppose).
6 votes -
Label (alias) for notification recipients
For notification recipients both sms and email it would be very useful to be able to label these with an alias/display name (especially for sms recipients)
8 votes -
Scan opened ports to detect firewall misconfiguration
The idea is to scan for opened ports to detect if something changes.
It will alert for firewall misconfigurations or servers configuration mistakes like a database listening to the public interface in place of the private one.
Even only one scan per day would be great.
2 votes -
Import CA for all checks, or import "valid" certificate by check
For some reason, we have certificats only valide by our internal CA Root (not validate by a CA Authority) for disable warn/fail but keep expiration feature we need one of those feature:
- import cert by service
- import ca root by account
- an interface validation to valide the actual certificate.
4 votesOne 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.
-
FavIcon
Please add option to add FavIcon to status page
4 votes -
Add Indian Location
It would be great to be able to monitor our services as they are seen by Indian customers !
4 votes -
Telegram channel posting
Current Telegram support is for either a conversation, or a group.
I'd like it to also (or rather) sent to a channel it's a posting member/admin, as there it gets less cluttered as people could use the comment discussion group for the chatter/responses
3 votes -
[Status Page] Custom public website names for status page (different from dashbord)
I love the new multi-site status page but I can't share it with the public because our internal designations for our services means nothing to the public.
I would be awesome to be able to customize website names only for status pages and keep the private names for the dashboard and notifications.
E.g: https://updown.io/p/07ws1
"lAPInou" would be displayed as "Core" or something like that, "Dsgn BI" as "3D Engine - BI", etc.Bonus points if you implement a feature so we can add a description to each website :)
6 votes -
SSL notifications recipients
SSL and domain expiration notifications recipients should be adjustable like the other checks too.
3 votes -
Capability to check UDP's ports, for services with just an udp port
For some services we have only a UDP port to check, just tcp is aviable at this moment.
3 votesIndeed 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?
-
Read-only REST API keys per check
I would like to be able to generate read-only API keys per check, so I would be able to use the API to directly show information within customers sites (WordPress Dashboard).
6 votesThanks 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?
- Don't see your idea?