General

  1. Let customers subscribe to status page

    Let people subscribe to my status page via email

    17 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  2. Time to first response

    On the dashboard it would be nice to see the timing to the first response

    17 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    7 comments  ·  Flag idea as inappropriate…  ·  Admin →
  3. Bulk add domains

    Bulk add domains

    16 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Flag idea as inappropriate…  ·  Admin →
  4. Nothing!

    Do not give in to feature creep :-)

    14 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  5. Custom CSS for Public Status Pagess

    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.

    14 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Flag idea as inappropriate…  ·  Admin →
  6. Make per-stack (IPv4/6) status more accessible

    Currently, many of the downtimes I experience affect only IPv6, whereas IPv4 continues to work as usual. However, there are currently several places in updown.io where it doesn’t distinguish between such a partial outage and complete unavailability (IPv4/6 both down). In those cases, it simply marks the check as “down”. This is a real shame given that updown.io already has dual stack monitoring out of the box and is able to show separate statuses on the dashbord like in the attached screenshot (which is awesome!). It would be extremely useful to have this data exposed elsewhere as well, in particular:

    14 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    5 comments  ·  Flag idea as inappropriate…  ·  Admin →

    Thanks for your suggestion, well actually the first part is already implemented, when you have a downtime only on IPv4 or IPv6 it’ll say “DOWN (IPv6 only)” in the alerts. I see on your accounts that you didn’t saw this message because the checks were just created and already down, and we currently need at least one successful check on both stacks before to trigger this message. But thinking about this I’m not sure why so I’ll probably change this to make in work also in your case.

    Also you’re right it should be added to the UI.

    About the API and Webhook you can already get very detailed informations about dual stack tests in the /downtimes endpoint using the “results=true” parameter. I’ll gradually make more details available to other endpoints.

  7. Multiple email addresses for the weekly report

    I'd like to be able to enter multiple email addresses for the weekly report. For example, certain department managers would like to receive a weekly report of the checks, but not be disturbed every time a check goes up or down.

    14 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  8. Add button to fire example webhook to added webhook URL

    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.

    13 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  9. Set lower bound % for uptime per project

    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.

    13 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  10. Weekly reports via Slack

    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.

    13 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  11. 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
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  12. 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

    13 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  13. TCP certificate expiry checks

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

    12 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  14. Allow custom headers in webhook requests

    It would be great if you could sent custom headers (and values) in webhook requests. This would allow you to add an API-key as a header which you can check in the system receiving the webhooks to validate it is actually the updown-io services sending the request.

    Currently this is do-able by adding a GET-parameter with a key to the webhook URL, but sending custom headers would be a more preferable option.

    12 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  15. Integration with Geckoboard

    Geckboard is a popular system to display a variety of metrics via a dashboard for the room. I understand this can probably be done with the API, but if you did a direct integration with them I'm sure you'd see your sign-ups increase since you'd be on their integration list.

    Just my 2 cents worth. :)

    12 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  16. Allow API key revocation

    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.

    11 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  17. JSON version of the status page

    Having a JSON version of the status page allows any possible integration with 3rd party tools/dashboards. Lowers the amount of API requests required to get similar content (even though I think not all of the information that is currently visible on the status page is also available using the existing API). Probably you want to put it behind the API key except maybe for public status pages.

    11 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  18. 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> -&gt; <a rel="nofollow noreferrer" href="https://example.com">https://example.com</a>
    
    <a rel="nofollow noreferrer" href="https://example.com/">https://example.com/</a> -&gt; <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
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Flag idea as inappropriate…  ·  Admin →
  19. Customise (on/off) Default Notification Channels

    I would like to set which Slack Alert Channels (but this idea applies to all notification methods) should be default on or default off.

    I have a couple of channels I need just for specific high priority notifications. I don't want them accidentally switched on for every updown.io entry that is added

    11 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  20. Negative monitoring

    I would like to have checks which fail when something is there which shouldn't be there. For example a http endpoint which should only be available through https.

    11 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

General

Categories

Feedback and Knowledge Base