Back to protonmail.com logo

This site shows the current status of ProtonMail and ProtonVPN services.

For more additional information, follow us on Twitter: @ProtonMail & @ProtonVPN.

This site does not update in real time so information may be delayed. Refresh to get the latest status.
All systems are operational

Past Incidents

Wednesday 20th February 2019

VPN Service ProtonVPN Korean server shut down for maintenance

The ProtonVPN Korean server will be shut down for a couple of days to perform a hardware intervention. Service on the Korean server will resume as soon as the scheduled maintenance is over. Other servers should not be affected.

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

If you have questions or encounter issues with the other ProtonVPN servers, please don't hesitate to contact us at protonvpn.com/support-form

Regards, The ProtonVPN Team

Tuesday 19th February 2019

VPN Service ProtonVPN Servers Update

To ensure an optimal security level for our users, we are performing a reboot campaign on our ProtonVPN servers. Servers will reboot one by one with downtime of approximately 2 minutes/ server. This means users will be gradually disconnected from the respective server. Maintenance will end on Wednesday, February 20th, 7 am UTC.

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

Tuesday 5th February 2019

VPN Service ProtonVPN Connectivity Issues

There are currently issues connecting to ProtonVPN servers. Our engineering team is currently looking into this and will update as soon as we have more information.

Sunday 27th January 2019

Planned Maintenance

Between 6:30 and 9:30AM Geneva time today, there may be a few minutes of scattered downtime for certain users as we conduct some planned maintenance.

Monday 21st January 2019

ProtonAPI Outage

Between 9:55AM - 10:24AM Geneva time, the Proton API had an outage. All services are now operational and no emails or data were lost. We apologize for the inconvenience.

The root cause is a critical bug in the MySQL software published by Oracle. This software bug was also responsible for a previous incident in December: http://protonstatus.com/incidents/20#update-21 This bug occurs intermittently and can lock entire MySQL instances, but while in this state, MySQL does not gracefully exit, but will continue to accept connections which hang.

Unfortunately, it took us some time to trace the problem within the MySQL software. Upon completion of that, we proceeded to upgrade all MySQL replica slave instances in our infrastructure. Unfortunately, we still didn't yet have sufficient time to implement the fix on the MySQL master instances. This operation was actually scheduled for this week, as it was waiting for critical security/reliability patching to take place on our network equipment first. Unfortunately we had bad luck and this morning the issue reoccurred on one of the master instances which didn't yet have the patch. Upon completion of the patching this week, we believe this particular critical MySQL bug should be resolved. We are monitoring this situation closely and will also communicate with the software vendor about this issue.

Tuesday 15th January 2019

ProtonMail Bridge ProtonMail Bridge Outage

ProtonMail Bridge is currently experiencing connectivity problems. We are investigating the problem and will report back as soon as we know more.

VPN Service ProtonVPN Outage

There is a problem authenticating and connecting to ProtonVPN servers. Our team is currently investigating the issue and will update when we know more.

Saturday 8th December 2018

Site Outage

There is an error with the Proton backend. Our infrastructure team is currently investigating and we will report back when we have more information.

Monday 26th November 2018

Issues with the Proton API

The Proton API is experiencing issues. Our infrastructure team is currently investigating and will update when we have more details.