The multi-site status pages released a couple months ago now have their API so you can automate the creation and maintenance of these pages, check out the endpoints documentation here.
You can use these API endpoints to update the list/order of websites, the name and description (to automatically update in case of planned maintenance for example or known problems).
The first version of the recipients API has been released, it allows to list all possible recipients in your account (/api/recipients endpoint) and to modify the list of recipients selected for each check (recipients attribute in the /api/checks endpoints). You'll find the updated documentation here: https://updown.io/api
So you can now perform the same changes as on the bulk edit page but from the API, and thus automate the creation/update of checks while selecting only some recipients.
It is also possible to add new recipients (email, sms, webhooks, etc..) from the API using the POST endpoint.
Let me know if this is working well for your needs and if you notice any issues.
🧑🏫 Pro tip: before playing with the API and messing with your configuration, you can open the bulk edit page to have a snapshot of your current recipients configuration (as checkboxes). This way in case of problem you can just submit this form to restore the snapshotted configuration (don't reload the page before of course 🙃).
After months of development and beta testing, we are now releasing the domain expiration reminders feature publicly. The goal is to warn you a couple days before your domain expires in case you forgot to renew it. This feature is disabled by default, you'll need to enable it in your settings if you want it:
(this is because for many people it'll probably be useless and noisy)
⚠️ Note that some TLDs do not share expiration date or simply refuse to run an open RDAP or WHOIS service so this will not work with ALL domains but so far our success rate is about 80%. If your TLD supports RDAP (you can verify with https://rdap.org/domain/example.com) and gives an expiration date here you should be good to go. If your TLD does not support RDAP but responds to WHOIS queries and has an expiration date, most of them will be supported by our parser, if not feel free to open an issue or a PR or just ask us and we should be able to add support.
Since the beginning it has not been possible to specify an expected HTTP status code (though it was possible to specify a string to search in the body response, which often allowed to circumvent this limitation).
Well it is now possible to specify an expected HTTP status code (other than the default 2xx), in the same place you could specify a string to search, the tooltip has been changed accordingly:
This can be useful if you need to monitor an endpoint with a non 2xx status but which doesn't return any body (or not stable enough to match on). The error message will be the same for now: UP/DOWN (short version) or "Couldn't find the configured string" (long version) because it's simpler. I'll see about changing that a bit if it creates confusion.
We've just added support for internationalized URLs, showing unicode chars in domain names, path and query. Like in browsers, this is for display only. underneath the URL is stored normalized in ASCII format to remain valid and it is this one that is sent to your server.
You can paste an IRL when creating a new check, updown will accept it and convert it to the appropriate format automatically (this is also true for ASCII characters which are not allowed in URLs).
It's possible there are still some places where the ASCII version will be shown instead of the unicode one. As always, let us know if you have any feedback about this new feature.
We've been using UserVoice for quite some time for feature suggestion, FAQ and customer support contact widget:
The thing is in the end this was just a very limited UI for an email, as support is anyway handled the same way and by the same person (me) on support@updown.io.
And among the years we hit some deliverability issues, likely caused by UserVoice not supporting proper DKIM signing. Also some clients had bad experience because they thought this was a live chat. Overall many opportunities for frustration.
So in order to address this problem in the simplest way possible – and as UserVoice is not gonna change soon – I decided to stop using this widget in favor of direct email. Twitter is also an option for people still using it ☺
I slightly reworked the footer to make the Support button more visible to compensate for the widget button being gone, also it'll now includes the account name in the subject by default:
For a while, French clients have benefited from a 0% VAT because we were VAT exempt in France 🥖 but unfortunately good things don't last forever. updown revenue keeps increasing (thank you 🙇), this means we are no longer VAT exempt and have to start collecting the French VAT (20%) for individual and company purchases from France, starting September 1st 2021.
↻ Note that if you have auto-renew enabled, the subsequent payments after September 1st will automatically include the VAT.
Do not hesitate if you have any questions.
After a couple months of private beta we are now releasing multi-site status pages (example):
You can choose the title, description, list of checks to show and customize the order. It's also possible to serve them from a custom domain like we did for single-page status pages. By the way if your single-site status pages are public, they'll be accessible from the multi-site status page. You should easily find the new feature in the (slightly reworked) top menu:
This was one of the most requested features of all time, and more options will surely come later. Let us know what you think and what you would like to see in the feedback tool or by contacting us.
Also part of this release is a new system to connect custom domains to single-site or multi-site status page, using an additional TXT record instead of only one CNAME:
The advantages are:
Don't worry the previous system using only one CNAME is still working and will not be removed anytime soon but you are encouraged to use the new one. The new setup page (which should make it easier to debug problems by the way) will only help you using the new way.
We've been using BitPay to accept Bitcoin (BTC) and BCH payment for a while now, but they recently broke our account, without any reason or warning, their support is not responding (of course) and considering the poor reputation and compatibility they created, we didn't even care wasting our time trying to get it back.
Instead we worked on replacing them by a new provider, and took this opportunity to improve our cryptocurrency support. We searched for a solution with at least:
After some research we settled on CoinGate as our new provider, they checked all the boxes and even support a lot more altcoins. So starting today you'll find a new payment form which should be easier to use:
(the email address is not required)
Please give it a try and let us know if you have any problem with this new provider or if you would really like to use another altcoin not supported here.
Recently, Let's Encrypt started generating certificates with a new intermediate (called "R3") in which they decided to stop supporting OCSP (which is one protocol allowing to check for a certificate revocation individually) in favor of CRL (another older protocol allowing to get a list of revoked certificates) for the intermediary certificate.
The library we built to detect certificate revocation only supported OCSP up until now, so after checking your certificate successfully, when checking the intermediary (R3) it failed because it didn't find an OCSP endpoint. Because of this you may have seen this warning recently:
Up until now it was very rare for certificates not to offer OCSP, that's why we didn't implement CRL yet. But this new intermediate from Let's Encrypt (which represents more than 30% of all certificates on updown.io) pushed us to add support for CRL to our library. This is now done and deployed, so this warning on your certificates will disappear soon (at the next test).
Note: this change will also helps with a couple other Certificate Authorities (other than Let's Encrypt) which were already doing this, and also the ones which will follow Let's Encrypt move in the future.
If you still have some OCSP or CRL warnings on your certificates after that, and you're not sure if it's your Certificate Authority's fault, do not hesitate to ask us!
