<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>ELLA Status - Incident history</title>
    <link>https://withella.instatus.com</link>
    <description>ELLA</description>
    <pubDate>Thu, 15 Jan 2026 05:00:00 +0000</pubDate>
    
<item>
  <title>Advisors unable to access existing workspaces</title>
  <description>
    Type: Incident
    Duration: 2 days and 22 hours

    Affected Components: ELLA App Reachability
    Jan 22, 17:30:00 GMT+0 - Identified - We identified the cause. A recent update to our data-access permission rules was more restrictive than intended, causing some advisors to be blocked from viewing their own content. We began preparing and testing a corrected set of permission rules. Jan 24, 03:00:00 GMT+0 - Resolved - This incident is resolved. All advisor access has been restored, and no data was lost, altered, or exposed at any point. Notably, the root cause was a permission change that over-indexed on security controls. the rules erred toward locking data down rather than opening it up, so the failure was one of over-protection, not exposure. We&#039;ve since tightened our testing so access changes can&#039;t have this unintended effect again. We apologize for the disruption. Jan 15, 05:00:00 GMT+0 - Investigating - We began investigating reports that some advisors could not see their workspaces and associated content (documents, deliverables, and fact-finding data) after signing in. We began investigating on 1/21, but the problem was released into production several days prior before we were found the issue. We&#039;ve backdated this issue to the 15th to reflect that. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 2 days and 22 hours</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Jan &lt;var data-var=&#039;date&#039;&gt; 22&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;17:30:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We identified the cause. A recent update to our data-access permission rules was more restrictive than intended, causing some advisors to be blocked from viewing their own content. We began preparing and testing a corrected set of permission rules..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jan &lt;var data-var=&#039;date&#039;&gt; 24&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;03:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident is resolved. All advisor access has been restored, and no data was lost, altered, or exposed at any point. Notably, the root cause was a permission change that over-indexed on security controls. the rules erred toward locking data down rather than opening it up, so the failure was one of over-protection, not exposure. We&#039;ve since tightened our testing so access changes can&#039;t have this unintended effect again. We apologize for the disruption..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jan &lt;var data-var=&#039;date&#039;&gt; 15&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;05:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We began investigating reports that some advisors could not see their workspaces and associated content (documents, deliverables, and fact-finding data) after signing in. We began investigating on 1/21, but the problem was released into production several days prior before we were found the issue. We&#039;ve backdated this issue to the 15th to reflect that..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Thu, 15 Jan 2026 05:00:00 +0000</pubDate>
  <link>https://withella.instatus.com/incident/cmt1oo3a90e5b0kmep15yp2sm</link>
  <guid>https://withella.instatus.com/incident/cmt1oo3a90e5b0kmep15yp2sm</guid>
</item>

  </channel>
  </rss>