Is Kami Down Right Now? Check if there is a current outage ongoing.

Due to an ongoing Google Cloud Outage: https://status.cloud.google.com/ we are currently experiencing degraded performance from certain features within Kami. Loading Files from Google Drive Updating Kami Share Link Sharing Settings for Drive files. Kami AI Tools Kami Companion Beta tools. We're currently investigating the issues and seeing if there is anything we can do to restore functionality. We'll keep you updated on any progress, and if you have questions or concerns, please reach out via "support@kamiapp.com". Thank you for your patience and understanding, and best wishes! The Kami Customer Success Team

We are resolving the incident as we have confirmation a fix is on the way, and will update affected users once that has been released

We've identified an issue with our Microsoft Teams Integration. The "Kami Button" under "Apps" in the Microsoft Teams Assignment page does not function. This is affecting both the Teams App, and Teams with Browsers. You are still able to view the student work and access Class-View via clicking the "Take Action in Student View" button, and then clicking the Kami Button there.

We've identified an issue with our Microsoft Teams Integration. The "Kami Button" under "Apps" in the Microsoft Teams Integration does not function when clicked by a teacher viewing the student Submissions. This is affecting both the Teams App, and Teams with Browsers We have escalated the issue to Microsoft and are working with them on a fix, which we hope to have out this week. You are still able to view the student work and access Class-View via clicking the "Take Action in Student View" button, and then clicking the Kami Button there. We completely understand the frustration that this has caused, and are working to get things up and running again as soon as possible. If you do have any questions or concerns about this, please reach out to support@kamiapp.com, and we'll be happy to help. Thank you for your patience and understanding, and best wishes. The Kami Customer Success Team.

We are resolving the incident as we have confirmation a fix is on the way, and will update affected users once that has been released

We've identified an issue with our Microsoft Teams Integration. The "Kami Button" under "Apps" in the Microsoft Teams Assignment page does not function. This is affecting both the Teams App, and Teams with Browsers. You are still able to view the student work and access Class-View via clicking the "Take Action in Student View" button, and then clicking the Kami Button there.

We've identified an issue with our Microsoft Teams Integration. The "Kami Button" under "Apps" in the Microsoft Teams Integration does not function when clicked by a teacher viewing the student Submissions. This is affecting both the Teams App, and Teams with BrowsersWe have escalated the issue to Microsoft and are working with them on a fix, which we hope to have out this week.You are still able to view the student work and access Class-View via clicking the "Take Action in Student View" button, and then clicking the Kami Button there.We completely understand the frustration that this has caused, and are working to get things up and running again as soon as possible.If you do have any questions or concerns about this, please reach out to support@kamiapp.com, and we'll be happy to help.Thank you for your patience and understanding, and best wishes.The Kami Customer Success Team.

This incident has been resolved.

We've now made a couple of changes on the backend that should have mitigated the issue. If you are still experiencing any issues, please reach out via support@kamiapp.com, and we'll be more than happy to help! Thanks again for your patience while we've figured this out, and best wishes! The Kami Customer Success Team.

We are aware that several Kami users are reporting Kami running incredibly slowly, and struggling to load and view files. Our Developers have been notified and are looking into the cause now. As soon as we have an update on what's caused this, and any potential fixes, we will let you know. Thanks for your patience while we figure this out! The Kami Customer Success Team,

This incident has been resolved.

We've now rolled back the change that we believe was responsible for the performance issues in Kami. Everything looks to be back up and running smoothly, however, we'll keep monitoring to make sure everything is working as expected. If there are still any issues please reach out via support@kamiapp.com, and we'll be happy to help! Thanks again for your patience and understanding, and best wishes! The Kami Customer Success Team.

We've identified the change that has caused these performance issues and are working on a fix for the issue now. All tools and features are still working, but slower than expected. Annotations will also save eventually, but please stay on the page until you see the “all changes saved” message. We are still monitoring Kami's performance for any changes as we We'll keep you updated on the progress of that fix, and are doing all we can to get this back up and running for you. Thank you for your patience and understanding while we figure this out! The Kami Customer Success Team

We are aware that Kami is currently experiencing reduced performance when it comes to loading files, saving annotations, and exporting documents out of Kami. All tools and features are still working, but slower than expected. Annotations will also save eventually, but please stay on the page until you see the “all changes saved” message. Our developers are aware of the issue and are investigating the cause now. As soon as we have more information, we will update everyone ASAP. Thank you for your patience and understanding while we figure this out! The Kami Customer Success Team

This incident has been resolved.

We've released a change that should fix the issue, and student work should now be accessible again. If you are still encountering this issue, please reach out to us on support@kamiapp.com, and we'll be happy to look further into that for you. Once again, thank you so much for your patience and understanding while we've sorted this out. Best Wishes! The Kami Customer Success Team.

