Is Litify Down Right Now? Check if there is a current outage ongoing.

Salesforce has reported the performance issues to be fully resolved. Please reach out to Litify Support if issues persist.

Salesforce has initiated service restarts to mitigate the impact and has begun to observe performance improvements. We are continuing to monitor.

Salesforce has reported widespread performance issues that are leading to slow loading times and loading errors. Salesforce is currently investigating. You can find updates from Salesforce on status.salesforce.com; we will continue to provide updates as well.

Docrio Calendar is fully functional. Please reach out to Litify Support if sync performance issues persist.

A fix has been implemented and is showing positive results. We are continuing to monitor.

The issue has been identified, and Litify is working to implement a fix. We will provide another update soon.

Docrio Calendar Sync is currently experiencing sync delays. We are actively investigating.

We have confirmed that the AWS outage has been resolved. Please reach out to Litify Support if other issues arise.

AWS has identified increased API error rates and noted that these have recovered. Several Litify clients have confirmed that Docrio is operational again following this recovery. We are continuing to monitor.

Docrio is currently experiencing an outage. This appears to be related to an AWS outage. We are investigating further and will provide an update as soon as possible.

Salesforce reported this issue fully resolved at 3:00 AM EST. If further issues are experienced, please reach out to Litify Support.

It appears that the emergency release from Salesforce will continue to be rolled out overnight. We will continue monitoring and provide an update early tomorrow (Wednesday) morning.

Salesforce is continuing to perform the emergency release. We've continued to receive confirmations that Litify clients are operational again; however, we are also continuing to receive reports of clients who are still unable to access the platform. Litify is continuing to monitor progress.

Salesforce has identified more affected instances and continues to roll out the emergency release. Several Litify clients have confirmed the outage has subsided in their orgs. We recommend trying to log back in at this time.

Salesforce continues to roll out the emergency release, which is showing success. However, there is a small subset of instances that will need manual intervention from Salesforce. Also, please note that Litify has also been affected by this outage, so we have been unable to receive any support cases since the issue began, we will respond as quickly as possible once we are fully operational. We are continuing to monitor.

Salesforce has identified the issue and is rolling out an emergency release. Additional capacity has been added to all affected instances in an attempt to minimize further degradation during the emergency release. Litify will continue to provide updates as we have them from Salesforce.

Salesforce has reported performance issues that are affecting the USA instances listed below; this list appears to be growing. Users may experience slow load times or complete outages. We are monitoring and will provide more information as available from Salesforce. USA1, USA304, USA316, USA340, USA344, USA352, USA366S, USA374, USA376, USA494, USA554, USA556, USA558, USA600, USA612, USA618, USA680, USA694, USA708, USA714, USA780, USA790, USA1012

Docrio Email delays have been resolved. Please reach out to Litify Support if the delay is persisting for your org.

Docrio Email is currently experiencing delays in processing saving of emails and autothreading. All requests are still being processed, but users may see a delay in the save tag appearing or the email being created in Litify.

The remaining LRN issues appear to have been resolved. Please reach out to Litify Support if continued issues are experienced.

We are continuing to investigate ongoing errors and login issues. We will provide another update within two hours.

The issue has been identified and diagnosed. Some clients may have had all issues resolved, however, there are ongoing issues with LRN site access and logins within LRN Pro for other clients. We are continuing to investigate and work on these issues.

This morning's Litify Referral Network (LRN) is currently down due to unexpected release complications. Users are experiencing 502, 504, and error emails. We are actively investigating this issue and will follow up soon.

We've received confirmation that the fix was successful and Litify Inbox is fully operational. Please reach out to Litify Support if other issues are experienced.

A fix was implemented last night, we are currently awaiting confirmation that the fix was successful. More information will be provided soon.

As this issue is with Microsoft, we will not have another update today. We hope to have more information tomorrow morning, thank you for your patience.

We believe the cause of this issue has been identified and traced back to a change from Microsoft. It also appears that it is affecting other Microsoft products in addition to Outlook at varying degrees. The Litify Inbox team is looking for a workaround and is in contact with Microsoft. We will provide further updates as we have them.

