AdminAdrien Rey-Jarthon (Founder, updown.io)

My feedback

  1. 85 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 →
    An error occurred while saving the comment
    AdminAdrien Rey-Jarthon (Founder, updown.io) commented  · 

    Sorry but I can't give any ETA as this will depend on the time I have and other higher priority task that comes before. If you are hesitating on switching because of this I recommend staying with your current provider until you receive an update on the status of this suggestion. Or be prepared to keep both tools for a while.

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

    Hello and thanks for your suggestion.

    The first option you're talking about where you would "refresh" the up status on your end is actually planned for later here: https://updown.uservoice.com/forums/177972-general/suggestions/5586072-periodic-task-cron-monitoring (under the name "pulse monitoring", "cron monitoring" and various other versions). I am actually gonna merge these suggestions together so you get the updates from the other suggestion and it adds up your vote too.

    Also as you said one alternative which is currently possible is to expose a small HTTP/TCP service to the outside for monitoring purpose only and configure this one in updown, some of our clients are doing this to "expose" the status of internal services. But I totally understand if you don't want to do this of course.

    In this case what I would recommend would be to use one of the existing pulse monitoring services discussed in https://updown.uservoice.com/forums/177972-general/suggestions/5586072-periodic-task-cron-monitoring before updown implements this, and once we do and if you want to consolidate everything in updown.io it should be easy to switch over.

    An error occurred while saving the comment
    AdminAdrien Rey-Jarthon (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 (Founder, updown.io) supported this idea  · 
    AdminAdrien Rey-Jarthon (Founder, updown.io) shared this idea  · 
  2. 7 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 →
    An error occurred while saving the comment
    AdminAdrien Rey-Jarthon (Founder, updown.io) commented  · 

    Thanks for the feedback!

    An error occurred while saving the comment
    AdminAdrien Rey-Jarthon (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?

  3. 1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
    AdminAdrien Rey-Jarthon (Founder, updown.io) shared this idea  · 
  4. 1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
    AdminAdrien Rey-Jarthon (Founder, updown.io) shared this idea  · 
  5. 7 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 →

    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 (Founder, updown.io) commented  · 

    Yep, some of this will likely be added. Feel free to also upvote https://updown.uservoice.com/forums/177972/suggestions/33404443 and/or https://updown.uservoice.com/forums/177972/suggestions/39625915 for other options depending on what would be best for you.

    An error occurred while saving the comment
    AdminAdrien Rey-Jarthon (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?

  6. 3 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 →
    An error occurred while saving the comment
    AdminAdrien Rey-Jarthon (Founder, updown.io) commented  · 

    Perfect, I just flipped the flag on these checks and they are now considered UP.

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

    Thank you for this new suggestion Daniel and for the detailed explanation (which is perfectly correct). This situation in particular (dual stack redirection to IPv4 only website) is on my radar because other people had the same problem and there's no easy workaround on your end (I have an internal task in my roadmap which I just linked to this suggestion and bumped the priority). I will try to tackle this problem without adding more configuration if possible but it may end-up with an option to disable redirections as you suggested.

    In the meantime there is one workaround I can offer you (and other people with the same problem if they are reading this). I have a hidden flag to disable "dual-stack" monitoring, which basically does the same as a curl without "-6" or "-4" so it uses IPv6 if available and falls back to IPv4 otherwise. So in this case it would (like a browser) use whatever is available for each hop, namely IPv6 to CF and then IPv4 after the redirection.

    If you want me to toggle this option on some of your checks please let me know which ones. We can then remove this option once I improve this case.

    PS: About the previous suggestion (https://updown.uservoice.com/forums/177972-general/suggestions/38068798-add-the-ability-to-disable-following-redirects) I got very few requests for this feature so I'm keeping it open to gather interest in parallel to this one. Though I may close it earlier if I end-up adding an option to stop following redirections.

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

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

    Hello, this is still in private beta for now as we are evaluating how reliable this is and adding support for more TLDs. If you want to be part of it let me know ;)

    An error occurred while saving the comment
    AdminAdrien Rey-Jarthon (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.

  8. 4 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    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 (Founder, updown.io) commented  · 

    What would be the use-case for this ? what would make it better than an hourly check for example ?

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

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

    @Sjon indeed in an ideal world this would be nice but as you said it doesn't play well with the minimal UI and pricing. That being said we definitely provide the IP that is monitored when you receive downtime alerts, the IP tested is visible in the list of last 5 requests. (also in the detailed results in the downtime API as mentioned in this suggestion)

    An error occurred while saving the comment
    AdminAdrien Rey-Jarthon (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 ;)

  10. 24 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  ·  4 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    AdminAdrien Rey-Jarthon (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 (Founder, updown.io) commented  · 

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

  11. 3 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  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
    AdminAdrien Rey-Jarthon (Founder, updown.io) shared this idea  · 
  12. 3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    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 (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 :)

  13. 4 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  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    AdminAdrien Rey-Jarthon (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.

  14. 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 →
    An error occurred while saving the comment
    AdminAdrien Rey-Jarthon (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 (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.

  15. 138 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    12 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 (Founder, updown.io) commented  · 

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

    AdminAdrien Rey-Jarthon (Founder, updown.io) supported this idea  · 
    An error occurred while saving the comment
    AdminAdrien Rey-Jarthon (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 (Founder, updown.io) commented  · 
  16. 4 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  ·  General » Locations  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    AdminAdrien Rey-Jarthon (Founder, updown.io) commented  · 

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

  17. 34 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 » Locations  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    AdminAdrien Rey-Jarthon (Founder, updown.io) commented  · 

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

  18. 1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    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 (Founder, updown.io) commented  · 

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

  19. 20 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  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
    AdminAdrien Rey-Jarthon (Founder, updown.io) shared this idea  · 
  20. 8 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    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 (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 ;)

← Previous 1

Feedback and Knowledge Base