Summary
On March 10, 2026, between 10:32 AM and 2:52 PM (JST), we experienced a service disruption that prevented some users from logging into Notta. The issue has since been fully resolved, and all systems are now operating normally.
Incident Period
March 10, 2026, 10:32 AM – 2:52 PM (JST)
Details
Users meeting the following criteria may have encountered a 500 Internal Server Error when attempting to log in:
Users with expired session cookies/local cache.
New users attempting their first login.
Root Cause
The incident was triggered by an update from a third-party software provider used within our web application. This update caused a conflict in our authentication flow. After identifying the source, our engineering team restored service by disabling the affected component.
Scope of Impact
This issue impacted a subset of users attempting new or re-authenticated login sessions. Existing active sessions were not affected.
Action Required
If you are still experiencing issues, please perform a hard refresh of your browser:
Windows:
Ctrl + Shift + RMac:
Command + Shift + R
Should you need further assistance, please contact us at support@notta.ai.
Data Integrity and Security
This disruption was strictly limited to login authentication. No user data (audio, transcripts, or personal information) was impacted, and no unauthorized access occurred.
We sincerely apologize for the disruption to your workflow. We are conducting a full internal review to prevent a recurrence of this issue.
Thank you for your patience and for choosing Notta.