General
-
Allow Green Status when using letsencrypt staging CA
In dev environments is common to use the letsencrypt staging CA rather than the production one .
This CA does not verify using the standard system ca store.
Would be useful to allow marking the letsencrypt staging ca as allowed on a per check basis
1 vote -
Uptime Reports for month, year
Get Uptime report for the whole year
20 votes -
Warn about expiring domain names
Domain name registration expiry notice
47 votesFirst part of this feature has been deployed (the one fetching expiration dates from whois database) but the problem is there’s a lot of mistakes in this process because it requires parsing free-text from all different TLD whois format (which is not standard). So we’re currently making sure the data is correct (at least when we have it) and improving the parser with the values we see in the wild, to ensure we don’t send any false alarms about this when we enable the alerts (also implemented but disabled for now). Knowing this, if you want to try anyway we could enable the alerts for some beta testers, let me know.
-
Break down the time taken by redirects since they're often a key part of the user experience
Currently updown.io breaks out the time of normal requests into:
- name lookup;
- connection;
- tls handshake; and
- response time
but shows redirects as a single block of time. It would be useful to see redirects broken out the same way.
Users often type naked domains, like example.com, into browsers. That might lead to this sequence of redirects:
<a rel="nofollow noreferrer" href="http://example.com/">http://example.com/</a> -> <a rel="nofollow noreferrer" href="https://example.com">https://example.com</a>
<a rel="nofollow noreferrer" href="https://example.com/">https://example.com/</a> -> <a rel="nofollow noreferrer" href="https://www.example.com">https://www.example.com</a>(HSTS preload requires the first redirect; you can't go straight from http://example.com/ to https://www.example.com.)
Depending on how you're handling both http and naked domains the…
11 votes -
Test based on hash
It would be handy if instead of content we could choose to hash the response and test if the response matches the hash.
1 vote -
servers in hong kong and indonesia
servers in hong kong and indonesia
2 votes -
South America checkpoint
Hello, I suggest that a South American checkpoint is a priority. I have (among others) websites in Spanish and Portuguese, and although Spain and Portugal are in Europe, the majority of users in these languages turn out to be from South America. If you need a VPS in Brazil, I can recommend Virtuaserver (I had a good experience with them), or there are many others. Best wishes and keep going.
28 votes -
Add Belgium location
Add more server locations ( in particular Belgium)
4 votes -
Add notification escalation
Add notification escalation.
Add a method for responsible people to aknowledge reception of an alert. Add an escalation of alerts in case someone did not respond in due time (15 min, or parametrable).
1 vote -
Alias for alert email addresses
When using a service such as StatusPage for client updates, it provides a long unique email address for each type of alert we need to monitor. Without an alias it’s difficult to see if we are selecting the correct alert when assigning to each monitoring process.
6 votes -
@channel support for Slack integration
When a Slack notification for downtime comes through, I'd be happy to have it use @channel, to increase the chance that anyone on that channel will know about downtime as soon as possible. I don't see any way to configure that currently.
1 vote -
Custom Logo
I think a custom logo has been suggested before in a comment (https://updown.uservoice.com/forums/177972-general/suggestions/33892252-custom-css-for-public-status-pagess), just wanted to raise it a suggestion now
13 votes -
STARTTLS check for SMTP servers
Ath the moment SMTP ports may be checked for responsiveness but not for valid connections. Interesting would be:
- check if there is really a SMTP server
- check for STARTTLS
- check for valid certificate / expiring certificate
- check for MTA-STS/DANE
10 votes -
Support WebSocket endpoint
Allows to monitor WebSocket only endpoint (ws:// and wss://)
20 votes -
Full white label functionality
I want to be able to white label status pages, email alerts, etc. (total white label possibilities)
1 vote -
Allow URLs with non-ascii symbols
Allow monitoring a URL suck as http://wikipedia.org/wiki/λ or http://wikipedia.org/wiki/🍔. It's annoying to manually have to URL-encode URLs and it's hard to see what the “real” URL is in the list when it's all percentage signs and numbers.
1 vote -
Google Sheets Integration
Google Sheets integration.
We use the API now with an external Python script polling in data every x minutes to keep our overviews up to date.1 vote -
Show QUALYS SSL Labs Grade
Show somewhere on the status page, the SSL Labs grade for the monitored host. It can be get trough the API, like https://api.ssllabs.com/api/v3/analyze?host=updown.io (it could be tested once a day for each host)
6 votesYes, 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).
-
Add the ability to disable following redirects
Currently updown.io will follow 302 redirects when checking if a service is up. In the
curlcommands that are emailed when downtime is detected, this is achieved via the-Lflag. It would be good if this could be disabled, so that the actual endpoint given is tested and not the endpoint at the end of the 302(s).An example of when this might be useful: I have a few endpoints that simply 302 to another endpoint, which I don't maintain / own / have any control over. I'm less interested in whether those endpoints are up, and more interested…
2 votes -
Add name to phone numbers
Give a name to phone numbers! otherwise it's hard to know who they belong to.
2 votes
- Don't see your idea?