We started checking Proton Mail on November 2, 2026, which is 6 days ago. Everything below covers that period, not the full 90 days a longer-tracked service would show.
Email me when Proton Mail reports an incident on its status page, and again when it reports it resolved.
01
The last 24 hours
What happened most recently, on one time axis: our own probe readings by surface, how many people reported a problem, and what Proton Mail's own status page declared. Below it, any public chatter we saw about Proton Mail and the extra probe it triggered.
The last 24 hours on one axis: what our probes read for each surface we check, how many people reported a problem, and what Proton Mail's own status page declared. Three records side by side; none of them changes another.
Our probes, web
Our probes, api (primary)
Unverified user reportsNo reports about Proton Mail in the last 24 hours, which is not evidence that nothing is wrong.
Proton Mail's status pageNo incident declared in the last 24 hours.
24h ago18h ago12h ago6h agonow
Each check cell is the worst reading across every region in that quarter hour: one region that did not answer colours the cell, never an average. An amber cell is a reading that answered, but at three times or more its 7-day median for three checks running: slow is not down, and we say which. A filtered reading stays neutral, because a refused check is not a failed check. Report bars count reports as submitted; we do not check who sent them, and they never change our reading. The status-page lane is Proton Mail's own declaration, shown as they made it.
Third-party chatter, labeled
Public posts from the last hour that mention Proton Mail next to an outage word (“down”, “outage”, “not working”). This is what other people said in public, collected by keyword: not something we measured, and not the user reports above. It never affects the verdict.
No matching public posts in the last hour from the sources we watch.
02
Checks passing by region
Checks passing is the checks that passed, divided by every check we attempted, per region. Not interpolated, not smoothed, and never computed for a region with zero recorded samples.
Region
Checks passing
Probes recorded
US-East
100.00%
574
US-West
99.77%
430
Europe
100.00%
393
Asia-Pacific
100.00%
236
Their declared record
Proton Mail's own incident history, taken from their public status feed. This is their account of what happened, not our check reading.
Partial outage on Proton VPN serversAll systems operational
Oct 27, 2026, 3:22 PM UTC to Oct 27, 2026, 4:16 PM UTC (54 min)resolved
their latest update (Oct 27, 2026, 4:16 PM UTC): This incident has been resolved.
MacOS Certification Errors on the Proton Meet & Proton Mail appsMajor outage
Oct 2, 2026, 2:54 PM UTC to Oct 2, 2026, 6:11 PM UTC (3h 17m)resolved
their latest update (Oct 2, 2026, 6:11 PM UTC): We've now updated both the Proton Meet and Proton Mail MacOS desktop apps. If you're still receiving a pop-up on your device, please update to the latest version of the desktop apps. Once again, we apologize for any inconvenience this has caused.
Service disruptionPartial outage
Sep 1, 2026, 2:42 PM UTC to Sep 1, 2026, 6:49 PM UTC (4h 8m)resolved
their latest update (Sep 1, 2026, 6:49 PM UTC): UPDATE:
The incident recovery caused some push notifications related to suspicious login activity to be delivered several hours later than expected.
The delay affected only the delivery of these notifications and was related to the service disruption experienced earlier today. T…
Global OutageMajor outage
Aug 26, 2026, 10:18 PM UTC to Aug 27, 2026, 12:27 AM UTC (2h 9m)postmortem published
their latest update (Aug 29, 2026, 6:53 PM UTC): A post mortem of this incident has been made available here: [https://proton.me/blog/august-27-outage-incident-report](https://proton.me/blog/august-27-outage-incident-report)
Partial outage on Proton VPN servers in the Dominican RepublicAll systems operational
Jul 15, 2026, 4:27 AM UTC to Jul 16, 2026, 9:19 AM UTC (1d 4h)resolved
their latest update (Jul 16, 2026, 9:19 AM UTC): This incident has been resolved.
Investigating IncidentMinor incident
Jul 10, 2026, 1:35 PM UTC to Jul 13, 2026, 10:22 AM UTC (2d 20h)resolved
their latest update (Jul 13, 2026, 10:22 AM UTC): This incident has been resolved.
Proton Calendar IssueAll systems operational
Jun 30, 2026, 3:00 PM UTC to Jun 30, 2026, 3:00 PM UTC (0 min)resolved
their latest update (Jun 30, 2026, 3:00 PM UTC): We experienced an infrastructure issue on our API that caused some users to experience an empty Calendar app on Android, with no events or calendars displayed. No data was lost, and all events and calendars remained safe. The underlying issue was resolved at 2026-06-30 19:38 UTC.…
Power outage on Proton VPN servers in North MacedoniaAll systems operational
Jun 29, 2026, 11:49 AM UTC to Jun 29, 2026, 2:30 PM UTC (2h 41m)resolved
their latest update (Jun 29, 2026, 2:30 PM UTC): This incident has been resolved.
Partial outage on Proton VPN servers in Cuba, Honduras, Guatemala and the Dominican RepublicAll systems operational
Jun 25, 2026, 7:30 AM UTC to Jun 25, 2026, 10:16 AM UTC (2h 46m)resolved
their latest update (Jun 25, 2026, 10:16 AM UTC): This incident has been resolved.
Jun 24, 2026, 9:41 PM UTC to Jun 24, 2026, 11:45 PM UTC (2h 4m)resolved
their latest update (Jun 24, 2026, 11:45 PM UTC): All servers have been restored.
Showing the 10 most recent of 50 incidents Proton Mail has declared in the history we hold.
These entries are Proton Mail's own declarations, taken from their public status feed, shown separately from our own check readings. Their page publishes what they choose to publish: an incident missing here means they did not declare one, not that nothing happened, and an incident here is their account, not our measurement. Neither record ever changes the other.
Proton Mail's own status feed works, so its declared incidents are the record and our probe events are not listed or counted. Our check results by region are above, as a reading beside the statement.
Full detail on what a probe does and does not prove is in the methodology page.