AdminAdrien Rey-Jarthon (CEO / Founder, updown.io)

My feedback

  1. 16 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  4 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    AdminAdrien Rey-Jarthon (CEO / Founder, updown.io) commented  · 

    Ok, then feel free to create another suggestion because it's not the same thing that is asked here.

    An error occurred while saving the comment
    AdminAdrien Rey-Jarthon (CEO / Founder, updown.io) commented  · 

    @Adrian that's a different case, this one is already possible by setting an "Alias" for your check.

  2. 4 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
    AdminAdrien Rey-Jarthon (CEO / Founder, updown.io) shared this idea  · 
  3. 1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    AdminAdrien Rey-Jarthon (CEO / Founder, updown.io) commented  · 

    Thanks for suggestion, so basically we would be talking about a TCP + TLS handshake test, the connection would then be closed before exchanging any data. Something like "echo | openssl s_client -connect updown.io:443" ? does this work well with your LDAPS?

  4. 64 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  5 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    AdminAdrien Rey-Jarthon (CEO / Founder, updown.io) commented  · 

    Thanks for bringing this one to my attention, looks nice. I'm adding it to the list of alternatives in the description too so other people can use it.

    AdminAdrien Rey-Jarthon (CEO / Founder, updown.io) supported this idea  · 
    AdminAdrien Rey-Jarthon (CEO / Founder, updown.io) shared this idea  · 
  5. 2 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    AdminAdrien Rey-Jarthon (CEO / Founder, updown.io) commented  · 

    This is already handled, the 30 days alert is disabled for short certificates like Let's Encrypt ones. If you had that problem please let me know on which site so I can have a look, otherwise I'll assume it was just speculation :)

  6. 10 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 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.

    An error occurred while saving the comment
    AdminAdrien Rey-Jarthon (CEO / Founder, updown.io) commented  · 

    "I think I misread the description of the results parameter, I thought that parameter was for historical up/down data, even though that is actually the purpose of the endpoint it belongs to…" → don't worry that's not your fault, this parameter isn't explained much and is not shown in the example because it's quite new and kind of beta so I prefer people to start using it slowly ;)

  7. 6 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →

    Hi, 2 months ago we started providing canonical URLs so search engines would only display a single result (without the localized version) but it looks like this is not enough and multiple versions are still indexed. We’ll probably add some noindex to help with that.
    On the other end we’re not gonna totally block the indexing of the main status page because this is a feature, being able to lookup a status page when the monitored service is down can be useful.

    An error occurred while saving the comment
    AdminAdrien Rey-Jarthon (CEO / Founder, updown.io) commented  · 

    Yes, thanks for the suggestion. I also think it may be interesting to only allow public status pages with custom domain (ex status.mywebsite.com) to be indexed and not the URLs on our domain (ex updown.io/ngg8). This way it keeps the client's website hostname visible and doesn't allow to list public pages in search. I'm not saying this a replacement for "hidden" status pages, more like an improvement for this initial suggestion. What do you think?

  8. 262 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    22 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    AdminAdrien Rey-Jarthon (CEO / Founder, updown.io) commented  · 

    Nothing I can show yet it's still very early stage but the work has started.

    An error occurred while saving the comment
    AdminAdrien Rey-Jarthon (CEO / Founder, updown.io) commented  · 

    Not yet, this is at the top of the roadmap but I can't give any ETA, could be a couple months or a year. If you make a status page yourself it should not be hosted on the same servers of course, you could host it for free on github for example. Also checking the global status in case of downtime is easy from your dashboard as a user. Anyway feel free to go with one of our competitors if this is important for you right now.

    An error occurred while saving the comment
    AdminAdrien Rey-Jarthon (CEO / Founder, updown.io) commented  · 

    Hello, development of this feature hasn't started yet but it is still planned.

    An error occurred while saving the comment
    AdminAdrien Rey-Jarthon (CEO / Founder, updown.io) commented  · 

    No ETA, sorry

    AdminAdrien Rey-Jarthon (CEO / Founder, updown.io) supported this idea  · 
    An error occurred while saving the comment
    AdminAdrien Rey-Jarthon (CEO / Founder, updown.io) commented  · 

    Hi, there's already a weekly email report with all you checks, but I guess you're talking about a public status page ? It'll probably be possible in the future to choose multiple checks to display on a public page.

  9. 4 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    AdminAdrien Rey-Jarthon (CEO / Founder, updown.io) commented  · 

    Thanks for the suggestion, indeed we didn't write such documentation because usually our users know when they are doing redirections but I understand it could be useful to some. I'll keep this idea open to measure interest.

  10. 14 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    AdminAdrien Rey-Jarthon (CEO / Founder, updown.io) commented  · 

    @Tony you can use https://tools.pingdom.com/ for example to get a waterfall view of the different redirection requests detailing how much time they took and from which URL you passed by.

    It's also possible with local tools like curl if you're familial with command-line (https://dev.to/yuyatakeyama/how-i-measure-response-times-of-web-apis-using-curl-6nh).

    An error occurred while saving the comment
    AdminAdrien Rey-Jarthon (CEO / Founder, updown.io) commented  · 

    Unfortunately the library we use to issue requests (libcurl) doesn't provide more detailed timings on the redirection intermediary requests, also presenting this amount of information would be much less readable so I don't think we'll do this but I'll keep the suggestion open to measure interest.

    Alternatively you can of course mesure the performance of your different redirections on your side and if you want to more detailed metrics from our locations you can contact us by email and I'll give them to you.

  11. 35 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 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.

    An error occurred while saving the comment
    AdminAdrien Rey-Jarthon (CEO / Founder, updown.io) commented  · 

    Yes, a 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.

  12. 134 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    10 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
    AdminAdrien Rey-Jarthon (CEO / Founder, updown.io) commented  · 

    That's a good point Jimmy, I'll try to add more details to the downtimes API.

    AdminAdrien Rey-Jarthon (CEO / Founder, updown.io) supported this idea  · 
    An error occurred while saving the comment
    AdminAdrien Rey-Jarthon (CEO / Founder, updown.io) commented  · 

    Good idea, if you want data you can already use the downtime API (https://updown.io/api#rest) no special skills needed, just put the url in your browser with your API key and the check token (visible on the status page URL) to get all the downtimes with precise time. You can use a json formatting extension or website to make it more readable if needed.

    An error occurred while saving the comment
    AdminAdrien Rey-Jarthon (CEO / Founder, updown.io) commented  · 
  13. 4 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    AdminAdrien Rey-Jarthon (CEO / Founder, updown.io) commented  · 

    Hello,
    Thank you for your suggestion but I'm not sure how would this make the service better to everyone?

  14. 24 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    AdminAdrien Rey-Jarthon (CEO / Founder, updown.io) commented  · 

    Thanks for the recommendations, we'll keep that in mind.

  15. 1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    AdminAdrien Rey-Jarthon (CEO / Founder, updown.io) commented  · 

    In the meantime you can ask me to bulk update for you if it's not too often ;)

  16. 14 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
    AdminAdrien Rey-Jarthon (CEO / Founder, updown.io) shared this idea  · 
  17. 6 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    AdminAdrien Rey-Jarthon (CEO / Founder, updown.io) commented  · 

    Hi Richard, these security notifications are not implemented yet (no response from SSL labs), currently we only have notification for important issues like SSL handshake error or invalid certificates. I don't see any recent SSL alerts sent on your account so I'm not sure what you're talking about, it may not be from updown.io. Please send a screenshot of the notification you're talking about if you want more information ;)

  18. 270 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  11 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    AdminAdrien Rey-Jarthon (CEO / Founder, updown.io) commented  · 

    @Frank if you publish your status page you can then share the link for read-only access to unauthenticated people.

  19. 3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    AdminAdrien Rey-Jarthon (CEO / Founder, updown.io) commented  · 

    Indeed that's a classic problem but it's better solved using the standard Cache-Control header to disable caching, and this one can already be set on updown.io using the customize request form (</> icon).

  20. 11 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    AdminAdrien Rey-Jarthon (CEO / Founder, updown.io) commented  · 

    @Mario As a first iteration, I've just reduced the white-space of the status page substantially (160px).

    An error occurred while saving the comment
    AdminAdrien Rey-Jarthon (CEO / Founder, updown.io) commented  · 

    Thanks for feedback, the problem with the prefix idea is that people will stop using it, and I'll end up with broken/ugly pages branded as updown.io all over the internet ☹

    Your suggestions are interesting though, I've already been asked for custom logo and may implement this at some point. About company colors it may be possible but again probably not a good idea if people replace the green with red for example :/ it may make the page impossible to understand. Which part would you have like to re-color?
    And finally about the whitespace I'll try to improve that on the existing design!

    An error occurred while saving the comment
    AdminAdrien Rey-Jarthon (CEO / Founder, updown.io) commented  · 

    This most probably won't happen as we don't want to have 100 different designs in the wild and risk breaking them when we do changes to the status page. Why do you feel the need to draw more attention to the translation dropdown? it uses browser locale by default so almost nobody would ever need it actually. About the whitespaces do you think there are too much is specific places or you just want to make the whole page more compact?

← Previous 1

Feedback and Knowledge Base