Proton Mail service status
Check whether the provider lists a problem with the feature you use. Look at the update time and any affected regions.
Live Domain Check
Run a live reachability check for proton.me. Compare the regional responses with the problem you see in Proton Mail.
Find Proton Mail help and reporting links, specific checks, and step-by-step guidance below the live result.
Checking reachability from multiple regions.
Share a quick update and see what other visitors are experiencing.
What’s happening? Choose one to send your report.
Loading community reports…
—problem reports
—working reports
No problems reported in this period.
Visitor reports are separate from our automated checks and don’t confirm an outage. How reports work · Privacy
Proton Mail, Drive, VPN and account access are separate products; a proton.me response does not test them all.
The checker above requests proton.me from eight configured locations and shows the responses and measurement times. Compare those observations with the actual Proton Mail action that failed. A homepage response alone cannot verify an account, app workflow or transaction.
Looking for another service? Browse messaging checks.
Check whether the provider lists a problem with the feature you use. Look at the update time and any affected regions.
Choose Proton Mail, Drive, VPN or the actual product involved.
Open the website in your browser and compare it with the result above.
Open Proton Mail help / reporting. Use the provider's customer-service or account-help route for the affected product. Sign-in may be required for private account questions.
Product, client/version, failed send/sync/connect action, error and timestamp without private contents.
Attach the checker’s downloaded JSON if it helps show the hostname, regional responses and original timestamps. Describe what happened in your browser or app as well. A report sent to WebsiteDown.org is not automatically forwarded to Proton Mail.
These are troubleshooting comparisons, not claims that Proton Mail is currently experiencing a particular incident.
Identify the product and compare its web interface with another authorised client where available.
Use the matching Proton status/support component; retain drafts or unsynced files before reconnecting the account.
A 403 Forbidden or 429 Too Many Requests means the host answered but refused or limited that request. A timeout gives no HTTP response. Keep those outcomes separate and check the available-region count before treating the result as broad evidence.
Use these local troubleshooting steps after the down-check workflow when Proton Mail seems broken only for you. This section focuses on app, browser, account, and network fixes.
Open proton.me in your current browser, then test in a private window or second browser. If only one session fails, compare its account, cookie and extension context before assuming the entire service is unavailable.
Keep an existing working session and preserve unsaved work. For a sign-in failure, use the official account-help route. Avoid repeated password or security resets until you confirm this is not a broader Proton Mail issue.
If possible, compare Wi-Fi with mobile data and note which one fails. Leave any required work VPN or security settings in place.
Save timestamp, device, network type, exact error, final URL, and status code. Use the check workflow above before contacting Proton Mail support.
Run the proton.me check and compare its original timestamps and responses with your actual error. Proton Mail, Drive, VPN and account access are separate products; a proton.me response does not test them all.
Use the community buttons on this page to share whether the service works for you. For help from Proton Mail, use the official help/reporting resource linked above. Choose Proton Mail, Drive, VPN or the actual product involved.
Identify the product and compare its web interface with another authorised client where available. Use the matching Proton status/support component; retain drafts or unsynced files before reconnecting the account.
Product, client/version, failed send/sync/connect action, error and timestamp without private contents.