We've identified an issue with our fix for the outage earlier this week that has caused Teachers to encounter an error when opening student work in Assignments created using the Kami Google Classroom Add-on. Students are still able to complete and submit the work without issue. We've figured out the cause, and are working on releasing a fix for that as soon as we can. Thank you for your patience and understanding while we get things up and running smoothly again. The Kami Customer Success Team

This incident has been resolved.

The cause of the error has now been resolved, so we are monitoring for any further occurrences, If you are still encountering any issues, please let us know via support@kamiapp.com, and once again, we greatly appreciate your patience while we sorted the issue out. Thanks, and best wishes! The Kami Customer Success Team

We've identified the cause of the error message, and are working on a fix for it now, which we hope to have ready to good very soon! As soon as that is live, we'll update you again, and once again, really sorry for the disruption. Thank you for your patience and understanding while we sort this out! The Kami Customer Success Team

We've received multiple reports from users that when using the Google Classroom Kami Add-on, students encounter an "Error loading document through Google Classroom" message when opening their assignments. We are investigating this issue now, and are working on confirming the cause and we will update you as we learn more, as well as progress on any fixes. Thank you for your patience while we sort this out! The Kami Customer Success Team

We've confirmed that our fix has resolved the issue, and Kami should be back up and running as usual now! If you are still encoutering any issues, please let us know via support@kamiapp.com, and we'll be more than happy to help! Thanks again so much for your patience while we fixed this, and best wishes! The Kami Customer Success Team

We've now identified and implemented a fix for this issue, and are monitoring for any further issues with loading Kami. Please reach out to support@kamiapp.com if you are still encountering any issues! Thanks again for your patience while we get things back to normal.

We are aware that Kami is experiencing intermittently slow loading and issues with opening files the Kami platform as of 12:00 PM Eastern Time / 9:00 AM Pacific time. Our engineers are looking into this now, and we will update you as soon as we have more information. Thank you for your patience while we troubleshoot this.

We are aware that Kami is experiencing slow loading and issues with opening files the Kami webpage as of 12:00 PM Eastern Time/ 9:00 AM Pacific time. Our Developers are looking into this now, and we will update you as soon as we have more information. Thank you for your patience while we troubleshoot this,

We've now confirmed that Short.io's fix has worked, and that the links created during the outage are now working. If there are any ongoing issues with these links, please reach out to support@kamiapp.com. Thanks again for your time and understanding The Kami Customer Success Team.

Short.io has released a fix that has resolved the issue. Sharing links should now be working again, but any links created during the outage (8:18 PM UTC - 8:28 PM UTC) may still be broken, and need re-creating. If there are any ongoing issues with these links, please reach out to support@kamiapp.com. Thanks again for your time and understanding The Kami Customer Success Team.

Due to an outage with our Redirection Service, Kami Sharing Links, and other shortened links starting with kami.app may not be working, instead showing an "Internal Server Error" message. We're waiting on more information from their team regarding the outage, and as soon as we have an update we'll let you know. We appreciate your patience and understanding. The Kami Customer Success Team.

The Google Drive Outage has now been resolved, so Kami s now functioning as expected. If there are any further issues, please reach out to us via support@kamiapp.com! Thank you for your time and patience, and best wishes! The Kami Customer Success Team.

Due to an ongoing outage on Google Drive affecting file uploads, users uploading or exporting files out of Kami into Google Drive may experience issues where the files fail to upload. This is happening intermittently and is waiting on the resolution of the outage on Drive's side. We are aware of this issue and are monitoring it now, and as soon as we have an update, we'll let you know. Thanks for your understanding, and best wishes! Kami Customer Success Team

This incident has been resolved.

Kami IS NOT affected by the global CrowdStrike-caused outage. Our systems remain active and are fully operational. Kami Engineering will closely monitor for issues that might be related to this outage, such as Microsoft Azure, Microsoft 365, and Microsoft Single-Sign-On as our customers may rely on these systems along with Kami. So far we have not received reports that those systems have been affected. We will provide updates as this situation develops.

Due to a networking issue with Google Cloud, saving, exporting, and turning in OneDrive files was likely to fail starting at April 23 3pm Eastern Time. We have now mitigated the issue.

The recents list is now restored.

We're investigating an outage that started at 7:40 PM Pacific time. This was affecting our backend, so logging into Kami and loading documents were affected. Kami's offline mode automatically kicks in to ensure all work is saved. From 8:35pm Pacific usual Kami functionality is restored, although you may notice some items are missing from your Recent documents list - full recent list functionality will be restored shortly.

Our engineers have been monitoring Kami's health metrics, and as of 01:01 PM Pacific Time, we saw a full recovery of the Kami app to normal levels. This outage was caused by an issue that occurred on our side while running a database query. If you continue to experience issues, please email us at support@kamiapp.com so that we can track down the root cause. We're sorry you experienced this outage, and we want to thank you for your patience as we worked to resolve it. Correction