Litify Inbox is currently down. Users have reported an inability to get into the add-in (Error: Application failed to initialize) or the inability to sync emails (Error: Sorry an error occurred, please restart the sidebar). Initial investigations are pointing to a change on the Microsoft side being the cause, but we are continuing to investigate.

The issue is resolved, Docrio Email is fully functional.

The release has been redeployed and a fix put in place. We are currently monitoring and working to confirm.

This morning's Docrio Email and Word Add-In release has led to an unforeseen AWS rate limit that has led users to be unable to log in to either product. Our Product & Engineering team has identified the issue and is currently working on a fix. More information will be provided as we have it.

The LRN performance issues have been fully resolved.

An adjustment has been made that appears to have resolved the issue. We will continue to monitor through tomorrow (11/21) morning.

The Litify Referral Network (LRN) is currently experiencing performance issues. We are actively investigating.

The Salesforce rollback is continuing; however, multiple Litify clients have indicated that the issue is now resolved. The rollback will continue through the evening. If you are still experiencing child record creation issues tomorrow, please reach out to Litify Support.

Salesforce has continued the rollback of the release that led to this issue. This rollback is now in hour six and we are unable to know what orgs have had a successful rollback. Therefore, we advise continuing to check the creation of child records throughout the day.

Salesforce is currently experiencing issues with the creation of child records from a related list of a parent object. Parent object details are not being populated, preventing the save of the new child record. This can affect a large variety of activities, for example, creating notes. Salesforce has identified that this issue was created from a release. They have tested a rollback, which was successful and are currently working to rollback all orgs. They expect this to take a few hours. Litify Support is continuing to monitor and will provide updates as we see them.

All LRN issues have been resolved. Please reach out to Litify Support if any new issues occur.

The 406 error has been resolved. However, we have identified other issues affecting access that we are continuing to investigate.

The Litify Referral Network (LRN) is currently down. Users have experienced issues creating/sending referrals and have reported a 406 error. Litify is actively investigating this issue.

Litify Inbox is operational.

The Litify Inbox outage was caused by a temporary server outage. This has been resolved, but we're continuing to monitor.

Litify Inbox is currently experiencing an outage. The tool will spin and say 'Connecting to Litify.' We are actively investigating.

We have confirmed that this incident has been resolved.

A workaround has been implemented. Affected users will need to restart the Litify Inbox add-in. We are currently monitoring to confirm the workaround.

The issue has been identified and a workaround is currently being tested.

Following this morning's Litify Inbox upgrade, clients are reporting the following error message: Your MS Outlook Configuration is no longer supported by Litify Inbox. This is actively being investigated.

Salesforce Authenticator is fully functional.

Salesforce's throttling measures are showing positive results, we've confirmed that the issue is fixed with several Litify clients and are continuing to monitor.

Salesforce believes they have identified the root cause and have been working on the traffic throttle, which is showing improvement. We are continuing to monitor.

We are continuing to investigate this issue.

Salesforce has noted that initial mitigation efforts have been unsuccessful, and engineers are continuing to investigate. Salesforce had noted the following workaround: Workaround: Customers can authenticate and access Salesforce services by waiting for the connection to time out and using the six-digit OTP (One Time Password) on the Salesforce Authenticator mobile app. This is an authentication option that allows the user to authenticate with a shared encrypted secret password.

Salesforce has noted that initial mitigation efforts have been unsuccessful, and engineers are continuing to investigate. Salesforce had noted the following workaround: Workaround: Customers can authenticate and access Salesforce services by waiting for the connection to time out and using the six-digit OTP (One Time Password) on the Salesforce Authenticator mobile app. This is an authentication option that allows the user to authenticate with a shared encrypted secret password.

We have received several reports of the Salesforce Authenticator being down for MFA logins. We have reached out to Salesforce for investigation.

Litify Inbox has been fully restored.

The performance degradation issue has been identified and a fix put in place. We are currently monitoring.

Litify Inbox is currently experiencing an outage that is being actively investigated. Users report errors such as "Error while reading settings for user."

Salesforce has confirmed that the performance degradation issues have been resolved in all affected instances. Please reach out to Litify Support if the issues reappear.

Salesforce has completed the release rollback on NA152. Initial indications from this instance are that the issue has subsided. Salesforce is running additional health checks before proceeding with the fix on the other affected instances.

