General

← updown.io support & feedback

How can we improve updown.io?

You've used all your votes and won't be able to post a new idea, but you can still search and comment on existing ideas.

There are two ways to get more votes:

  • When an admin closes an idea you've voted on, you'll get your votes back from that idea.
  • You can remove your votes from an open idea you support.
  • To see ideas you have already voted on, select the "My feedback" filter and select "My open ideas".
(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  1. 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:

      …
    11 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Forgot password?
    Create a password
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    5 comments  ·  Flag idea as inappropriate…  ·  Admin →
    started  ·  AdminAdrien Rey-Jarthon (CEO / Founder, updown.io) responded

    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.

  2. Warn about expiring domain names

    Domain name registration expiry notice

    44 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Forgot password?
    Create a password
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    5 comments  ·  Flag idea as inappropriate…  ·  Admin →
    started  ·  AdminAdrien Rey-Jarthon (CEO / Founder, updown.io) responded

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

  3. Log of uptime/downtime

    Maybe I overlooked it, but is there a log of the incidents available? Simply a text list of the times when a website went down, and when it was up again.

    135 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Forgot password?
    Create a password
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    11 comments  ·  Flag idea as inappropriate…  ·  Admin →
    started  ·  AdminAdrien Rey-Jarthon (CEO / Founder, updown.io) responded

    Hello everyone, I’ve just added a way to get the detailed results from the last 5 checks before downtime and recovery to the downtime API, all you have to do is add the “results=true” parameter, like this:

    https://updown.io/api/checks/yyyy/downtimes?api-key=xxxxxxxxxxxxxx&results=true

    Warnings:
    - This API is alpha version, it can still change.
    - The response can be huge, I recommend using this only when needed and with http gzip compression if you can.
    - The dual stack results (IPv4 and IPv6) will NOT repeat “body” and “received_headers” if they are the same as in the parent result record, to save space.

    Let me know what you think!

  4. Public status page with several checks

    A status page with several checks, showing daily/weekly/monthly stats for all of them.

    271 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Forgot password?
    Create a password
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    23 comments  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

General

Categories

Feedback and Knowledge Base

(thinking…)