Here are some example custom status page made by our users that could start from:
Nothing I can show yet it's still very early stage but the work has started.
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.
Hello, development of this feature hasn't started yet but it is still planned.
No ETA, sorry
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.
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.
@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).
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.
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.
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.
Indeed this is not currently possible, there’s just the 6 months view with downtime duration per day and 24h timeline with detailed downtimes. But this is planned, I’m currently working on adding detailed failing requests to downtimes email and will later add a downtime history on the status page.
That's a good point Jimmy, I'll try to add more details to the downtimes API.
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.
@Lars yes, that's in another idea you can vote for: https://updown.uservoice.com/forums/177972-general/suggestions/15589635-allow-text-updates-for-incidents ☺
Thank you for your suggestion but I'm not sure how would this make the service better to everyone?
Hello and thank you for the suggestion. Doing special treatment for monitoring endpoints (versus website pages) is too specific and error-prone so we’re not gonna do that.
One thing which might be done to help in this case is display the response body when using the contains feature but this only makes sense if it’s small and simple (no html). How does yours look?
Ok thanks, I'll see what I can do
Thanks for the recommendations, we'll keep that in mind.
In the meantime you can ask me to bulk update for you if it's not too often ;)
11 votesAdminAdrien Rey-Jarthon (CEO / Founder, updown.io) shared this idea ·
Yes, I want to do it for a long time but the Qualys API is not free to use for commercial projects so I need to discuss with them (this is currently in discussion).
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 ;)
@Frank if you publish your status page you can then share the link for read-only access to unauthenticated people.
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).
@Mario As a first iteration, I've just reduced the white-space of the status page substantially (160px).
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!
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?
Interesting, as an alternative currently you could define aliases on your checks which mention the top level first and subdomain after (ex: "hexstreamsoft / mail") to have this kind of ordering.
What do you mean?
Ok then you're not looking for the TTFB but for the server response time (in green on updown.io status page) this one does not include connection and handshake, though it still includes the network latency in addition to the server time as we can't get the exact server time from a remote location. But if you look at the number from a close location (small connect time) or if you subtract the connection time, you can get a pretty good idea of the server only response time.
Response time does include the download but it doesn't include the connection and handshake time, whereas the TTFB from chrome does include these but not the download time. As this is server to server the download time is most of the time negligible, unless you're bandwidth constrained, so the number you're interested in would be the total time.
This one is not included in the dashboard because it's very location dependent of course and showing and average may not be very clear, whereas on the status page as there's the detail per location it is clearer.
Do you think we should put something like the total time average in the dashboard? when you say dashboard are you talking about the status page or the list of checks in your account?
What do you mean exactly by "the timing to the first response" ? Which number would it be from the detailed timings chart? (ex https://meta.updown.io/)
Thanks for your feedback, I just wanted to point out that with the recently added bulk update interface (https://headwayapp.co/updown-changelog/bulk-update-notification-recipients-54559) it's much easier to edit this kind of things.
Hello, raw access is already possible using the API: https://updown.io/api
Using the /metrics endpoint you can get the apdex per host or per hour for any timeframe you want (minimum resolution is hour though). History is kept forever but aggregated, so you get per-hour data for at 1 day, then per day data for a month and then per month data.
What would this be useful for?
Ok I see, about the slack channels though @Matt this is now possible to have multiple slack channels and select were each check's notification go to (released about 2 months ago)