The issue was believed to have been triggered by congestion on various Salesforce database nodes. Salesforce engineers cleared out the job queues and began application tier restarts which have shown improvement, however, there remain some concerns about database response times. Litify Support is continuing to monitor.

Salesforce has reported performance degradation in the instances below. Orgs on these instances can expect slow speeds and potentially timeouts. Salesforce is investigating the issue, we will provide an update soon. NA148, NA152, NA168, NA204, NA158

AWS has reported this issue to be fully resolved.

AWS has reported signs of recovery, which has been confirmed by several clients. We are continuing to monitor.

Docrio is currently down for a large number of customers due to an AWS internet outage. Clients have reported not being able to preview or download files from Docrio. We will update when we hear more.

The Salesforce performance degradation issue had been resolved.

Salesforce is reporting performance degradation on the Salesforce.com site. Users may experience latency and timeouts when navigating the site. Salesforce is currently investigating the issue.

We have confirmed that the issue is fully resolved.

A fix has been deployed and Docrio Email is operational. We are continuing to monitor.

The issue has been identified and we are actively working on a resolution.

Docrio Email is currently experiencing an issue where users are unable to log in. Users have reported the following error: Connection Failure - Please click here to start over. If you continue to encounter issues, contact your system administrator, or visit Litify Help. We are investigating this issue.

We have confirmed that the Litify Inbox sync issue has been resolved.

Litify Inbox sync has been restored and normal operations should have resumed. Litify Support Engineering is continuing to monitor. Please disregard the email noting that an action is required.

We are currently investigating Litify Inbox outage that has caused syncs to cease. If you are experiencing this, you likely received an email noting that syncs have been suspended and that an action is required. No action is required from you at this time. Further updates will be provided shortly.

We have confirmed that Litify Inbox is fully functional, this issue is resolved.

Full operation of Litify Inbox appears to have been restored and performance spikes are subsiding. We are continuing to monitor.

Litify Inbox is currently experiencing performance degradation. We are investigating the issue.

The rolling restarts appear to have been effective thus far. Salesforce is continuing the application restarts and has added additional instances.

Salesforce is conducting a rolling restart to resolve the performance issue. We are continuing to monitor.

Salesforce Instance NA152 is currently experiencing performance degradation. Salesforce has isolated the issue and is currently working on a fix.

Salesforce has updated certificate configurations and have confirmed the access issue is resolved.

Salesforce is investigating a service disruption that limits access to the platform. It has been determined that this is due to an expired certificate. We will continue to monitor.

Salesforce has resolved the issue.

Salesforce is still working on the issue. We have discovered a workaround, please follow these steps: 1. Log in with username/password. 2. After authentication fails, click the 'Use a Different Verification Method' link. 3. Choose the middle option: Use a code from an authenticator app. 4. Open Salesforce Authenticator and choose the applicable account. 5. Enter the six-digit code from the authenticator.

We have received several reports that the Salesforce Authenticator is down for MFA logins. We are actively investigating with Salesforce.

This incident has been resolved.

Vendor is working to recover affected components, users are able to login and use LRN. We are continuing to monitor until full operation is confirmed.

LRN is currently experiencing an outage, we are investigating.

We've been monitoring this issue and can confirm Docrio is fully functional and operating normally. This issue is now marked as resolved. If you are still having any issues please don't hesitate to reach out to our Support Team at support@litify.com.

This issue has been marked as resolved by AWS and Docrio should now be fully functional. We will continue monitoring the performance and provide an update later today. If you are still having any issues please don't hesitate to reach out to our Support Team at support@litify.com.

We are seeing some improvement in Docrio functionally as it appears that AWS has identified and is actively resolving this issue. We will continue to closely monitor this issue and provide further updates. You can view the AWS Status page as well here at https://status.aws.amazon.com/

We are continuing to investigate this issue.

We are continuing to monitor this issue will provide updates accordingly. You can view the AWS Status page as well here at https://status.aws.amazon.com/

We are currently aware of an issue impacting Docrio performance and it appears to be caused by an AWS outage. We are actively monitoring the issue and will provide updates as the issue is further investigated and resolved. You can view the AWS Status page as well here at https://status.aws.amazon.com/

