Application UI Intermittently Inaccessible

What to do

• Check whether you use Close Application UI. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 47m it lasted.

  Anything that failed between 2025-06-19 04:23 UTC and 2025-06-19 05:10 UTC may need a replay.

• Subscribe to Close's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=close works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Close 6

1. investigatingJun 19, 2025, 4:23 AM UTC

   Users are currently unable to load the application UI due to an issue with the serving infrastructure.

   provider

2. investigatingJun 19, 2025, 5:02 AM UTC

   We're continuing to investigate the issue.

   provider

3. monitoringJun 19, 2025, 5:08 AM UTC

   Application is loading again, we're monitoring the situation.

   provider

4. monitoringJun 19, 2025, 5:09 AM UTC

   We are continuing to monitor for any further issues.

   provider

5. resolvedJun 19, 2025, 5:10 AM UTC

   This incident has been resolved.

   provider

6. postmortemJun 19, 2025, 6:01 PM 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 and Desktop applications were intermittently failing to load for from June 18th 22:32 UTC to June 19th 05:10 UTC. The issue started with only a few errors with the frequency gradually increasing until it was resolved. ## Root Cause and Resolution A misconfigured version of the application was partially deployed due to mishandling of failures of a re-run CI/CD job. The issue was resolved by deploying a freshly built version of the application. We are improving our alerting systems to detect such incidents sooner and implementing safeguards into our build process to prevent misconfigured versions from occurring in the first place. ## Timeline * June 18th 22:32 UTC - an already deployed version of the application image gets misconfigured due to an issue in our build system * as time goes on and our infrastructure cycles resources which causes more and more traffic to get served by the misconfigured version, but not often enough to trigger our alerts * June 19th 04:17 UTC - Close Engineering team realizes there’s a problem, begins an investigation and starts taking mitigation steps * June 19th 05:10 UTC - a new version of the application is deployed resolving the issue

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.