Close experienced a critical incident on January 6, 2025 affecting Application UI, lasting 1h 58m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Jan 06, 2025, 05:49 PM UTC
We are currently investigating the issue.
- monitoring Jan 06, 2025, 05:50 PM UTC
Issue was identified and reverted. Monitoring to confirm no further issues.
- resolved Jan 06, 2025, 07:47 PM UTC
This incident has been resolved.
- postmortem Jan 09, 2025, 07:48 AM UTC
Close sincerely apologizes for the interruption of our service. We take the stability of our platform very seriously. Below is an explanation of what happened and how we will prevent another such interruption from occurring. ## Impact The Close Web UI was unavailable for 15 minutes from 2025-01-06 17:33 to 2025-01-06 17:48. ## Root Cause and Resolution A change to our deployment process introduced a build where JavaScript file contents were updated without corresponding filename changes, leading to caching issues that caused outdated files to be served. We quickly rolled back to a previous build to restore services and then resolved the underlying issue by updating the affected assets. ## Timeline * 17:33 UTC - Deployment of the broken Close Web UI * 17:48 UTC - Restored prior version