<?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>Elicit Status - Incident history</title>
    <link>https://status.elicit.com</link>
    <description>Elicit</description>
    <pubDate>Thu, 9 Apr 2026 21:42:04 +0000</pubDate>
    
<item>
  <title>Disconnected from server errors</title>
  <description>
    Type: Incident
    Duration: 44 minutes

    Affected Components: Elicit
    Apr 9, 21:42:04 GMT+0 - Investigating - We are experiencing an infrastructure issue impacting Elicit research agent, reports, systematic review, find papers, and library to fail and show disconnected from server errors. We are currently investigating this incident. Apr 9, 21:58:17 GMT+0 - Identified - Sessions are operational again Apr 9, 22:08:03 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Apr 9, 22:26:13 GMT+0 - Resolved - This incident has been resolved. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 44 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 9&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;21:42:04&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are experiencing an infrastructure issue impacting Elicit research agent, reports, systematic review, find papers, and library to fail and show disconnected from server errors. We are currently investigating this incident..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 9&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;21:58:17&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Sessions are operational again.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 9&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;22:08:03&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  We implemented a fix and are currently monitoring the result..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 9&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;22:26:13&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Thu, 9 Apr 2026 21:42:04 +0000</pubDate>
  <link>https://status.elicit.com/incident/cmns05s6s049dzilvhet2baew</link>
  <guid>https://status.elicit.com/incident/cmns05s6s049dzilvhet2baew</guid>
</item>

<item>
  <title>Degraded performance of paper searches</title>
  <description>
    Type: Incident
    Duration: 1 hour and 43 minutes

    Affected Components: Elicit
    Mar 27, 16:10:45 GMT+0 - Identified - An upstream service provider is experiencing an infrastructure issue causing paper searches in Elicit research agent, reports, systematic review, and find papers to be slow or intermittently fail. They have identified a fix but expect degraded performance to continue over the next hour. Mar 27, 17:39:10 GMT+0 - Monitoring - The provider has upgraded their infrastructure and search performance has recovered. We are continuing to monitor closely. Mar 27, 17:54:11 GMT+0 - Resolved - This incident has been resolved. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 43 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Mar &lt;var data-var=&#039;date&#039;&gt; 27&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;16:10:45&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  An upstream service provider is experiencing an infrastructure issue causing paper searches in Elicit research agent, reports, systematic review, and find papers to be slow or intermittently fail. They have identified a fix but expect degraded performance to continue over the next hour..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Mar &lt;var data-var=&#039;date&#039;&gt; 27&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;17:39:10&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  The provider has upgraded their infrastructure and search performance has recovered. We are continuing to monitor closely..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Mar &lt;var data-var=&#039;date&#039;&gt; 27&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;17:54:11&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Fri, 27 Mar 2026 16:10:45 +0000</pubDate>
  <link>https://status.elicit.com/incident/cmn93llgl003j9c26zugyl5qu</link>
  <guid>https://status.elicit.com/incident/cmn93llgl003j9c26zugyl5qu</guid>
</item>

<item>
  <title>Intermittent errors when loading Elicit sessions</title>
  <description>
    Type: Incident
    Duration: 4 hours and 56 minutes

    Affected Components: Elicit
    Mar 26, 14:30:00 GMT+0 - Identified - We have identified the root cause and are working to remediate it. Mar 26, 16:12:34 GMT+0 - Identified - We have isolated the problem and are upgrading some infrastructure to fix the problem.