We've identified the cause of the outage now, and at 01:03 PM Pacific Time, we've seen the API has recovered, and our error rates have decreased. We're still monitoring the situation, but the outage appears to be resolved. We're seeing the success rate of document opens, login rates and annotations being saved are now improving to normal levels.

We're investigating an outage that started at 12:41 PM Pacific time, our engineers were alerted to the issue about 5 minutes later, and have been investigating the issue since. This is affecting our backend, so logging into Kami and loading documents are affected. Kami's offline mode should automatically kick in to ensure all work is saved. We will update you once we have more information.

Engineers have been monitoring Kami's health metrics, by 8:21am Pacific Time / 11:21am Eastern Time, we saw a full recovery of the Kami app to normal levels. This outage did appear to be caused by an outage by Google SSO APIs. If you continue to experience issues, please email us at support@kamiapp.com so that we can track down the root cause. We're sorry you experienced this outage, and want to thank you for your patience as we worked to resolve it.

We've identified our outage is being caused by Google SSO backend API was down. At 8:21am Pacific Time, we've seen that API recover, and our error rates have decreased. We're still monitoring the situation, but the outage appears to be resolved. We're seeing success rate of document opens, login rates and annotations is being saved improve to normal levels. Correction to previous post, this incident started at 7:35am Pacific Time.

We're investigating an outage that started at 7:35am Pacific time, our engineers were alerted to the issue about 5 minutes later, and have been investigating the issue since. This is affecting our backend, so logging into Kami and loading documents are affected. Kami's offline mode should automatically kick in to ensure all work is saved.

The fix for the bug preventing Kami questions from displaying correctly has now been released and they should be working as expected. If you are still experiencing any issues, please update the page using the link here: https://web.kamihq.com/web/update_app.html and if the issue persists, please reach out to support@kamiapp.com. Thank for your patience while we've sorted this all out!

We've been informed that several users are experiencing issues with students being unable to see Kami Questions annotations when Opening assignments. The issue was caused by an update done before Christmas that changed how those annotations were exported, meaning they would not show correctly on new copies of the file. Our Developers have identified the issue now, and we are working on a fix that should be released by EOD today. If you have any questions or concerns, please reach out to Support@kamiapp.com

During an update to our Production Database, a Google update rolled out that caused several Database nodes to restart, but not turn back on effectively. This caused an issue where due to the lowered capacity, several Kami Services were slowed, or stopped working, including: Sign-up/Login Loading Files from Google Drive, OneDrive, or the device's local Storage Creating Kami Assignments through the LMS integrations Saving annotations Turning in Assignments. The issue has now been resolved, and all services have been restored.

This incident has been resolved fully. Thank you for your patience and apologies for the slight disruption of services.

A fix has been implemented and is looking like it has solved most of the issues with the exception of tools.kamihq.com, which covers our Split & Merge, Text Recognition, and Header & Bates. We expect this tools service to be back online soon.

We are currently investigating a major issue that caused the Kami API and Web app to be inaccessible right now.

Thank you for your patience! We have released a fix for this issue and confirmed that it is working as expected. For any users, the issue lingers for, please try clearing the browser cache one last time, and contact us at support@kamiapp.com if there are any outstanding issues. And once again, thank you so much for your patience and understanding while we've sorted this all out.

We are continuing to work on a fix. If you are experiencing this issue, please clear your full browser cache (including both "Cached images and files" and "Cookies and other site data") and choose "All time" for the time range. Restart the browser and then load Kami again. This method has worked on most users. If it doesn't work for you, please contact support@kamiapp.com to let the team know. We sincerely apologize for this disruption.

We've identified the issue, and it's caused by a corrupted cached file on our CDN. So this no longer affects new users loading Kami, but any affected users should still clear their full browser cache (including both "Cached images and files" and "Cookies and other site data"), restart their browser and then load Kami again. We have reports of users who tried these steps which resolved the issue We're sorry for the inconvenience. Our engineers continue to monitor the recovery. Please email support@kamiapp.com if you have any questions.

There's an issue where a release we rolled out is causing issues for our users. Symptoms are blank pages or a weird styling issue where it Kami partially loads. We're investigating all reports of this, but so far affected users are reporting that fully clearing their browser cache will resolve it. We don't think that going go https://web.kamihq.com/web/update_app.html or https://web.kamihq.com/web/clearcache.html will fix this because the files corrupted files appear to remain cached by the browser.

The Add Page error issue has been resolved.

The issue with Add Page has been identified and a fix will be deployed soon.

We are currently investigating an error that is appearing when you try to add a page to your document.

Fully resolved. dThank you for your patience and for understanding. If you have any questions, please feel free to email support@kamiapp.com

