FROM ALL SOURCES
No sign of a widespread Proton problem right now; every source we read is quiet.
confidence: medium Vendor: operational · users: normal · routing: no data.
- Vendor status page Operational · 1 open incident
- User reports 0 in 15 min vs ~0 typical
- Routing / BGP no ASN mapped, so no routing view
- News & network weather no recent mentions
- Providers it may run on (inferred) no mapped dependencies
- CISA KEV (context) no recent entries for this vendor
Regions mentioned: Web Application, Free servers, Mobile Apps
| Clock | Started | Running |
|---|---|---|
| Vendor clock when the vendor's open incident started | 86 days | |
| Crowd clock when user reports began rising above normal | not seen | n/a |
| Network clock when routing anomaly data first flagged it | not seen | n/a |
| ORBIT clock when our checker first recorded the change | not seen | n/a |
Evidence
- Official page: Operational (“All Systems Operational”). evidence confidence: high
- Vendor stage: postmortem on “Global Outage”. evidence confidence: high
- User reports are within normal range (0 in 15 min). evidence confidence: low
What we don't know: what is happening inside Proton's own systems, how many users are actually affected (reports are self-selected and unverified), and anything from routing / bgp, providers it may run on (inferred). Routing data shows reachability, not whether the app works.
Automated analysis by Cloudy_Day NetWeather; not a personal statement. Generated .
Cloudy_Day's take
Stage vs. health
The vendor's stage is “postmortem”. Stage tells you where they are in their process; health is what users experience. Right now vendor: operational · users: normal · routing: no data. Vendor status and outside signals roughly agree.
Who depends on whom
We don't map other services that depend on Proton. Dependency chains are where single points of failure hide.
Identity & trust lens
When Proton has trouble, people see failed logins, MFA prompts that don't arrive and sessions that drop. That's when phishing pages and “verify your account” texts show up. Only sign in through the official app or site, and don't re-enter credentials from a link someone sends you.
For users
Nothing points to a broad problem. If it's broken for you, try “Is it just me?” and check your own network first.
For security teams
Treat this as an availability event unless an official source says otherwise. Check which of your systems sit on Proton, watch for outage-themed phishing aimed at your users, and log what you see with timestamps (all four clocks).
What to watch next
Any new vendor incident, a jump in user reports above baseline, or trouble at the providers Proton may depend on.
Automated analysis by Cloudy_Day NetWeather; not a personal statement. Independent researcher; not affiliated with Proton. No blame or attack claims without an official source. Generated .
INCIDENT REPLAY
Global Outage
critical postmortem · started · resolved
9 updates
- investigating
We are currently investigating this issue.
- investigating
We are continuing to investigate this issue.
- investigating
We are continuing to investigate this issue.
- investigating
It appears that Proton VPN works for some, so it has been changed to "Partial Outage" rather than "Major Outage"
- identified
We have identified a critical cooling failure in our Frankfurt datacenter. We are currently in the process of shifting traffic to our backups sites.
- identified
Our efforts to restore impacted services are now yielding results, and as a result are starting to recover for some users. Meanwhile, we are continuing recovery operations.
- monitoring
A fix has now been implemented, and we're monitoring results. This means most services have been recovered for most users now, but our efforts to recover the remaining instances continue.
- resolved
This outage has now been largely resolved, and services are back online. We are still clearing a few lingering issues, however, meaning some users will experience delays in email delivery and reception, and receiving notifications. No data has been lost as a result of this outage. UPDATE: We have now resolved the remaining minor issues. We will be providing a post mortem with more information about the incident, here on the status page, after we complete the incident clean up.
- postmortem
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)
Community comments (0)
Comments are opinions of visitors, not statements by Cloudy_Day. Every comment is held for review before it appears. Links are removed, and personal data is redacted. Community guidelines.
No approved comments yet.
How to read this: official status comes from each provider's own public status page. User reports are unverified visitor reports. Things that happen at the same time are coincidence, not causation. Cloudy_Day is independent and not an official status source for any company listed.