Litify Admins, Salesforce has resolved this issue, so Litify will be closing the issue as well. Thank you for your patience while Salesforce worked to resolve this issue. Details can be found here: https://status.salesforce.com/incidents/7607 ~Litify Support~

Litify Admins, It appears Salesforce has restored service to all impacted accounts, however they are still in the process of implementing a permanent fix for the issue. Litify will keep this post up until the outage is fully resolved. Thank you for your patience and we apologize or any downtime that was caused during this incident. You may continue to follow updates from Salesforce here: https://status.salesforce.com/incidents/7611 ~Litify Support~

Litify Admins, Latest Update from Salesforce: The rolling restart of the application services for the impacted instances has been completed, with the exception of NA151, which is expected to finish soon. The Technology team continues to validate the restart and monitor the health and average page times for all instances. This means that all but a few customers should be back up and running at this point. For details on this incident, including 30 minutes updates from Salesforce, visit the following link: https://status.salesforce.com/incidents/7611 ~Litify Support~

Litify Admins, Salesforce reports that many accounts have gone thought the restart of services and are seeing positive outcomes. Some accounts are taking longer than others to complete their restart, so some Litify customers may still be experiencing slowness. Salesforce continues to treat this at the HIGHEST priority, and the issue will be resolved for all instances ASAP. For details on this incident, including 30 minutes updates from Salesforce, visit the following link: https://status.salesforce.com/incidents/7611 ~Litify Support~

We are continuing to monitor for any further issues.

Litify Admins, Salesforce continues to proceed with application restarts for all impacted accounts. Their estimated time of resolution is around an hour. This timeframe may be updated as the fix is rolled out. We apologize for the slowness you may be experiencing during this downtime. We will continue to closely monitor the situation with Salesforce. For details on this incident, including 30 minutes updates from Salesforce, visit the following link: https://status.salesforce.com/incidents/7611 If you're unsure if your issues is related to the outage, you may open up a ticket by emailing us (support@litify.com) ~ Litify Support ~

We are continuing to monitor for any further issues.

Dear Admins, Salesforce reported at outage at 6:31 am UTC, Aug 19 this morning that is causing performance degradation for some Litify customers. Salesforce is already in the process of resolving this issue and you should see speed/performance issues resolve shortly. We apologize for the inconvenience this has caused. To receive text/email updates from Salesforce directly, you can subscribe at https://status.salesforce.com/. For details on this incident, including 30 minutes updates from Salesforce, visit the following link: https://status.salesforce.com/incidents/7611 If you're unsure if your issues is related to the outage, you may open up a ticket by emailing us (support@litify.com) ~ LItify Support ~

Litify is marking this incident as closed. Per Salesforce: Update: At 17:09 UTC, the third party provider reported that the issue is resolved. The Salesforce Technology team has validated that all services returned to normal performance levels and customers were out of impact between 16:40 and 16:47 UTC. The team called the issue all clear at 17:09 UTC. Thank you for your patience and sorry for any possible interruptions of service during this outage.