In our monitoring and testing, we believe this Office 365 outage has been resolved by Microsoft. Our teams will continue to monitor the recovery. Thank you for your patience and for understanding. If you have any questions, please feel free to email support@kamiapp.com

A Microsoft 365 Services Outage is affecting some of the available Microsoft OneDrive Integration for Kami. Affected Services Include: - Loading and Saving Files from Microsoft OneDrive - Microsoft OneDrive Assignment Creation for Schoology and Canvas We are monitoring for updates from the Microsoft Team, and will resolve this once everything is back up and running. For up-to-date info on the Microsoft outage, please see their Status page here: https://status.office365.com/ Thank you for your patience and for understanding. The Kami Customer Success Team.

This incident has been resolved.

We're seeing good progress in the status of resolving this temporary issue at midnight Pacific time. If you're concerned about lost work, email us at support@kamiapp.com and link this page as reference: https://status.kamihq.com/incidents/hkg4mryvb9kl

Kami has encountered an issue impacting our platform's ability to communicate with Google. This temporary issue will be automatically resolved at midnight Pacific Time. Until then, Google Classroom users may experience limited functionality, including being unable to create assignments. Our team is already hard at work to avoid this issue in the future and ensure Kami continues to provide you and your students with a reliable and uninterrupted learning experience. We apologize for any disruption this may cause.

This incident has been resolved.

API Performance has returned back to normal and we are continuing to monitor. Please keep your Kami tabs opened to ensure that all of your work saves back to our servers.

We're currently investigating a major API outage on the Kami API. Kami's offline mode will continue to work for any file you have open or have previously opened, although Kami will behave slower than usual because of the nature of the outage. Engineers are are working on a resolution. We're sorry about the inconvenience this is causing.

From 6:55am to 8:00am (Eastern Time) Kami experienced issues with our infrastructure which meant that document exports, Google Drive and OneDrive file saving, and realtime notifications for document updates were delayed or would not complete. We have resolved the issue and all features are working normally now.

Loading error rates have now returned to normal so we are resolving this incident. We will continue to monitor for any issues.

We're currently monitoring this issue, as there may have been a change on Google's Side that's allowing these files to be loaded without issue. If anyone is still encountering Network Issues with loading files, please reach out to support@kamiapp.com, and we'll be happy to look further into that. Thank you again for your patience and understanding!

We are continuing to work on a fix for this issue.

We've rolled back the fix that caused this issue now, so access to those files should be restored. Please note that this does mean that any files affected by the earlier issue today (6:30 PM - 9:09 PM UTC ) will re-encounter the network error when opening the file Our Engineers are working on an updated fix that should prevent either error from occurring, and we'll update you once that is released. Thank you again for your patience and understanding while we resolve this.

We received a number of reports that the fix we released for the earlier Network issue may be causing loading issues with other files from Google Drive. Our Engineers are actively looking into this now to figure out what has caused this issue, and we'll be releasing an update shortly to try and resolve this. Please note this does mean that the files that were affected by the original issue may re-encounter this error, but we are working on getting everything back up and running. We are again really sorry for the inconvenience that this has caused. Thank you so much for your patience and understanding.

This fix has been released and is holding steady, so we're considering the issue resolved.

We've released a fix for the issue now that should allow those files to load going forward. We'll keep monitoring to make sure the fix holds. Please let us know if there are any further issues via "support@kamiapp.com" and we'll be happy to look further into this. Thanks again for your patience and understanding while we got to the bottom of this and got things back to normal.

Our Engineers have investigated this issue, and figured out what's going on. it appears that Google has flagged a number of files as Malicious Content/Malware, and is blocking them from being opened. Currently, the best workaround for immediate access is to download the file to your device and open it from there into Kami. We understand this isn’t ideal and are still looking into solutions now. We’ll keep you updated on any progress on a resolution and will have things back to normal ASAP. Once again, we’re really sorry for the inconvenience. Thank you so much for your patience and understanding,

We are still looking into this issue with Google Drive files to determine what is causing the error, and how we can get things back up and running normally. If you require immediate access to the file, downloading it to your Device and opening it into Kami directly does work to open the file. Our Engineers are still diving into the problem, and we'll provide an update as soon as we know more. Thank you for your patience and understanding while we work this out and get service back to normal!

We are currently aware that a number of users are experiencing "Network Errors" with loading files from their Google Drive. OneDrive and loading files from the Device's local storage are unaffected. Our Engineers are actively looking into what has caused that issue now and we'll update you once we have a better idea of what's causing this. If you do encounter the issue, please let us know via our support email support@kamiapp.com. Thank you for your patience and understanding while we get this back up and running!

The Canvas issue seems to have been resolved not too long ago. After multiple tests on our end, we have determined that it is safe to move this incident as "Resolved". We appreciate your patience and understanding with this incident.

