As I'm sure most of you have been aware, Deepbot for the most part of the 13th January 2016 was down. This was due to an expired SSL certificate. If you don't know what a SSL certificate is it basically is a pass which tells your browser "Oh, ok, this link is secure enough to send encrypted data over" (Which is why on some sites, especially login pages, you see https:// in front of the URL). This encrypts the data you send to the API over the internet to stop those who want to acquire your data from getting it easily.
This issue was that this certificate expired. As you've travelled across the internet I'm sure you've seen your browser warn you that the site you're about to enter is untrusted. This basically means that the certificate that allows the HTTPS protocol to transfer your data securely is more then likely not going to do that so it'd make your data more susceptible to man-in-the-middle attacks. Now usually these certificates get renewed before they tend to expire but unfortunately in this case that didn't happen. This meant that the SSL certificate was invalidated.
Of course as many of you also know you were still able to connect by rolling back your system's date. Your browser only matches the date that you have set to the date that is on the certificate when deciding if the link is trusted or not which is why that little work around actually worked.
I'm sure this issue angered many of you and all we can do is apologise for the downtime you have experienced. You are paying for a program and, even though it is still in beta, you want to be able to connect 99% of the time. Basically something like this shouldn't have happened in the first place. Hopefully measures will be put in place to prevent an event like this from happening again.
Again, sorry for the downtime and thank you for your patience. Thank you for reading this if you have made it down to the bottom of this post.
Sorry,
Dante557