history.rss
Elicit Status - Incident History
Incidents
Disconnected from Server Errors
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.
Degraded Performance of Paper Searches
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.
Intermittent Errors When Loading Elicit Sessions
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 for up to 30 minutes. - Mar 26, 16:47:23 GMT+0 - Identified
The infrastructure upgrade is now being applied – we'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. Everything is fully operational now. No data was lost.
Incident with Loading Sessions on Elicit.com
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. - Mar 17, 15:55:36 GMT+0 - Resolved
Some users may have experienced issues loading or interacting with sessions. This was caused by our session database replica temporarily going offline. The replica recovered on its own and all functionality has been restored. No session data was lost or corrupted.
Degraded Performance for Some Users
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. - Feb 26, 19:40:59 GMT+0 - Identified
We have identified the issue and are finalising a fix. - Feb 27, 21:42:00 GMT+0 - Resolved
The issue has been resolved. More information about the resolution is available here.
Login Outage; Some Users May Be Signed Out
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. 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. - Nov 8, 20:07:01 GMT+0 - Resolved
Sign-ups, sign-ins, and session renewals are operating normally again.
Elicit.com is Slow, or Not Loading for Some
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 to learn from today's incident.