Pricing
Status historyRSS updatesStatus API

Powered by Uptimus

    Encryptme outage history

    7 recorded Encryptme incidents since June 2020, with official updates, affected components, duration and resolution information.

    Back to current status

    Email Message Delays

    Started April 8, 2026 at 7:31 PM UTC · 4h 33m

    IssuesMinor incident
    Affected components
    Support
    1. April 8, 2026 at 7:31 PM UTCidentified

      An ongoing Google-related issue with email messages has resulted in extended delays in response. You can check the status of the issue here - https://www.google.com/appsstatus/dashboard/incidents/224ozRqzW4sFBDK8hLnT

    2. April 9, 2026 at 12:03 AM UTCresolved

      Google has indicated that the issue has been resolved.

    Service impacting situation for Amsterdam, Netherlands

    Started February 25, 2026 at 3:40 AM UTC · 168d 14h

    IssuesMinor incident
    Affected components
    Web
    1. February 25, 2026 at 3:40 AM UTCinvestigating

      We are currently investigating a potential service impacting situation for Amsterdam, Netherlands. There is intermittent packet loss at this location that is affecting connections to some of the servers.

    2. August 12, 2026 at 6:15 PM UTCresolved

      This incident has been resolved.

    Certificate Error

    Started February 2, 2026 at 8:25 PM UTC · 17h 36m

    OutageMajor incident
    Affected components
    WebSupport
    1. February 2, 2026 at 8:25 PM UTCinvestigating

      We are currently investigating an issue that is related to security certificates causing customer connection errors. We will provide an update when more information is available.

    2. February 3, 2026 at 2:01 PM UTCresolved

      This incident has been resolved.

    Live Chat

    Started July 17, 2024 at 12:53 AM UTC · 2d 4h

    Pending
    Affected components
    Support
    1. July 17, 2024 at 12:53 AM UTCmonitoring

      A recent upgrade requires that certain aspects of live chat be re-configured before being re-enabled. Please utilize our helpdesk and ticketing system as alternatives in the mean time. We appreciate your patience.

    2. July 19, 2024 at 5:08 AM UTCresolved

      Functionality to the chat system has been restored.

    Unable to connect to servers

    Started June 7, 2023 at 11:41 PM UTC · 13h 35m

    Pending
    1. June 7, 2023 at 11:41 PM UTCinvestigating

      We are currently investigating this issue.

    2. June 8, 2023 at 12:15 PM UTCmonitoring

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

    3. June 8, 2023 at 1:16 PM UTCresolved

      This incident has been resolved.

    London servers stability issue

    Started June 17, 2022 at 4:12 PM UTC · 3h 35m

    OutageMajor incident
    Affected components
    IPsec (iOS + Windows)OpenVPN (MacOS + Android)
    1. June 17, 2022 at 4:12 PM UTCinvestigating

      We are currently investigating an issue in our London data center that is causing some servers to drop vpn connections.

    2. June 17, 2022 at 4:31 PM UTCidentified

      We have identified an issue with a driver that did not update properly after our last server maintenance. A fix is been deployed followed by a restart of the London servers to correct this issue.

    3. June 17, 2022 at 5:25 PM UTCmonitoring

      Fix has been deployed to all London servers.

    4. June 17, 2022 at 7:47 PM UTCresolved

      This incident has been resolved.

    Elevated IPSec Login Errors

    Started June 15, 2020 at 2:01 AM UTC · 13h 0m

    OutageCritical incident
    Affected components
    IPsec (iOS + Windows)
    1. June 15, 2020 at 2:01 AM UTCidentified

      We're experiencing an elevated level of login errors pertaining only to IPSec connections (iOS + Windows) and are currently looking into the issue.

    2. June 15, 2020 at 3:04 AM UTCmonitoring

      A fixed has been identified and is being deployed currently.

    3. June 15, 2020 at 5:14 AM UTCinvestigating

      We believed this fix would address the issue but we are rolling back our change. We are back in the investigation phase.

    4. June 15, 2020 at 6:55 AM UTCinvestigating

      We are continuing to investigate this issue.

    5. June 15, 2020 at 8:20 AM UTCidentified

      The issue has been identified and a fix is being implemented.

    6. June 15, 2020 at 8:31 AM UTCidentified

      We are continuing to work on a fix for this issue.

    7. June 15, 2020 at 2:17 PM UTCidentified

      We have fixed the issue and are deploying it in stages worldwide. We are sincerely sorry for how long this has taken.

    8. June 15, 2020 at 2:29 PM UTCidentified

      50% of the servers have the fix in place. We expect to be completed in the next 20-30 minutes.

    9. June 15, 2020 at 3:01 PM UTCresolved

      All of the servers have the fix in place. We will continue to monitor the situation, and if something arises we will let you know.