Past Incidents

There is a partial outage of ProtonMail and ProtonVPN impacting a significant fraction of users globally. Our engineering team is currently investigating and working on the issue and we will report back when we have more information.

A failure on one of Proton's backend storage devices is making the service unavailable for some users. We have identified the issue and are working on a fix.

Due to an upstream server intervention the ProtonVPN German servers DE#1-4 will be unavailable today for 3 hours starting at 10:00 CEST.

We are performing some maintenance on our storage systems this Sunday between 12-2PM Geneva time which may result in intermittent downtime of some number of minutes for certain users.

Part of the Swiss Secure Core is currently unavailable due to networking issues. The incident is being investigated.

Due to an issue with one of our upstream DDoS protection providers, a very small percentage of users were unable to reach protonmail.com for several hours. The upstream provider has identified and fixed the issue. They are also working on making improvements to prevent this from happening again.

Thank you for your understanding.

To ensure an optimal security level for our users, we are going to perform a reboot campaign on our ProtonVPN servers. Servers will reboot with downtime of approximately 5 minutes/ server. This means users will be gradually disconnected from the respective server.

There should be no issues with reconnecting after the reboot. However, if you're encountering issues reconnecting to the desired server, please contact us at https://protonvpn.com/support-form

We apologize for the inconvenience and we thank you for your understanding. The ProtonVPN Team

Due to some work on our Australia servers, there may be connectivity issues where users are unable to connect to Australia servers. If you experience this problem, we recommend trying to connect manually to different Australia servers as manual connection may work while auto/quick connect could encounter issues. We expect this issue to be corrected by Monday at the latest.