The Canvas issue seems to have been resolved not too long ago. After multiple tests on our end, we have determined that it is safe to move this incident as "Resolved". We appreciate your patience and understanding with this incident.

We've confirmed that this is a canvas issue which is also affecting other integrated apps. We have informed Canvas of the issue - if you are experiencing this, please also submit a support ticket with them.

We are seeing issues with the creation of assignments with the Kami Canvas integration where after selecting the file the process becomes stuck at a "Retrieving content..." screen. This appears to be caused by an issue with Canvas and we are investigating further.

Cloudflare is now reporting the issues as fully resolved on their end, so everything is stable and back to normal. Thank you for your patience while we've monitored this. For any other questions or concerns, please reach out to us by sending an email to support@kamiapp.com. Thanks again!

Cloudflare looks to have released a fix for the outage, and service has been restored, but we're monitoring until Cloudflare updates its status for the issue to be resolved.

We have identified an outage of the Kami main app ( https://web.kamihq.com ) caused by the global Cloudflare outage currently in progress. We are monitoring the situation and will update when we have more information.

Good news, after multiple tests and with the help of our awesome Kami community, we can confidently say that the issue is resolved. We are all grateful to all the people who reported this issue right away and have kept their patience and understanding on this matter while we resolve the issue. Sincere apologies for the trouble this has caused. We will continue investigating why this issue has happened and will make sure changes are made to avoid this from happening again. For any other questions or concerns, please reach out to us by sending an email to support@kamiapp.com

An update to the app has been deployed that will fix the issue of "The app is blocked" by Google authentication. Please make sure to refresh your app to automatically get this update, or use this link to get the update manually (copy and paste this link): https://web.kamihq.com/web/update_app.html If you are still experiencing any issues after using the update link provided above, please reach out to us by emailing support@kamiapp.com with the details and a screenshot of the issue. We appreciate your understanding and we apologize again for the trouble this has caused.

We are continuing to monitor for any further issues.

An update to the app has been deployed that will fix the issue of "The app is blocked" by Google authentication. Please make sure to refresh your app to automatically get this update, or use this link to get the update manually: https://web.kamihq.com/web/update_app.html If you are still experiencing any issues after using the update link provided above, please reach out to us by emailing support@kamiapp.com with the details and a screenshot of the issue. We appreciate your understanding and we apologize again for the trouble this has caused.

We are continuing to work on a fix for this issue.

The issue has been identified and a fix is being implemented.

Thank you for all the quick reports about this issue. We are now aware of it and our team has identified a recent release that has caused this. We will revert this change immediately to fix the issue right away and do our thorough investigation afterward for the recent update that has caused this. We apologize for the inconvenience this has caused today.

This incident has been resolved.

We are still monitoring the status. If the app triggered an offline mode, it should successfully go back online and saved any changes you made. If it does, you can safely continue working with the app again without worrying about losing any work. If you were not doing work with a file in the app but rather using other features of the app that have failed (opening a document, creating a Kami assignment, loading a file, etc.), please do try it again, it should work this time. Any other issues, please do contact us at support@kamiapp.com

A fix has been implemented and we are monitoring the results.

The issue has been identified and a fix is being implemented.

We are currently experiencing an issue with our API performance. Our team is currently investigating and has been applying fixes to get performance back to a stable status. The use of the app is affected while this issue is unresolved. Please do not close any unsaved changes you have made and temporarily halt the use of the app to avoid any further chance of losing work. Email support@kamiapp.com for any other queries.

This incident has been resolved.

The fixed version v2.0.15112 has now been approved by Google and browsers will automatically update to this version. Thank you for your patience, and our teams will continue to monitor the issue closely to ensure no other issues pop up. Please email us at support@kamiapp.com if you have questions, or other issues we can help with.

We've identified the issue, it's related to a recently Kami Extension update v2.0.15110 we did to fix Kami on Schoology Elementary Mode. To fix this 'Open with Kami' bug we'll need to do a new extension update. The previously released, Kami Extension v2.0.15049 remains unaffected. This doesn't affect assignment creation or our integration to the grader on the teachers side. We've developed a fix, we'll be working as quickly as possible to get it out to everyone, but a Chrome Extension update will probably take up to 24 hours for Google to approve the update. Please look at for Kami Extension v2.0.15112, which contains the fix. WORKAROUND: Please use Kami's share button in the top right corner, and share out a "Anyone with the link" and "Create individual copy". We're sorry about the impact this is causing, and we'll continue to work on ways to minimize the impact.

We're getting reports that Kami's Schoology integration isn't working. This appears to be related to our "Open With Kami" buttons not appearing. Our team is investigating the issue. We're sorry for the inconvenience.

The Kami API recently went down for all users between 11:32 pm and 11:47 pm Eastern Standard Time. This has now been resolved, and our engineers are keeping a close eye on things to make sure there aren’t any further disruptions. During the outage, all API requests were affected, including any new assignment creations or document uploads; new annotations and modifications; saving and exporting work. As normal, Kami's Offline Mode kicked in to protect your open documents and auto-save any progress locally. Please keep your Kami tabs open in order for all changes to be synced to our servers. If you’re having any further issues, please don’t hesitate to get in touch with our Customer Success team at support@kamiapp.com. We’re sorry for any disruption or inconvenience this outage might’ve caused – Kami’s now back up and running as normal!

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.

Kami experienced a Minor outage from 10:12 to 10:24 EST ( 7:13 to 7:24 PST). This would have affected all API requests, which means it's affecting all assignment creation, document loading, creating and modification of annotations, and saving and exporting work.

We've resolved the outage, and we’re sorry for the inconvenience that this caused. If you completed work during the last hour, as a precaution, please make sure you double check all of your work has saved, turned in or exported correctly. This outage affected Kami from 3:53pm to 4:19pm Eastern Standard Time / 12:53pm to 1:19pm Pacific Standard Time. We'll be investigating and resolving the root issues that lead to this outage. If you are encountering any further issues, please contact us on support@kamiapp.com so we can investigate further.

Our engineers have identified and are actively resolving an API outage. This appears to affect all API requests, which means it's affecting all assignment creation, document loading, creating and modification of annotations, and saving and exporting work. Kami’s offline mode will automatically kick in to ensure that your work is saved locally. Please keep your Kami tab open so that we are able to sync all of your work once this outage is resolved. We are sorry for any disruption this may have caused. We have now confirmed that Kami is back up and running with a temporary fix in place.

We've rolled out a fix for both issues. To get the update, please refresh Kami, and the app will then automatically download the update. It should automatically refresh the Kami page again once it's updated. We're actively monitoring for any new issues. Please email us at support@kamiapp.com if you're encountering another problem. Sorry again for the disruption this has caused. Edit: We've discovered another issue where the Turn In button dropdown will say "We couldn't load this assignment. Please refresh and try again". This bug has been fixed as part of the latest update.

We've identified two separate issues with a new release of Kami where 1) New changes to pre-made fillable text boxes are not triggering a "save" and causing our users to lose work on those fillable boxes. The workaround is to use our Kami "text tool" instead and type into the Kami textbox to save that work. 2) Images from the original document are not rendering, so the pages appear blank. There are no current workarounds. Our engineers are actively working on fixes for both cases. If you have an issue unrelated to these two issues, please email us at support@kamiapp.com so that we can investigate further. We're sorry for the disruption caused by these bugs, we hope to automatically roll out an update to fix them soon.

The chrome extension update has been approved and is rolling out now. You should see it automatically update within the next few hours, if you haven't seen the update you can try the instructions here: https://support.cloudhq.net/how-to-manually-update-chrome-extensions

We have developed a chrome extension update to fix this issue and we are currently waiting for Google to finish reviewing it.

We've been made aware of an issue where the "Create Kami Assignment" button in Google Classroom is missing for teachers. The fix will come in the form of a Kami Chrome Extension update, we’ll keep you updated as the fix progresses. The best workaround is to go to Kami’s Dashboard > Create Classroom Assignment. Or you can go directly using this link https://web.kamihq.com/web/viewer.html?open_dialog=create_assignment You’ll need to select your class in the top right corner. This will provide you with the same dialog you'd expect to open from the missing button. We’re so sorry for the disruption – we know how busy you are and how even the littlest hiccup can affect your day; we’ll be working ‘round the clock to get you back to business in no time.

Our incident has been largely resolved as AWS' outage has resolved. We've seen error rates for loading files/turning in on Canvas back to normal error rates. All shortened link issues with "Open with Kami" links, and "https://kami.app" sharing links are resolved. We'd like to thank you for your patience with us today. Sorry for the inconvenience this has caused. Please email us at support@kamiapp.com if you have any questions, or issues. We're happy to help.

A fix for "kami.app" shortened links has just been implemented. We're still experiencing some problems with Canvas, but it's error rates has decreased significantly. Less than 0.5% of our requests to Canvas are erroring out. We're still actively monitoring the situation, and will provide updates as they come. Thanks again for your patience.

The outage has since started to affect Kami's Turn In button for Canvas documents. Up to 25% of turn ins to Canvas are erroring out. Please attempt to workaround this problem by retrying the turning in.

Amazon Web Services (AWS) outage impacting Kami link sharing. Our engineers have identified an issue with our shortened links that use the domain "https://kami.app". This is due to the third party service that we use for this feature, Amazon Web Services (AWS), is currently experiencing an outage. This affects Kami Assignments created for Google Classroom because, by default, we add the shortened “Open with Kami” links to the assignment. Please workaround this problem by sharing the full un-shortened link (if you have it), sharing the file directly via Google Drive or OneDrive's file sharing dialogue, or using the “Open with Kami” link at the top center of the Google Drive file preview. This AWS outage is also affecting around 5% of document loads on Instructure's Canvas. To workaround this, try loading the Kami assignment from Kami again. In the meantime, you can still use all the other features of Kami without issue. Our engineers are closely monitoring this situation and hope to provide an update shortly.

We've rolled out a change which should work around this issue and error rates have returned to normal

Starting from 10:00 am Pacific Daylight Time or 1:00 pm Eastern Daylight Time 11th May 2021, we noticed an increase of errors affecting OneDrive for Business customers. This outage affects anyone attempting to save or turn in document changes to Microsoft OneDrive for Business from Kami. This outage affects 90-100% of documents save attempts to OneDrive for Business users. You will notice errors such as "Save Failed" or turn-in failures. This outage does not affect Google Drive, nor does it appear to affect OneDrive Personal users. Rest assured, your work and changes are saved safely to Kami's servers. We recommend you download the PDF file to your computer and upload it to One Drive manually or submit your work outside of Kami's Schoology Turn In or Canvas' Submit buttons. Or use the Kami share link and ask that your collaborators open the file in Kami. We have reported to Microsoft this outage, and our engineers are attempting to work around this. We're sorry for the inconvenience this is causing. For additional support, please email support@kamiapp.com.

Between 9:12 am and 9:26 am Pacific Daylight Time (PDT) today, we experienced a major outage caused by a database deadlock bug. This outage affected Kami users' ability to load and save documents, annotations, turn in work, and assignment creation. Our engineering team has fully resolved this issue, and our systems have been back to normal since 9:35 am PDT). Any annotations created during this time would have used Kami's Offline Mode, meaning it will automatically save your annotations next time you open Kami (even if you're on another document). We recommend that you open Kami to ensure all of your work has been saved and turned in. If you're experiencing any issues, reach out to our team at support@kamiapp.com. We're sorry the inconvenience this caused to you and your students. Our engineering team will investigate the root cause, and work on migitations to avoid it happening again.

There has been issues with Kami's "Open with Kami" buttons disappearing in Google Classroom. We have since released a Kami Chrome Extension update that fixes this problem. Any Kami Extension version 2.0.13390 or later will contain the fix. You can check your Kami Extension by going to chrome://extensions/?id=bhfdppnpkppcmclldhnadigbmfheemjf in your Chrome browser and checking the "Version" value. This Chrome Extension update will automatically roll out to everyone within 24 hours. If you do not get the update, please restart your Chromebook or Google Chrome, and it should provide your browser an opportunity to download the update. This bug was caused by a Google Classroom update that changed their Google Drive links. We're sorry for any inconvenience caused.

This incident was resolved at 11:33am Eastern, our teams are actively monitoring our infrastructure to ensure stability.

Between 10:25am and 11:33am Eastern time, we had an outage that caused failures or slowness with saving, exporting (e.g. OCR) and turning in documents. For example, you may have encountered an "Error while saving to Google Drive" message during this outage. Your work was saved to Kami, but may not have saved back to Google Drive or One Drive during this period. Please go back to your documents to submit or save to ensure everything is saved back to Google Drive or One Drive. This issue has been resolved after 11:33am Eastern, and our teams are actively monitoring our infrastructure to ensure stability. We're sorry about the late notification of this outage, and the inconvenience of this outage.

This incident has been resolved.

We're seeing higher rates of login failures with our Microsoft integration, due to an Azure issue https://status.azure.com/en-us/status

We've resolved a hardware performance issue that caused this outage. Kami's service is back up but it'll remain slow as our servers clear the backlog of requests from our Offline Mode. This issue was resolved at 3:45 PM Eastern Time. We apologize for the disruption this has caused. Our engineers will continue to monitor the situation, and investigate the underlying root cause of this outage.

Our engineers have rolled out a fix and will continue to monitor the situation.

We are continuing to work on a fix for this issue.

We've identified and currently investigating a major service outage that is affecting the majority of our features, including signing in, loading, saving, and creating annotations inside of Kami. The issue started at 3:19 PM Eastern Time. Our Offline Mode should have kicked in now to save the annotations locally, so please keep that tab open, and once service is restored that annotations should sync up automatically. Our engineers have been alerted to the issue, and are currently looking into what is causing this, and how we can resolve it for you. We will keep you updated on what we find, and any progress on a fix both via email or through this status page.

We experienced an issue from 10:25am EST to 10:35am EST where Kami was very slow or unavailable. We re continuing to investigate the cause of the interruption. Kami was available again with reduced performance at 10:35am EST and fully recovered at 10:45am EST.

We recently added two (2) new domains to Kami. If you have any firewall whitelists, please add the following domains to your whitelist. These domains are used for adding images to the app and for attaching files to your Kami assignments. If they're not whitelisted, you will notice errors such as "Try Again" when adding a file to an assignment or adding images stuck on "Loading Media...". Domains to whitelist: *.kamiaccess.com (specifically we use https://t.kamiaccess.com) *.kamiaccessfiles.com (specifically we use https://h.kamiaccessfiles.com) You're welcome to only whitelist those two specific subdomain names. Though, we want to potentially use other subdomain names in the future, which is why we're recommending a blanket sub-domain name wildcard whitelist. Please see https://help.kamiapp.com/en/articles/1420804-kami-network-requirements for a full list of domains to whitelist.

We've identified and are working on an API outage that started at 10:01 pm Eastern Time. The outage is caused by one of our databases. Our engineers are working on restoring the service. Kami's offline mode will automatically kick in to ensure your work is saved. Please make sure you keep your Kami tab open so that any annotations made while offline will sync back to Kami. This was resolved by 10:14 pm Eastern.

We can confirm that the firewall blocking has now stopped due to changes made by the vendor. We're working with them to prevent issues like this happening in the future.

We've figured out that we have a Kami firewall issue that's affecting some users that's causing your IP from being blocked and that's causing an issue loading files from Google Drive and signing in via Google. We're working with our firewall vendor to resolve this issue, but in the meantime we have some workarounds: - Please try loading Kami from another network or ISP. If you have an unlimited hotspot that you can use with Kami, try that. - If you wait up to 24 hours, Kami's firewall will cool down and remove the block. So it should be fine again tomorrow. We'll be working with our firewall vendor to come up with a long term solution to this problem. We're sorry for the inconvenience this is causing, thanks again for your patience.

We've identified the problem as an issue connecting to Google's authentication/Oauth service. The Kami frontend is having trouble connecting directly to Google's servers and this could be a network issue. We're still investigating and attempting to come up with a workaround. This will affect loading files from Google Drive, as well as signing up/signing in as Google

We've noticed an uptick of issues loading files from Google Drive. Our teams are investigating. We suspect it's a network issue reaching Google's services. The specific error is "An unknown error occurred while loading file from Google Drive"

A version of Kami was released that caused errors in the handling of in-app authentication for a small number of users. A fix (v2.0.12819) for this has now been released. The issue started at 1:30am PT, 21st Dec 2020 and was caused by an update that incorrectly handled authentication within Kami. The fix was rolled out at 3pm PT, 22nd December 2020. This bug caused issues with loading documents, creating assignments, and a range of other unusual behavior within Kami. We're extremely sorry about any disruption this may have caused and for our delay in notifying you. We strive to fix bugs and notify our users much sooner than this. The delay was caused by reduced staff numbers over the holiday period. If you're still affected by this issue, please go to https://web.kamihq.com/web/update_app.html to update your version of Kami. We will be developing a way to push out an update automatically. We will continue to closely monitor Kami over the holidays to avoid any disruption to the work of yourself and your students. - Your friends at Kami

We believe the latest update on production has definitely fixed the issue.

We're investigating the possibility that this "This Document has been Turned In" bug also affected students. We will update this message once we confirm more info. But in the meantime, if this is also affecting your students, please have them also update their app using the same link: https://web.kamihq.com/web/update_app.html

We identified and fixed a bug that is causing teachers or teacher assistants to see a "This Document has been Turned In" error message when they try to annotate student work from the Canvas Speedgrader. A fix has been rolled out. If you're affected, to get the fix immediately, please go to https://web.kamihq.com/web/update_app.html to update your app. We don't recommend pushing this out to students since they aren't affected by this bug. Also, Kami will naturally update itself throughout the next 24 hours with this fix, so if you haven't had reports of this issue, it's okay to let the update roll out automatically. Our teams are working on a way to ensure the root cause of this bug doesn't happen again. We're deeply sorry about this issue.

This incident has been resolved. There are still some lingering issues for some accounts on the Google side and increased response times which we are monitoring.

We are continuing to monitor for any further issues.

We are continuing to monitor for any further issues.

At 6:48am EST Google Auth services became unavailable affecting all services needing a user account (Login, Drive, GMail, Classroom, etc). We are now seeing some recovery of error rates but are still monitoring the issue.

The rolled out fix is holding.

We are continuing to work on a fix for this issue.

We've identified an issue that's similar to yesterday's issue with Canvas. An error message would show a "An Error occurred while validating the launch of Kami" message while teachers try to view Kami documents in Speedgrader and create assignments using the External Kami Tool. We know this is caused by a recent update where Canvas' LTI integration stops not sending us information about the course, and this is why it's predominantly affecting teachers only. We've developed a fix but are having issues with one of our engineering tooling providers to roll out the fix.