Anonymous

My feedback

  1. 301 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  12 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous supported this idea  · 
  2. 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  ·  General  ·  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.

    Anonymous supported this idea  · 
  3. 136 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

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

    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!

    An error occurred while saving the comment
    Anonymous commented  · 

    The data being returned in the API is super-helpful, especially the received headers! I would love to see these on the status page in some form.

    Anonymous supported this idea  · 
  4. 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  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous supported this idea  · 

Feedback and Knowledge Base