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 | 80 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: resolved on “Service disruption”. 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 “resolved”. 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
Service disruption
major resolved · started · resolved
5 updates
- investigating
We’re aware that a small number of users may be experiencing issues accessing Proton services. Our team is investigating and we will share updates here as soon as possible. We apologize for the inconvenience.
- investigating
We are currently dealing with residual hardware failures that are likely related to the damage suffered from the overheating incident last week. At the moment we are operating at a reduced capacity, while our engineers work to bring additional infrastructure online. We apologize for the unfortunate timing of this incident and any disruption or inconvenience this may have caused you.
- identified
Database capacity is being restored. Traffic limitations are being gradually lifted and outgoing mail will be re-enabled as soon as the situation is stable. Queued emails will be delivered progressively, and no data was lost as a result of this disruption. Thank you for your patience, we'll update you again once everything is back to normal.
- monitoring
Traffic limitations have been fully removed for all users. Services are returning to normal operation, and outgoing mail will be gradually re-enabled in 15 minutes. Messages that were queued during the disruption are being delivered progressively Our engineers continue to monitor the infrastructure closely as capacity returns to full levels. We'll confirm here once everything is completely back to normal.
- resolved
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. The delayed notifications have now been processed, and the system has returned to normal operation. We apologize for any confusion this may have caused. --- Earlier today, a subset of Proton users experienced intermittent service disruptions. The incident began during exceptional database maintenance following last week's datacenter overheating incident. The maintenance had been tested and was expected to cause only a brief disruption. However, the switchover exposed additional instability under high load, and this forced us to remove some additional infrastructure from service and operate at reduced capacity for a
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.