This may cause slowness and user-facing errors on [elicit.com](http://elicit.com) for up to 30 minutes. Mar 26, 16:47:23 GMT+0 - Identified - The infrastructure upgrade is now being applied – we&#039;re expecting elevated error rates for up to 30 minutes. Mar 26, 18:00:27 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Mar 26, 19:25:34 GMT+0 - Resolved - Resolved — Some users experienced issues loading workflows and sessions earlier today. This was caused by our database running low on memory, which we resolved by upgrading the infrastructure. The upgrade took longer than expected, causing a second period of disruption between approximately 10:55 AM and 11:30 AM PT where workflows would not load.

Everything is fully operational now. No data was lost. We&#039;re sorry for the disruption and are taking steps to prevent this from happening again. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 4 hours and 56 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Mar &lt;var data-var=&#039;date&#039;&gt; 26&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;14:30:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We have identified the root cause and are working to remediate it..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Mar &lt;var data-var=&#039;date&#039;&gt; 26&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;16:12:34&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We have isolated the problem and are upgrading some infrastructure to fix the problem.

This may cause slowness and user-facing errors on [elicit.com](http://elicit.com) for up to 30 minutes..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Mar &lt;var data-var=&#039;date&#039;&gt; 26&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;16:47:23&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  The infrastructure upgrade is now being applied – we&#039;re expecting elevated error rates for up to 30 minutes..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Mar &lt;var data-var=&#039;date&#039;&gt; 26&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;18:00:27&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  We implemented a fix and are currently monitoring the result..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Mar &lt;var data-var=&#039;date&#039;&gt; 26&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;19:25:34&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  Resolved — Some users experienced issues loading workflows and sessions earlier today. This was caused by our database running low on memory, which we resolved by upgrading the infrastructure. The upgrade took longer than expected, causing a second period of disruption between approximately 10:55 AM and 11:30 AM PT where workflows would not load.

Everything is fully operational now. No data was lost. We&#039;re sorry for the disruption and are taking steps to prevent this from happening again..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Thu, 26 Mar 2026 14:30:00 +0000</pubDate>
  <link>https://status.elicit.com/incident/cmn7o2led09f5h889gjrs74wp</link>
  <guid>https://status.elicit.com/incident/cmn7o2led09f5h889gjrs74wp</guid>
</item>

<item>
  <title>Incident with loading sessions on Elicit.com</title>
  <description>
    Type: Incident
    Duration: 26 minutes

    Affected Components: Elicit
    Mar 17, 15:30:00 GMT+0 - Identified - As of 8:34 PST, we began to see issues loading session for all users on Elicit.com. We immediately investigated and identified the issue in our AWS infrastructure, and began remediation. We expect resolution within 30 minutes, and will continue to monitor.  Mar 17, 15:55:36 GMT+0 - Resolved - Some users may have experienced issues loading or interacting with sessions between approximately 8:30 AM and 8:55 AM ET. This was caused by our session database replica temporarily going offline while processing a large batch of maintenance operations. During this window, session reads and writes were unavailable. The replica recovered on its own and all functionality has been restored. No session data was lost or corrupted. We apologize for the disruption. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 26 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Mar &lt;var data-var=&#039;date&#039;&gt; 17&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;15:30:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  As of 8:34 PST, we began to see issues loading session for all users on Elicit.com. We immediately investigated and identified the issue in our AWS infrastructure, and began remediation. We expect resolution within 30 minutes, and will continue to monitor. .&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Mar &lt;var data-var=&#039;date&#039;&gt; 17&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;15:55:36&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  Some users may have experienced issues loading or interacting with sessions between approximately 8:30 AM and 8:55 AM ET. This was caused by our session database replica temporarily going offline while processing a large batch of maintenance operations. During this window, session reads and writes were unavailable. The replica recovered on its own and all functionality has been restored. No session data was lost or corrupted. We apologize for the disruption..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Tue, 17 Mar 2026 15:30:00 +0000</pubDate>
  <link>https://status.elicit.com/incident/cmmusfjad001w111fj18ha2b9</link>
  <guid>https://status.elicit.com/incident/cmmusfjad001w111fj18ha2b9</guid>
</item>

<item>
  <title>Degraded performance for some users</title>
  <description>
    Type: Incident
    Duration: 29 days and 1 hour

    Affected Components: Elicit
    Feb 25, 22:05:00 GMT+0 - Investigating - Some users may encounter server errors when running a workflow.

We are investigating the cause and will update this page as we know more. Feb 26, 19:40:59 GMT+0 - Identified - We have identified the issue and are finalising a fix.

We will update when the fix has been released and is stable. Feb 27, 21:42:00 GMT+0 - Resolved - The issue has been resolved. More information about the resolution is available here.

&lt;https://www.notion.so/elicit-research/Service-Disruption-Session-Data-Loss-February-25-26-2026-314cfae9876c8018892bf397468b3e25?source=copy%5Flink&gt; 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 29 days and 1 hour</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Feb &lt;var data-var=&#039;date&#039;&gt; 25&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;22:05:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  Some users may encounter server errors when running a workflow.

We are investigating the cause and will update this page as we know more..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Feb &lt;var data-var=&#039;date&#039;&gt; 26&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;19:40:59&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We have identified the issue and are finalising a fix.

We will update when the fix has been released and is stable..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Feb &lt;var data-var=&#039;date&#039;&gt; 27&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;21:42:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  The issue has been resolved. More information about the resolution is available here.

&lt;https://www.notion.so/elicit-research/Service-Disruption-Session-Data-Loss-February-25-26-2026-314cfae9876c8018892bf397468b3e25?source=copy%5Flink&gt;.&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Wed, 25 Feb 2026 22:05:00 +0000</pubDate>
  <link>https://status.elicit.com/incident/cmm3pnex50r7ohrimlnm8ghyb</link>
  <guid>https://status.elicit.com/incident/cmm3pnex50r7ohrimlnm8ghyb</guid>
</item>

<item>
  <title>Login Outage; Some Users May Be Signed Out</title>
  <description>
    Type: Incident
    Duration: 1 hour and 36 minutes

    
    Nov 8, 18:30:59 GMT+0 - Investigating - We’re seeing errors with sign-ins and session renewals (refresh tokens). This means some people can’t log in, and some active sessions may sign out unexpectedly. Nov 8, 19:13:02 GMT+0 - Monitoring - Our authentication provider has implemented a fix. Sign-ups, sign-ins, and session renewals are succeeding again. We are monitoring closely. Nov 8, 20:07:01 GMT+0 - Resolved - Sign-ups, sign-ins, and session renewals are operating normally again. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 36 minutes</p>
    
    &lt;p&gt;&lt;small&gt;Nov &lt;var data-var=&#039;date&#039;&gt; 8&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;18:30:59&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We’re seeing errors with sign-ins and session renewals (refresh tokens). This means some people can’t log in, and some active sessions may sign out unexpectedly..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Nov &lt;var data-var=&#039;date&#039;&gt; 8&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;19:13:02&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  Our authentication provider has implemented a fix. Sign-ups, sign-ins, and session renewals are succeeding again. We are monitoring closely..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Nov &lt;var data-var=&#039;date&#039;&gt; 8&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;20:07:01&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  Sign-ups, sign-ins, and session renewals are operating normally again..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Sat, 8 Nov 2025 18:30:59 +0000</pubDate>
  <link>https://status.elicit.com/incident/cmhqmej9p0166z6shli17bimr</link>
  <guid>https://status.elicit.com/incident/cmhqmej9p0166z6shli17bimr</guid>
</item>

<item>
  <title>elicit.com is slow, or not loading for some</title>
  <description>
    Type: Incident
    Duration: 1 hour and 22 minutes

    Affected Components: Elicit
    Aug 31, 15:07:44 GMT+0 - Investigating - We are currently investigating this incident. Aug 31, 15:52:00 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Aug 31, 16:30:08 GMT+0 - Resolved - This incident has been resolved. We will conduct a post-mortem so that we can learn from today&#039;s incident. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 22 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 31&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;15:07:44&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are currently investigating this incident..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 31&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;15:52:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  We implemented a fix and are currently monitoring the result..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 31&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;16:30:08&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved. We will conduct a post-mortem so that we can learn from today&#039;s incident..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Sun, 31 Aug 2025 15:07:44 +0000</pubDate>
  <link>https://status.elicit.com/incident/cmeztrdja00a6yqlcet3dtt1m</link>
  <guid>https://status.elicit.com/incident/cmeztrdja00a6yqlcet3dtt1m</guid>
</item>

  </channel>
  </rss>