App UI unavailable

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 1h 58m it lasted.

  Anything that failed between 2025-01-06 17:49 UTC and 2025-01-06 19:47 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 4

1. investigatingJan 6, 2025, 5:49 PM UTC

   We are currently investigating the issue.

   provider

2. monitoringJan 6, 2025, 5:50 PM UTC

   Issue was identified and reverted. Monitoring to confirm no further issues.

   provider

3. resolvedJan 6, 2025, 7:47 PM UTC

   This incident has been resolved.

   provider

4. postmortemJan 9, 2025, 7: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

   provider

Corrections

None so far.

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