I mean, no one cares if accessing mail is down, but it looks like their MX is down, the status page reports incoming mail has a ‘partial’ outage.<p>I don’t care if I can’t access my email for a while.<p>I very much care if email sent to me isn’t received. They should just be dumping all mail received at their MX’s to maildirs or something if it’s this bad and process them properly later. Losing data is not ok.
"<i>Proton Mail mobile apps are are now operational again, and so is Proton Calendar.</i>"<p><a href="https://nitter.net/ProtonSupport" rel="nofollow">https://nitter.net/ProtonSupport</a><p>also RSS feed:<p><a href="https://nitter.net/ProtonSupport/rss" rel="nofollow">https://nitter.net/ProtonSupport/rss</a>
I'm kind of curious what the source of the outage is.<p>It looks like most of their services are down, including their incident status page¹. The number of things I can think of that so many different services & are not a massively catastrophic failure is pretty small. Though that may be a lack of imagination on my part.<p>1: <a href="https://status.protontech.ch/incidents/195" rel="nofollow">https://status.protontech.ch/incidents/195</a>
2 things to ask.<p>1. why don't people selfhost email more? mailinabox is pretty painless to set up and would give you infinitely more security/privacy whatever you want.
2. why is email deliverability still an issue? why do you need to use third party email tools to ensure your email doesn;t go to spam? i am not concerned with newsletters/ads/ that sort of thing but a replacement to gmail/protonmail??<p>i have personally gone with miab like last year and beyond the first few weeks of gmail putting my emails into spam(then having to inform the other user to unspam it), things have been painless. i get to occasionally spin up the ssh to update the server but its fine. backblaze b2 backups ensure i am somewhat safe(er). can it be better? yes. is it ready to be used in production, aka a replacement to your regular paid/free email? you be the judge but i am sold on this idea
It has gone down again today.<p>Their statement yesterday:<p>Yesterday we unfortunately experienced technical difficulties which meant that Proton services were offline intermittently throughout the late afternoon and evening European time. During this period, incoming email, outgoing email, and push notifications were also temporarily delayed. As of 2:45AM Geneva time, all emails and notifications are caught up, but we are continuing to monitor the situation in case of further faults.<p>We can confirm that no data and no emails were lost. Due to our redundant infrastructure, emails that were not immediately delivered were queued and automatically redelivered. We are still investigating the issue, but what we can share so far is that the technical difficulties were caused by a software update that was conducted over the weekend which adversely impacted the performance of certain systems. Unfortunately, this issue only appeared under under high loads which we were not able to fully simulate in testing. Furthermore, because this was a major software and operating system upgrade, there was no way to roll back the software update.<p>This result of this was an extended period of intermittent outages and performance issues while we tried to work around the issue. We have now put a number of safeguards in place, and will continue to improve the reliability of our infrastructure to guard against this type of issue in the future. We apologize deeply for this issue and thank you again for your understanding. Our engineering team is currently conducting a root cause analysis and for transparency, we will be sharing results on the Proton blog after our investigation is complete.
>there was no way to roll back the software update<p>oof<p>>During this period, incoming email, outgoing email, and push notifications were also temporarily delayed<p>They say no data was lost but I'm not sure how they can know a sending mail server didn't give up trying to deliver a message to Proton
Looks like it's down again: "Some systems are experiencing issues" [1]<p>------<p>[1] <a href="https://protonstatus.com/" rel="nofollow">https://protonstatus.com/</a>
Has to be related to this maintenance announced a couple days ago[1]<p>> <i>"We're conducting a short database intervention on Sunday, July 10th, 2022, between 9:00 - 10:00 am GMT+2. During this time, users will be unable to access all Proton services for 2-4 minutes. We apologize for the inconvenience."</i><p>[1]: <a href="https://twitter.com/ProtonSupport/status/1545698028895584257" rel="nofollow">https://twitter.com/ProtonSupport/status/1545698028895584257</a>
Rather ironically, the site they link to for the incident status updates ( <a href="https://status.protontech.ch/incidents/195" rel="nofollow">https://status.protontech.ch/incidents/195</a> ) is not loading for me: "The connection has timed out"
Sorry about that.<p>I just moved the domain for my small business over to ProtonMail (where I already hosted my personal email). The fact that I did that guaranteed that it would go down. :)
Seems like it’s not yet completely sorted… despite being impacted, i feel for the guys steering through this outage and bending backward! Good luck guys!
Irony is the people most likey affected by a protonmail outage would be political staffers and strategic PR firms who would suddenly need to use messengers subject to disclosure.<p>As someone taken out by the Rogers outage last week, I'd be concerned the infrastructure of western powers may be too fragile to project power in a seriously contested conflict.
Just remember, clicking on refresh and searching the net what is going on want make the problem go anyway faster. Few of us urgently depend on email just this hour. An even if you do setting your alarm to some suitable interval and just doing something else is much more productive. Just act like the Arab cliche taxi driver who takes the hands of the steering wheel when it gets tight and say Allah will steer (No insult to anyone, I have never visited any Arab country. Probably the story is not true anyway, but a nice anecdote to accept things you cannot change.)<p>When hackernews was down recently I wanted to report it as big news in our company chat. But it was rather late here and I had already closed all work stuff for the weekend. So I first slept and when I woke up everything was working again. Oh yeah, I missed to share the scoop with my colleagues, but I guess I'll manage without any damage to my professional reputation.<p>Edit: Reading post-mortem afterwards is a different story. If it's well written instead of some corporate communications emptyspeak one can learn something. No mistake happens only once.