Radek
My feedback
34 results found
-
141 votes
An error occurred while saving the comment An error occurred while saving the comment Radek
commented
It is interesting that Proton has had IPv6 prefixes since at least 2014, but they don't seem to be using. You can see this in the list of originated prefixes on their AS:
Radek
supported this idea
·
-
1,374 votesRadek
supported this idea
·
-
856 votesRadek
supported this idea
·
-
465 votesRadek
supported this idea
·
-
185 votesRadek
supported this idea
·
-
9 votesRadek
supported this idea
·
-
6 votesRadek
supported this idea
·
-
4 votesRadek
supported this idea
·
-
26 votesRadek
supported this idea
·
-
8 votesRadek
supported this idea
·
-
20 votesRadek
supported this idea
·
-
7 votesRadek
supported this idea
·
-
14 votesRadek
supported this idea
·
-
25 votesRadek
supported this idea
·
-
16 votesRadek
supported this idea
·
-
1,514 votesRadek
supported this idea
·
-
2,053 votesRadek
supported this idea
·
-
5,115 votes
ProtonMail offers encrypted contacts for both web and mobile applications (https://protonmail.com/blog/encrypted-contacts-manager/). Calendar and note functionality will be released in the future.
Radek
supported this idea
·
-
3,789 votesRadek
supported this idea
·
-
1,199 votesRadek
supported this idea
·
I have contacted Proton about not being able to use their services properly on my IPv6-only ISP in February 2026, this is an excerpt from the response I received:
As mentioned, IPv6 support for Proton services is actively monitored and discussed internally, but at this time we do not have a publicly shareable timeline or commitment for enabling native IPv6 connectivity across Proton Mail, Drive, or other services. We avoid publishing roadmap details unless implementation is confirmed and scheduled.
It is acknowledged internally that users without reliable IPv4 connectivity may experience reduced performance or reliability when accessing Proton services. While the majority of users still operate in dual-stack or IPv4-capable environments, we recognize that this balance is shifting over time.
Proton services operate on a complex, security-focused infrastructure that includes encryption layers, traffic filtering, DDoS mitigation, abuse prevention, and global routing controls. Enabling IPv6 is not a matter of address availability alone, it requires ensuring parity in security, reliability, monitoring, and abuse resistance across both protocol stacks. These requirements significantly increase the scope and risk of deployment compared to many conventional web services.
For users who do not have native IPv4 connectivity, the most reliable way to use Proton services today is to make sure your network supports both IPv4 and IPv6, or to use a VPN that provides IPv4 access. This helps prevent slow or failed connections that can happen when your internet tries to convert IPv6 traffic to IPv4. Other than these options, there is no workaround on the Proton side, since our services currently rely on IPv4 for full functionality.
We continue to monitor IPv6 adoption and consider its implementation carefully, but we do not have a timeline for enabling full IPv6 support.