Skip to content

General

95 results found

  1. New "Hidden" status between Private and Public

    I'm really needing a "hidden" status for pages, for them to be shareable (to client ..).

    Exactly on the same model that Gdrive/Gsuite :

    Private > For your eyes Only

    Public > Shareable to the world. Can be linked on a public website. Can be found and indexed by google (and you have a lot .. https://www.google.com/search?q=site%3Aupdown.io

    Hidden > Only for people who know the URL, to be shared internally. With a long hash key in url that cannot be bruteforced, with meta no index , cannot be indexed by google.

    (YES, one could find the url if they hack…

    34 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  2. Meta tag "noindex" on public status page

    It seems that Google has indexed my public status page, in all available languages. This isn't really necessary; it would be useful if there was some way for me to turn on a "noindex" meta tag, preventing search engines from indexing it.

    12 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  3. Microsoft Teams integration (not via 3rd party)

    Sending messages through a third party is not that great and imho should not be necessary for a large service like MS Teams.

    80 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  4. Having a global domain as CNAME for all status pages instead of one per status page

    I would like to be able to have "https://status.domain.com/xxxx" instead of "https://xxxx.status.domain.com" :).

    This could allow me to avoid touching my DNS all the time for every check.

    6 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)

    Although this is not an official feature, this is now possible thanks to the multi-site status page.

    If you create a public multi-site status page with a custom domain (example: demo.updown.io), you can then access individual status page from the same custom domain (example: https://demo.updown.io/ngg8), and this is true even for sites which are NOT listed on this status page (as long as the individual status page is public of course).

  5. Link to status page from apdex alert mail

    In the body of the Apdex alert mail (or maybe every alert mail?), can you include a link to the status page of that site? This makes it easy to check the current state of a site, if the mail is already a few hours old.

    2 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  ·  Admin →
  6. Allow URLs with non-ascii symbols

    Allow monitoring a URL suck as http://wikipedia.org/wiki/λ or http://wikipedia.org/wiki/🍔. It's annoying to manually have to URL-encode URLs and it's hard to see what the “real” URL is in the list when it's all percentage signs and numbers.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  7. Include small response body in notifications directly

    I typically implement a health check/status endpoint in my services, so it will return both a JSON response, and a valid HTTP status code (eg. 200 on success, 500 on error, for example).

    Thing is, when I use this in combination with updown.io, I only get notifications that specify the reason based on the error code, eg. "Internal Server Error".

    What I'd really want here is to have at least the Slack notifications include the entire response, or even just part of the response.

    I'd even be fine if it only worked like this when you use the "contains" functionality,…

    9 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)

    This has just been deployed. You’ll now find in your down alert email an extract of the response alongside the string you configured for search in updown (that was already present before). There will also be a more visible link to the details page (to check the complete response received).

  8. Add the ability to disable following redirects

    Currently updown.io will follow 302 redirects when checking if a service is up. In the curl commands that are emailed when downtime is detected, this is achieved via the -L flag. It would be good if this could be disabled, so that the actual endpoint given is tested and not the endpoint at the end of the 302(s).

    An example of when this might be useful: I have a few endpoints that simply 302 to another endpoint, which I don't maintain / own / have any control over. I'm less interested in whether those endpoints are up, and more interested…

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)

    This is now possible, the "contains" attribute can accept an HTTP status and if you specify any of the intermediary redirect status (e.g. 302, 303, 307...) then the monitoring will stop here and consider the check as UP instead of following the redirect.


    About the SSL certificate analysis, it is actually always carried on the first endpoint before any redirection, it does not follow them and never has. If you have any counter example please let me know so we can have a look.

  9. Credit Balance and Burn rate in Weekly E-Mail Reports

    It would be nice to see in the header of the report that same Credit Balance and Burn Rate that's on the header of the system's landing page. I like the low touch of the weekly report, so that I'm never logging into the system but still being let know everything is on the up and up. Knowing how much runway I have would only make it better.

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  10. Editing and Deleting multiple sites simultaneously

    Hi, my name is Von Reid and my company uses updown for site monitoring. We like it, it's been useful.
    However, I use your interface enough that I'm going to try to request a few features that will make your interface easier for use for everyone that uses it:

    • Delete multiple sites. It would be sooo much easier to delete multiple sites with 1 click instead of having to delete one site at a time and wait for it to refresh every single time. It takes forever to delete multiple sites right now, but it would be so nice to…

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)

    Hi, this has been improved, you can now edit and delete checks independently without any refresh.

    We won’t do bulk delete though as it would complexify the front-end quite a bit for a small gain.

    Also (just in case you don’t already know) if you want to edit check recipient there’s a dedicated bulk edit page where you can see which recipient is enable on which check and toggle by line / row or individually: updown.io/checks/recipients

  11. Warn about expiring domain names

    Domain name registration expiry notice

    53 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)

    This feature has now been released (disabled by default expect for people enrolled in the beta), feel free to enable it for your account! You can read the announcement here:

    https://headwayapp.co/updown-release-notes/domain-name-expiration-reminders-219006


    Also display of expiration time in the dashboard and in weekly emails has been added later: https://headwayapp.co/updown-release-notes/domain-name-expiration-247330


    And let me know what you think :)

  12. Provide virus and malware alerts

    Integrate with a third-party (for example virusdie) to provide their virus/malware scan of your website for free.

    2 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  ·  Admin →
  13. Twitter up/down notifications via DM

    Twitter up/down notifications via DM

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  14. Order of the bulk update notification recipients

    What is the current logic for the sorting of the bulk update notifications? I hope to see the same order as the 'checks page'. [ Alias / URL ]

    3 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  ·  Admin →
  15. Order by status and disabled checks

    I like ordering checks by status having the "down" first.
    It would be nice, in this view, to have the disabled checks at the bottom of the list.

    10 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  16. Choose alert recipient with API

    It would be nice to be able to choose which notification recipient (email, sms, ...) to activate/deactivate when creating a check through the API.
    For now all recipients are activated by default.

    8 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  ·  Admin →
  17. Make detailed pricing information publicly available (without registering and logging in)

    updown.io is STUPENDOUSLY inexpensive compared to most other uptime monitoring solutions available today. This is obviously one of your strongest selling points.

    So, "hiding" detailed pricing information on the logged-in-users-only page https://updown.io/credits/buy seems counter-productive. I was especially surprised by the big discounts given when buying credits in bulk. It seems to me that a version of this page (or equivalent information) should be made available for everyone, even if they haven't signed up for the service yet or are currently logged out. (This would make it easier for fans to share this information with friends or other prospective users, as…

    7 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  18. 3 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  ·  Admin →

    Hi, there is a fallback icon of course if you site don’t have any, but in you case your server does serve a /favicon.ico file which is a blank gif (not very valid), that’s why you see a blank space instead of the default icon. You should remove this gif if you don’t want it to showup.

  19. Server should return its idea of "current time" for reliable delta ("last check X seconds ago", etc)

    When I added "last check" and "next check" information on my custom status page using the API, I opted to give a handy "time delta", for instance I might say things like (paraphrased) "the last check was 04:42 ago at 00:46:08" and "the next check will be in 00:18 at 00:51:08".

    This of course requires having an idea of what the "current time" is.

    I initially used simply the (client) time at which I sent the request to the server, but obviously that's fundamentally flawed in many ways, as the client clock and server clock may not be synchronised, and…

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)

    This is a legit question and fortunately it has already been tackled by HTTP. You can find in the API response headers the “Date” field which contains the local server time. You can use it as a baseline for your time difference comparisons.

    It is not by default accessible for CORS requests but I’ve just added the proper expose header so it’s now accessible from javascript too, here is an example:

    fetch(“https://updown.io/api/checks?api-key=ro-xxxxx”).then(function(res) { console.log(res.headers.get(“date”)) })

    Feel free to use it now :)

    But keep in mind that next_check time being in the past will still happen, this is because it’s value is updated after the check, which can take time (between 0 and 30 seconds depending on the server response time and latency) So it can be up to 30 seconds late even on synchronized clock, in this case, you can display something like: “currently running” or something…

  20. Microsoft Teams integration.

    Please add support for posting status to multiple Microsoft Teams channels, similar to what exists for Slack.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  • Don't see your idea?

General

Categories

Feedback and Knowledge Base