Help and Support More From Encyro

    Encyro Status

    Status

    For ongoing outages we will attempt to update this page or post on our Facebook page.

    Please feel free to contact us if you are experiencing any issues with Encyro. We will investigate and respond to you as soon as possible.

    Status History

    On Friday February 27, 2026, from 12:20pm to about 2:30pm Pacific time (about 2 hours), the SMS sending service experienced an outage. Most users were not affected. If a user was already logged in, they were not affected. New log in attempts where the user had SMS as their only MFA method were affected. We strongly recommend that you also set up an Authenticator app as an MFA method to avoid being locked out of your account in case of issues receiving SMS messages, regardless of whether it is due to an outage or simply cellular network delays.

    On Saturday February 7, 2026, the Encyro web application was not accessible due to an outage at the Microsoft Azure region that Encyro uses. The outage lasted from 12am to 10am PT.

    On Wednesday October 29, 2025, access to files stored in Encyro as well as the ability to upload new files was severely affected. The reason was that the underlying cloud storage service that Encyro uses, Microsoft Azure, had a major DNS related outage. Many services that rely on Microsoft Azure were affected worldwide. The issue started around 8am PT. Partial recovery was observed around 1pm PT and full recovery was verified at 4pm PT.

    On Thursday December 12, 2024, Encyro users experienced problems logging in. Encyro relies on Amazon Web Services (AWS) for authentication and the AWS cloud service that we use was affected, from about 5pm PST to 8pm PST. The login issues were resolved automatically as soon as the AWS cloud service was restored.

    While downtime is never fun, we are pleased with our vendor’s prompt attention to the matter and quick resolution.

    On Thursday January 25, 2024, Encyro experienced a severe degradation in the backend that prevented users from using the website normally. Most users could login but after the login, the data would usually not load (though it did load for some users). The degradation lasted from 10am PT (or earlier) to about 2pm PT.

    • An alert notice was placed in the logged-in view on the website informing users about the issue.

    • The cause of the issue was determined to be outside of Encyro software. Working with Microsoft Azure support, the cause was found to be a runtime update in the Microsoft Azure platform that was not working correctly.

    • A mitigation was put in place and normal operation was restored around 2pm PT (Jan 25).

    • The alert notice was removed from the website at 2:20pm PT. Customers who had contacted support were responded to by 3pm PT.

    • Jan 26, 2024: Encyro is continuing to work with Microsoft Azure support to understand the issue in more depth and determine if automated mitigations are feasible.

    • Jan 30, 2024: While the initial mitigations helped improve the situation, the degradations did re-appear sporadically during high load times. A more permanent fix was deployed on Jan 30 around 8:20am PT. This has resolved the issue.

    • Jan 31, 2024: Continued monitoring of the issue confirms that the fix is working as intended.

    On Tuesday June 13, 2023, we experienced a service degradation in the login and signup service component from around 12:30pm PT to 1:41pm PT.

    • Users who were already logged in could continue to use the service normally but new logins, signups, and password resets were affected.
    • The cause of the issue was a degradation in the underlying infrastructure that Encyro uses from one of our cloud providers (Amazon Web Services). News reports indicated that the issue affected many websites including the New York Metropolitan Transportation Authority, Southwest Airlines, The Verge, The Globe, among others.

    On Saturday, Aug 27, 2022 we had a corporate email degradation, between 11am and 6pm.

    • Encyro services (website, Gmail and Outlook addons) and related email notifications were NOT affected.
    • The communications through our Support website were NOT affected.
    • However, if you were in touch with our staff via their direct email address, or sent a plain email (non-encrypted) to our info@ group, then those emails may not have been delivered. If you have not received a response in the expected time, please re-send your email. This is only for emails that you sent on Saturday, Aug 27.

    Related articles