Legacy Token authentication failure after system authentication update

Update timeline

1. investigating Feb 17, 2026, 02:25 PM UTC

   Summary Between February 16 and 17, 2026, some customers using older API tokens experienced authentication failures. These tokens, originally created before a recent system update, could not be used to access services. Tokens issued after the update were not affected. The issue was caused by the removal of a process that allowed continued use of these older tokens. The problem was identified overnight and resolved the following morning. Key Timeline (IDT) February 16, 2026, 23:42 IDT: First reports of authentication failures with legacy tokens. February 17, 2026, 11:20 IDT: Corrective update deployed to restore access for affected customers. Root Cause A process that enabled older tokens to work with the updated authentication system was mistakenly removed during a recent update. This led to authentication failures for customers still using these legacy tokens. Actions Taken Restored the process that allows older tokens to be used for authentication.Deployed a corrective update to resolve the issue. Action Items Add tests to ensure all authentication scenarios are covered.Implement integration tests to verify continued support for older tokens.Improve validation procedures to detect similar issues before deployment.