Jacob Fogg

My feedback

  1. 78 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  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
    Jacob Fogg supported this idea  · 
  2. 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 →
    Jacob Fogg supported this idea  · 
  3. 294 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

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

    Feb 2021 update: A first version of the group status page feature (only the basics for now) has been released so you can give it a try!

    The link is hidden for the moment, please go to https://updown.io/status_pages to create your first status page.

    And here is a demo status page that we just created: https://updown.io/p/3ji4k

    Please give it a go and let us know what you think!

    For the record it is still possible to use our read-only API key to build truly custom status page or dashboard in javascript.

    Here are some example custom status page made by our users that you could start from:
    https://github.com/nya1/updown-status-page
    https://github.com/Hexstream/status.abc.hexstream.xyz

    Jacob Fogg supported this idea  · 
    An error occurred while saving the comment
    Jacob Fogg commented  · 

    I spent 30 minutes and $0 and setup my own multi status page using the nya1's github project. It's simple, its easy, and it works great! Simply clone the project, edit the package_config.json, make a couple projects public, configure netlify, and you are DONE!

    {
    "updown_read_key": "ro-xxxxxxxxxx",
    "twitter": "sometwitter",
    "website_name": "Site Name",
    "website_url": "https://siteurl.com",
    "logo_url": "https://www.siteurl.com/logo.png"
    }

    Thanks again updown.io!

    An error occurred while saving the comment
    Jacob Fogg commented  · 

    I would also LOVE this! I am sad though at the tone of some of these comments. I agree that you should be able to CRUSH the competition with this addition, but honestly, for this pricing model, there is already no way anyone offers both the central status page plus your level of tracking.... So I apologize on behalf of the threateners and wish them farewell while I patently await this amazing feature addition! =D

  4. 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!

    Jacob Fogg supported this idea  · 
  5. 52 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

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

    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.

    Jacob Fogg supported this idea  · 

Feedback and Knowledge Base