Exalate incident
Personal Access Token error on multiple environments
Exalate experienced a notice incident on December 6, 2022 affecting connect.exalate.net (mapper) and Hosting platform and 1 more component, lasting 1d 7h. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Nov 30, 2022, 07:48 AM UTC
Customers are reporting problems with Access Token, such as 401 errors and update Token in general settings.
- identified Dec 02, 2022, 10:27 AM UTC
The issue has been identified, workarounds provided to the customers upon Support request. The permanent solution is under development.
- monitoring Dec 02, 2022, 02:52 PM UTC
The fix is implemented and currently under testing
- monitoring Dec 06, 2022, 09:13 AM UTC
Workaround has been applied. Permanent solution under testing.
- monitoring Dec 06, 2022, 04:28 PM UTC
The permanent fix solution passed the QA tests and is going to be released in Exalate v5.4.8. The deployment of the new version on the customers' environments will start on Tuesday December 6 and end on Wednesday December 7 CET end of day. During the deployment time all nodes will be operational. It is expected that the node will restart and the sync will interrupt for about 1 minute. After the restart the sync will resume from the point it stopped. No actions required from the customers side.
- resolved Dec 07, 2022, 04:19 PM UTC
The update with fix has been deployed to all cloud nodes.
- postmortem Apr 01, 2026, 04:16 AM UTC
timeout