All Systems Operational

About This Site

This site shows the current status of Proton services.
For more information, follow us on Twitter: @ProtonSupport.
This site does not update in real time so information may be delayed. Refresh to get the latest status.

Proton Mail Operational
Web Application Operational
Incoming Mail Operational
Outgoing Mail Operational
Bridge Operational
Mobile Apps Operational
Push Notifications Operational
Desktop Apps Operational
Proton VPN Operational
Free servers Operational
Regular Servers Operational
Secure Core Servers Operational
Streaming Operational
Mobile and Desktop Apps Operational
Browser Extensions Operational
protonvpn.com Website Operational
Proton Calendar Operational
Mobile Apps Operational
Web Application Operational
Proton Drive Operational
Web Application Operational
Mobile and Desktop Apps Operational
Proton Pass Operational
Mobile Apps Operational
Browser Extensions Operational
SimpleLogin ? Operational
proton.me Website Operational
Proton Wallet Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Past Incidents
Jan 16, 2025

No incidents reported today.

Jan 15, 2025

No incidents reported.

Jan 14, 2025

No incidents reported.

Jan 13, 2025

No incidents reported.

Jan 12, 2025

No incidents reported.

Jan 11, 2025

No incidents reported.

Jan 10, 2025

No incidents reported.

Jan 9, 2025
Technical difficulties
Resolved - Incident report:

Earlier today at around 4PM Zurich, the number of new connections to Proton's database servers increased sharply globally across Proton's infrastructure.

This overloaded Proton's infrastructure, and made it impossible for us to serve all customer connections. While Proton VPN, Proton Pass, Proton Drive/Docs, and Proton Wallet were recovered quickly, issues persisted for longer on Proton Mail and Proton Calendar. For those services, during the incident, approximately 50% of requests failed, leading to intermittent service unavailability for some users (the service would look to be alternating between up and down from minute to minute).

Normally, Proton would have sufficient extra capacity to absorb this load while we debug the problem, but in recent months, we have been migrating our entire infrastructure to a new one based on Kubernetes. This requires us to run two parallel infrastructure at the same time, without having the ability to easily move load between the two very different infrastructures. While all other services have been migrated to the new infrastructure, Proton Mail is still in middle of the migration process.

Because of this, we were not able to automatically scale capacity to handle the massive increase in load. In total, it took us approximately 2 hours to get back to the state where we could service 100% of requests, with users experiencing degraded performance until then. The service was available, but only intermittently, with performance being substantially improved during the second hour of the incident, but requiring an additional hour to fully resolve.

A parallel investigation by our site reliability engineering team identified a software change that we suspected was responsible for the initial load spike. After this change was rolled back, database load returned to normal. This change was not initially suspected because a long period of time had elapsed between when this change was introduced and when the problem manifested itself, and an initial analysis of the code suggested that it should have no impact on the number of database connections. A deeper analysis will be done as part of our post-mortem process to understand this better.

The completion of ongoing infrastructure migrations will make Proton's infrastructure more resilient to unexpected incidents like this by restoring the higher level of redundancy that we typically run, and we are working to complete this work as quickly as possible.
Jan 9, 21:49 CET
Monitoring - We have resolved all service outages, and the situation has been stable for some time. We have identified the root cause of the problem, implemented a fix, and are now monitoring the results.
Jan 9, 19:27 CET
Update - We are continuing to work on a fix for this issue.
Jan 9, 19:00 CET
Update - Access to Proton Mail has been fully restored, and we can confirm that it is now operating normally. We are working on a solution for Calendar and will be back soon with more information.
Jan 9, 18:37 CET
Identified - As of 16:15 CET, all services other than Mail and Calendar are operating normally. We are still working on fixing the issue and restoring the rest of the affected services. We'll come back with more information in the next update. Thank you for your patience.
Jan 9, 17:42 CET
Update - We are continuing to investigate this issue.
Jan 9, 16:27 CET
Investigating - We are currently experiencing intermittent network issues affecting some of our users. We are working to fully restore services as soon as possible. We apologize for the inconvenience.
Jan 9, 16:10 CET
Server outage on ProtonVPN servers in Bosnia and Hercegovina
Completed - The scheduled maintenance has been completed.
Jan 9, 11:15 CET
Scheduled - Proton VPN servers in Bosnia and Hercegovina are currently unavailable. We are working with the upstream datacenter in order to solve the issue as soon as possible. We apologize for the inconvenience.
Jan 9, 08:20 CET
Jan 8, 2025

No incidents reported.

Jan 7, 2025

No incidents reported.

Jan 6, 2025
Partial outage on ProtonVPN servers in Netherlands
Completed - The scheduled maintenance has been completed.
Jan 6, 14:45 CET
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jan 6, 11:59 CET
Scheduled - Some Proton VPN servers in Netherlands are currently unavailable. We are working with the upstream datacenter in order to solve the issue as soon as possible. We apologize for the inconvenience.
Jan 6, 11:58 CET
Jan 5, 2025

No incidents reported.

Jan 4, 2025

No incidents reported.

Jan 3, 2025

No incidents reported.

Jan 2, 2025

No incidents reported.

← Incident History Powered by Atlassian Statuspage