Kami's API had slower than usual performance for 10 minutes, this incident has been resolved.
Between 2:49pm and 2:59pm Eastern Standard Time, Kami experienced slower than usual API performance, with worsening performance between 2:53pm and 2:59pm Eastern Standard Time.
This would've affected loading new documents that the offline mode could not open, affected saving work to Kami's backend, affected Turn In and assignment creation. Kami's Offline Mode would've kicked in to ensure all work is saved, and if you continue to keep the tab open, Kami will automatically retry saving all work.
We have fully recovered our Kami backend API service, and if any work remains unsaved, or not turned in, please try again. Our engineering team is closely monitoring the situation, and we're working towards resolution of its root cause.
We're sorry for the inconvenience this has caused.