Is Hi Rasmus Down?

This incident has been resolved. The root cause was issues with Google Gemini's models in the US. A fallback was implemented and deployed at 21:15 UTC, which resolved the issue. --- [2026-10-08T18:09:47.480Z] (monitoring) Unfortunately, after a short period of no issues, issues have started coming in again. We are monitoring the situation and will update once there is a change. --- [2026-10-08T17:48:21.101Z] (monitoring) It seems that Google Gemini has resolved the issue as of 17:28 UTC. We are still monitoring, but the AI auditor and generate text seems to be working as expected now. --- [2026-10-08T17:14:50.891Z] (investigating) This seems to be an issue with Google's AI (gemini). Users are reporting issues with Gemini (https://downdetector.dk/en/status/googlegemini/), although Google hasn't acknowledged the outage on its status page yet (https://status.cloud.google.com/). We will keep monitoring the situation, but for now, it is up to Google to resolve the issue with Gemini --- [2026-10-08T16:51:13.876Z] (investigating) We are currently investigating an issue with our AI note auditor. It is currently failing to generate the session summaries for some clients.

Resolved Signature saving, file uploads and session file access are working normally again across all regions. You do not need to do anything. There is no update to install and no need to sign out or reinstall. If you have a session note that you were unable to sign earlier, you can go back and sign it now. The cause was a fault in a Google Cloud service that our platform uses to authorise file access, introduced by a platform change on their side. It was not caused by anything in our system. Google have confirmed the cause and we have deployed their recommended workaround, which takes the affected component out of the path entirely. Google are still working on the underlying fault. Our workaround is stable and we will keep monitoring closely until they confirm it is fully resolved. No data was lost or exposed at any point. Earlier today some users were also briefly unable to start sessions or use support features. That was a separate Google Cloud networking incident affecting their US region, which they have since resolved. --- [2026-09-01T16:02:05.183Z] (investigating) Signature saving and file uploads are still failing intermittently. We have not yet been able to resolve it. If you see an error, please try again. The failure affects individual attempts rather than accounts or specific notes, so a second or third attempt will usually succeed. Nothing is lost when an attempt fails, and the note stays available and unsigned until it goes through. The cause is a fault in a Google Cloud service that our platform relies on to authorise file access. It is not caused by a change on our side, and we have no way to fix it ourselves. We have deployed changes to work around it, but they have not restored normal service. This is no longer limited to our US region. Customers in Canada and Europe may also see it intermittently. Separately, between approximately 10:45 and 11:25 AM Eastern, some users were unable to start sessions or use support features. That was caused by the same underlying Google Cloud problem and has since recovered. No data has been lost or exposed. We have escalated to Google Cloud at the highest level available to us and are pressing for a resolution time. We are monitoring continuously and will update this page as we learn more. --- [2026-09-01T10:25:44.160Z] (investigating) The errors we reported yesterday have returned. Some users in our US region are again seeing a permission error when saving a signature on a session note, or when uploading a client file. The cause is the same fault in a Google Cloud service that our platform uses to authorise file uploads. It is not caused by a change on our side, and only our US region is affected. Our support case with Google remains open and we have escalated the recurrence. No data has been lost or exposed. If you see this error, signing again will often work, though it may take more than one attempt. We are monitoring continuously and will update this page as we learn more.

Signature saving and file uploads have been working normally since 00:35 AM ET, and we have seen no further errors. The cause was a fault in a Google Cloud service that our platform uses to authorise file uploads. It was not caused by a change on our side, and only our US region was affected. Google Support has escalated the issue and their investigation is ongoing, so we are treating this as resolved based on current service levels rather than a confirmed fix. We have put additional monitoring in place that alerts us immediately if the errors return, and we are watching closely. No data was lost or exposed. If you have a session note that still will not accept a signature, please contact support and we will help you complete it. --- [2026-09-01T01:46:01.245Z] (identified) Some users in our US region are seeing an error when saving a signature on a session note, or when uploading a client file. The error reads "User does not have permission to access...". We have traced this to a fault in a Google Cloud service that our platform relies on to authorise file uploads. It was not caused by a change on our side, and it does not affect any other region. No data has been lost or exposed. Notes that could not be signed remain available and unsigned, and note content is saved as normal. If you see this error, signing again will usually work. We have escalated this to Google Cloud Support at the highest priority and are monitoring continuously. We will update this page as soon as we know more.