This is an introduction to the Kolab Now roadmap, and what the future is going to bring. I’ll give you a high-level overview of our future plans.
It’ll constitute the first in a series of blog posts, and different people will speak in more detail about individual topics.
There’s been four distinct aspects of the current pandemic we’ve needed to deal with, and I’ll attempt to state where they come from, and what the consequences are or have been or will be.
Kolab Now unterstützt alle, die auf Homeoffice nicht vorbereitet sind, indem wir unseren Service für die Dauer der Krise gratis zur Verfügung stellen.
Email, Kalender, Office-Dokumente und mehr, helfen Ihnen Ihre Arbeitsabläufe auch Zuhause aufrecht zu erhalten.
Registriere dich jetzt mit dem Voucher Code KOLABFROMHOMENOW.
Dieses Angebot werden wir so lange wie möglich aufrechterhalten und nachdem sich die Lage beruhigt hat wieder entfernen.
Authorities and experts alike tell us physically staying at home is the safest thing to do for you and yours, and everyone else. Our experts want you to enjoy the same safety on the web.
We have decided to spread the burden and not the virus, and do the right thing by not opportunistically profiting off of our collective misery. We now provide a 100% discount to all new signups for as long as we can manage, or for as long as the crisis continues, whichever comes first. When things cool down, we’ll remove the discount.
At 10:23 UTC this morning, Wednesday January 29th, our environment experienced a catastrophic storage failure. The time to resolution for this underlying problem was approximately 80 minutes, and full service was restored approximately 60 minutes thereafter — 12:48 UTC.
Our annual certificate refresh is upon us.
Our terms of service state there’s basically no way for anyone to get any access to your data without us also being able to talk about the fact it happened, and further down nested in our legal framework outline do we have a list of 3 general types under which individual requests could be filed.
Like the last time we declared having made a full eclipse around the sun at an arbitrary date, here’s our statistics for 2019.
You may have noticed BitPay isn’t a payment option to our service any longer. If that’s what you wanted to be using, please read this article.
You may have seen that we had some issues with our website front page ‘https://kolabnow.com/’ this afternoon, and that it was on and off a few times.
Yes! We did some updates on the themes and color pallets. We had the new update up for a short while, but found out that our designer had ‘made a boo boo’. It took a little time to fix it and get the colors right, but everything is ok up and running again now.
During this update we did not touch the actual service ‘https://kolabnow.com/apps’ or anything even close to the data – only the front page ‘web blah’. If you were just reading your mail and going about using the service, then everything was just working as it should. Chances are, that you did not experience any issue at all.
If you were looking for anything on the front page at exactly that moment where we were moving things around, then we apologize for the inconvenience.
DISCLAIMER: No bits died or were hurt during this update.
Late Sunday night at 21:31 CET we were alarmed by lost connections. Symptoms seemed to point to a networking issue in the datacenter. Our datacenter provider was alerted, we sent our own emergency team onsite to assist in resolving the issue, and to deal with any fallout.
A faulty firewall was recovered, and mail started flowing again at around 00:10. Our ops team is now investigating why the firewalls didn’t fail over as they are configured to do in such situation.
At about 04:15, long after the system had recovered from the firewall issue, one system started to throw disk errors, which was leading to some users not being able to access the data in their folders. As this was a separate issue, the symptoms were only discovered at around 06:45, as it was assumed to be recovery issues from the previous outage. As soon as the disk error issue was realized, it was fixed and recovered. Connection to data was available again for all users at 07:10.
Where as we are still investigating the root cause for both of these issues, we can state, that no data was at risk at any time during the events.
We apologize for any inconvenience this has caused.
