On November 16-17, Kami experienced a service outage due to an unexpected failure within our database. This significant service disruption drastically reduced the volume our database could handle, impacting our users’ ability to load the Kami app and successfully transfer files to our servers.
Our team identified the issue on November 16 at 11:00 am EST and Kami engineers worked relentlessly to resolve the outage as quickly as possible. Once the root cause was identified, immediate fixes to the Offline Mode feature were rolled out to minimize disruption to users. At 4:35 pm EST, our engineers saw good progress in restoring the service. However, to speed up the recovery process, Kami remained offline until service was restored on November 17 at 4:03 am EST.
Fix and prevention underway
Presently, we’re continuing to work on changes and with our database supplier to ensure that unexpected failures do not happen again in the future. We have also been making improvements to Offline Mode in order to make it more resilient.
There will also be improvements with in-app messaging to communicate any issues more quickly and informatively.In the meantime, you may view our incident report for a summarized timeline.
A message from the Kami Team
The Kami Team is deeply sorry for the inconvenience of this disruption and any stress to the community during an already challenging time.
We also want to thank you for your patience and continued support throughout the outage. We appreciate all the feedback that we’ve received and we’re committed to making more improvements as we continue to collate more information about this incident.
This blog post will be updated as more information comes to light. If you have any questions about this outage, you can reach us at email@example.com.