This issue was caused by an application version mismatch during deployment, where a frontend change deployed before dependent backend configuration updates had fully applied. That created a temporary incompatibility between the frontend and backend, which resulted in errors for authenticated users to access their own data. We mitigated the issue by reverting the change and have now implemented tighter deployment staging controls, compatibility validation for dependent changes, and faster rollback mechanisms to prevent recurrence and shorten future recovery time.
Posted Feb 16, 2026 - 16:30 GMT
Identified
Users are seeing escalated page load failures. We have already identified the issue and have a resolution fix in progress.