Salesforce has informed us that the 3rd party vendor responsible for the service outage has resolved their issue. Per Salesforce: Update: At 17:09 UTC, the third party provider has reported that the issue is resolved and we are validating that all services have returned to normal performance levels. We expect services have returned to normal, but we will leave this outage in a "monitoring" status until full resolved. You may continue to follow live notifications here (https://status.salesforce.com/generalmessages/724).

Salesforce has notified Litify of intermittent outages impacting their site. Due to the relationship between our two platforms, Litify users may expect interruptions to their ability to access the Litify platform while these outages persist. Thank you for your patience while we work with Salesforce to resolve these issues promptly. We will continue to update this posting as more information becomes available, however you can also follow the status of this issue directly here (https://status.salesforce.com/generalmessages/724).

Outage : Resolved Update from Salesforce: The Technology team has confirmed that customers were out of impact as of 18:04 UTC and has called the incident all clear. We sincerely apologize for any impact this issue had on you and your organization. As this incident has been cleared by Salesforce, we will be closing this incident. If you continue to have any issues with your services, please log a case by emailing Litify Support (support@litify.com). ~ The Litify Support Team ~

Dear Litify Admins, Update from Salesforce: The Technology team has given the third-party DNS provider internal domains that need to be allowed. They’ve observed performance improvement and continue to monitor to ensure that trend continues. Customers have also reported improved performance that corroborates internal monitoring. This indicates improvement from the Salesforce end, so we hope and expect services to start resuming for Litify customers as well. Anticipate potentially intermittent services until this outage is cleared. ~ The Litify Support Team ~

Dear Litify Admins, Additional error messages have been reported by users that are related to the ongoing Salesforce outage. These errors should clear after the Salesforce outage is resolved. The following messages are related to the Salesforce outage: Docrio Edit - "Cannot download file for editing: Org is not provisioned" Salesforce/Litify - "We are down for maintenance" In addition, Docrio functionality including "Template Merge" and "Document Downloads" may be intermittent while this outage is being worked on. We apologize for the inconvenience this is causing, and will continue to update you until the outage is resolved. At this point in time, you do not need to log a case with the Support Team. ~The Litify Support Team~

Dear Litify Admins, *Update from Salesforce: The team has determined that additional Salesforce services are impacted, including Heroku, and Pardot is also potentially impacted. The team continues to investigate and had seen improvements, however, a subset of customers may continue to experience intermittent issues while navigating multiple Salesforce applications. If you are still experiencing issues, Salesforce is still working to resolve the issue fully. We will continue to update the outage page here, buy you may also follow updates here ( https://status.salesforce.com/generalmessages/709 )

Litify Admins, Update From Salesforce: The Technology team developed and implemented a change to enable an alternate provider for network traffic and have observed improved network performance. The team continues to monitor to ensure health continues to improve. We've received multiple reports from users that their connections have been restored. We'll fully resolve this outage message once Salesforce clears the outage. Thank you for your patience. ~The Litify Support Team~

Dear Litify Admins, Salesforce is reporting that customers, primarily based on the East Coast are experiencing intermittent connectivity issues when logging into Salesforce. Per Salesforce "A subset of customers within our core production environment, including Government Cloud, will experience intermittent connectivity issues and may see blank pages while navigating multiple Salesforce services. The issue is primarily impacting the Eastern United States." Litify Services that may be temporarily impacted include: - Logging into Salesforce/Litify (mostly for users based in Eastern US) - Litify Inbox (All customers) - Docrio (All customers) This is being addressed by Salesforce as HIGHEST priority. Litify will keep you updated with the outage details on a regular basis until the outage has been resolved. ~The Litify Support Team~

Litify Help Center pages appear to be loading as expected. Our vendor has resolved the service outage. If you have any further issues, feel free to reach out to us at support@litify.com ~The Litify Support Team~

The Litify Help Center is currently not loading certain pages and instead producing an error: "502 Bad Gateway" This does not appear to be impacting the creation of support tickets. We are currently investigating this issue with our vendor and will continue to post updates here until the issues is resolved. We appreciate your patience while we work to resolve this issue. ~The Litify Support Team~

Litify Admins, Around 10:30 AM EST, there was an additional error that was encountered as part of Microsoft Office 365 mail server patch, that could interfere with our Calendar and Email synchronization. For a period of about 1 hour, Synchronization was stopped for all Office 365 users. All of the Litify Inbox add-in component's functions were still available during this downtime. The patch to address this issue was deployed around 11:55 AM been and synchronization is being restored automatically for all users. No further action is required at this time. Once synchronization is fully restored, all emails/events will automatically catch up from when synchronization was stopped. This incident is being backfilled as it was fixed immediately as the issue was uncovered. Thanks for your patience. ~The Litify Support Team~

Litify Admins, A fix has been deployed successfully and our engineering team has confirmed that sync sessions are continuing to return to normal. Thank you for your patience while we worked to resolve this issue. Please reach out to your customer success manage or our support desk (support@litify.com) if you continue to have issues.

Litify Admins, A fix has been implemented and it appears that synchronization is starting to restore for all Litify Users. We will continue monitoring until we have a full confirmation that everything is back up and running. Thank you for your patience while we worked to resolve this issue. ~The Litify Support Team~

Litify Admins, We have just been notified that Microsoft has released an Office 365 mail server patch that could interfere with our Calendar and Email synchronization. To prevent any potential issues we have temporarily stopped Synchronization for all Office 365 users. All of the Litify Inbox add-in component's functions are still available for all users. A few quick notes: 1. As the add in is still 100% available, your employees can continue to use the functionality as they normally would and information will synchronize once we turn the synchronization back on. 2. This only affects Microsoft Office 365 customers. We are working with Microsoft on resolving this issue as quickly as possible. We are actively working on a resolution and fully expect this to be resolved within a few hours. We apologize for the inconvenience. Please reach out to our support desk(support@litify.com) or your customer success manager for more information. We will update the status of this outage regularly until resolution. ~The Litify Support Team~

Update: Salesforce has resolved the outage as of 10:08 PM EST, last night. Litify will be marking this incident as resolved. You may review any outage details and post-mortem information here: https://status.salesforce.com/incidents/7175

Update: Salesforce has not fully resolved the outage, but we believe most if not all Firms are back up and running. Litify will keep this outage notification active until Salesforce resolves the outage. Latest Salesforce Update: The Technology team has identified a clear path to resolution and is making progress in restoring services. We currently don’t have an estimated time on when full recovery is expected. The team is confident that this incident was the result of an internal DNS change. Live update can be follow on Salesforce here: https://status.salesforce.com/generalmessages/697

**Update** While Salesforce hasn't officially resolved the ongoing outage, we are receiving reports that customer accounts are starting to come back online. At this point, you may attempt to log in to your Firm's org to see if you are able to log in successfully. We will keep the outage as active until further verification from Salesforce of the fix. Thank you for your patience.

Salesforce has acknowledged the outage on their status page. Due to the Salesforce status page not loading consistently, we are reposting here: ******** Multiple Salesforce Applications Disrupted User Impact: At 21:46 UTC on May 11, 2021, The Salesforce Technology team became aware of an issue impacting multiple Salesforce services. Customers will experience issues while navigating multiple Salesforce services, including the Core application, Marketing Cloud, Commerce Cloud, and Experience Cloud (fka Communities). The impact is also impacting the Salesforce Trust site, status.salesforce.com is not accessible. Path to Resolution: The team is pursuing multiple paths to resolution and is actively investigating to determine the root cause. Next Update: We’ll provide an update in 30 minutes, or sooner if additional information becomes available. ******* https://status.salesforce.com/generalmessages/697

At around 5pm EST, customers have started reporting issues using Litify. An error is being shown "We are down or maintenance". This is impacting all customers as far as we can tell and this is being investigated with Salesforce at an URGENT priority. You do not need to log a ticket with Litify Support as this issue is related to Salesforce. We apologize for the inconvenience and will keep this updated regularly. You may check for status updates at https://status.salesforce.com/.

We are marking this incident as resolved due to lack of new reports of any ongoing issues. In all reports of the incident, the issue was temporary and resolved within 30 minutes.

Some customers have reported intermittent errors in the Salesforce/Litify. Salesforce has reported an outage in at least one instance. We are monitoring and anticipate Salesforce will resolve all issues in a timely fashion. You may check the the status of your Salesforce instance from https://status.salesforce.com/ . You can type in your firm's domain to check the status of your specific instance (Eg: If your URL is https://myfirmname.lightning.force.com , you can simply search by "myfirm".

Our vendor has resolved the listed outage and we have observed no further issues with ticket creation in Litify Support.

The Litify Support ticketing system has been experiencing intermittent service interruptions over the past few hours. This is a known issue and our ticketing vendor is working to resolve this issue. Please be advised that there may be a delay in receiving ticket requests while this issue is resolved. Once the issue has cleared, this notification will be moved to resolved. Regards, The Litify Support Team

This issue has been solved as of 12:45pm EST. The root cause was an encryption misconfiguration during the deployment of the Fall '20 Update, which lead to a service outage. Steps were taken to resolve the misconfiguration but it required a re-deployment procedure, which took some time due to a slow encryption process. Once re-deployment was completed, the service was fully restored for both add-in and sync. Thank you for your patience.

A fix has been implemented and we are monitoring the results.

We are experiencing a Litify Inbox outage as of 10:00 am EST on 11/04/2020. Check back for updates as we prepare a fix. Thank you for your patience. https://help.litify.com/hc/en-us/articles/360058685273

This incident has been confirmed by the Inbox Engineering team and the Microsoft team as resolved

The Inbox Engineering team has released a fix to solve this problem and is monitoring to ensure sync has resumed for office 365 users. Thanks for your patience while this issue was being addressed. ~The Litify Support Team~

It has come to the attention of the Inbox engineering team that a recent Microsoft update is preventing Litify Inbox users from synchronizing email into Litify/Salesforce. This issue is only impacting a small subset of Litify users at the moment. As Microsoft continues to upgrade Office365 accounts the issue will began to impact more Litify Office365 users. The Inbox team has already identified the cause of the issue and is in the process of testing a fix. We apologize for the inconvenience this has caused and will update this outage page with more details on regular basis until the issues is resolved. No action is needed at this time from your end. ~The Litify Support Team~

Dear Litify Admin, Salesforce has marked this outage as resolved. Root Cause: The problem was caused by a software fault on one node of the database tier. Thanks for your patience while Salesforce worked to resolve this issue. -The Litify Support Team

Dear Litify Admins. Salesforce is currently experiencing an outage on the NA134 datacenter, which is impacting a small subset of our firms. If all of your users are unable to work right now, then likely you are impacted. Most of you receiving this message are NOT impacted. If you are impacted, we suggest that you subscribe to updates from Salesforce regarding this outage here ( https://status.salesforce.com/instances/NA134 ). Click "subscribe" on the top right of the page. Since Salesforce has already identified the outage, you can be sure they are working on this as a URGENT Priority Severity 1 issue and service will be restored ASAP. We apologize for the downtime during this outage. We will keep this post updated on our end as well. Regards, The Litify Support Team

Dear Litify Admin, If you were impacted by the Salesforce NA59 outage, your issue may have been resolved as Salesforce has listed NA59 as operational. We apologize for sending two emails in such short succession, but we are happy this has been reported as resolved. Thanks again for your patience. We still advice that you subscribe to notifications here ( https://status.salesforce.com/instances/NA59 ) so that you are immediately aware of any future issues. Thanks again, The Litify Support Team

Dear Litify Admins. Salesforce is currently experiencing an outage on the NA59 datacenter, which is impacting a small subset of our firms. If all of your users are unable to work right now and are experiencing error messages when trying to load Matters, then likely you are impacted. Most of you receiving this message are NOT impacted. If you are impacted, we suggest that you subscribe to updates from Salesforce regarding this outage here ( https://status.salesforce.com/instances/NA59 ). Click "subscribe" on the top right of the page. Since Salesforce has already identified the outage, you can be sure they are working on this as a URGENT Priority Severity 1 issue and service will be restored ASAP. We apologize for the downtime during this outage. We will keep this post updated on our end as well. Regards, The Litify Support Team

Thank you for your patience while the SpringCM team investigated the issue. The problem is caused by the new "Chrome Same Site Cookies" behavior. You can take the following steps below to solve this problem: 1- On your Chrome Address Bar type "chrome://flags/" without "" 2- A page with flags and a search bar will appear 3- Search for "SameSite by default cookies" 4- Disable this Flag and click Relaunch Chrome The SpringCM team will be working on a fix for a future update that will prevent users from having to make this change.

Some Google Chrome Users are reporting two different issues with the SpringCM Documents Viewer in Salesforce: 1. Clicking a folder may result in a continuous loading box, which does not result in the folder opening 2. When uploading a file, the upload progress bar errors with the message “Your upload failed” These issues have been escalated to the SpringCM team, who are investigating. We apologize for the inconvenience this may have caused. If you are experiencing this issue and you need to upload or access your files, we suggest using an alternative browser, such as Firefox as a temporary workaround. Please verify with your IT if this is an option for you.

This incident has been resolved.

Some firms have reported issues using the Litify Inbox tool. During this time, functionality may be limited. We are actively investigating this issue at the highest priority.

The Litify Referral Network has been restored back to normal operation by the engineering team. We apologize for any inconvenience this has caused.

The engineering team is investigating an issue with the Litify Referral Network. You may not be able to send or receive referrals at this time. We apologize for the interruption and will work to restore service as soon as possible.

Litify Customers, SpringCM has resolved the issue with the following announcement: "The SpringCM Technology Team has resolved the service availability issue on the NA11/NA21 instances. The problem began at approximately 14:45 CST and was resolved at 15:08 CST. During this time customers may have experienced errors accessing the application, reporting issues on the NA21 instance, as well as other issues that will be identified shortly. A full Root Cause Analysis will be posted on this site in the coming days. We apologize for the inconvenience and for any impact this may have caused your organization." You should be able to access your data as usual now. We apologize for any inconvenience this has caused. Regards, The Litify Support Team

Litify Admins - This is a reminder that SpringCM is experiencing an issue in one of their datacenters (NA11). During this outage you will likely not be able to access your documents. Their engineering team is working this on a priority one status! There is no need to send any examples at this time to the Litify Support team. You can follow live updates at: https://trust.springcm.com/na11-service-availability-issue We will also relay updates as they become available here, at status.litify.com Thanks for your patience, and we apologize for the inconvenience. The Litify Support Team

The SpringCM Technology team is working to isolate a service availability issue, on the application on the NA11 instance as of approximately 2:45 CST. During this time, customers may experience inability to access the application. For live updates, please visit https://trust.springcm.com/

The Inbox Engineering team had added additional resources to the synchronization system which has in turn resolved any performance degradation that was experienced during the downtime. If issues are continuing to occur for your firm, please let us know by reaching out at support@litify.com .

We are currently investigating an issue affecting the Litify Inbox product. The engineering team is investigating this on a high priority as service is fully impacted at this time. Updates to follow.

The Litify Inbox engineering team has resolved this issue. You should now be able to use the SpringCM connector within Litify Inbox. If you still are experiencing issues, please reach out to us at support@litify.com.

The Inbox Engineering team has identified an issue and pushed an update that will allow customers to view SpringCM documents within Litify Inbox. At this time, document upload may not work for some customers. The engineering team continues to work towards a final resolution.

We are continuing to investigate this issue.

The Litify Inbox engineering team is investigating an issue with the SpringCM/Documents integration within the Inbox sidebar that is preventing any users from authenticating to SpringCM. During the time, users will be able to use the Inbox core application without issue (Matter/Intake email association), however the SpringCM/Documents connector will be disabled. We ask that during this downtime, you upload documents directly within Litify Documents. *This does not have any impact on the SpringCM app within Litify.

This incident has been resolved.

After some database updates were made around 12pm EDT today, we believe that performance related issues have been resolved. If you are continuing to have issues with LRN performance or server errors, please email support@litify.com.

Thank you for your patience while we continue to investigate and implement a solution. If there are any business stopping issues please shoot an email to support@litify.com so we can help to resolve.

We are continuing to work on a fix for these issues. If there are any business stopping issues please shoot an email to support@litify.com so we can help to resolve.

In addition to error 500s being received, users are reporting that clicking on "Investigate" in the LRN Web app for incoming referrals is resulting in a red server error. This issue is being worked on by engineering. Please note that this issue is intermittent. As a workaround, waiting a minute, refreshing the page, and trying again should work. We apologize for any inconvenience this has caused and will restore full services as soon as possible.

There are reports of excessive errors of the type "LRN Error. Status Code 500/Code 503" that are being sent to customers via email from Salesforce (Litify). Please be advised that this error should be ignored, and does not represent a threat to your data. The engineering team at Litify is addressing the issue and we expect the errors to taper off after some changes are made this afternoon. We will post updates as they are available. If you are having issues sending or receiving referrals you may email your issues to support@litify.com.

Synchronization between the Litify Referral Network and LRN Pro is functioning normally at this moment. If any new issues are noticed, please contact us at support@litify.com with a description of your issue.

A fix has been pushed to production. The issue was impacting Outgoing referrals that were missing a value for "Incident Date". This outage will stay active as we continue to monitor and make sure all outlying issues related to the release have been identified and fixed. Updates to follow.

The engineering team is working to investigate an issue preventing referrals from synchronizing on the the Litify Referral Network relating to a recent release. During this time you may not be able to synchronize some inbound or outbound referrals. Updates will be posted as we work to resolve.

Emergency maintenance performed on database

Something went wrong, and it was resolved

This has been resolved

This is a Salesforce partial outage. Those on the impacted instance may or may not notice any differences. Please review details of out here: https://status.salesforce.com/incidents/4071