atYevP

Yev from Backblaze here -> I apologize for this mistake. We've updated the post with additional information now that we have it and there's also an apology.

Yev from Backblaze here - with sincere apologies. After we removed the offending code on Sunday night we went into investigation mode and conducted a rca - we wanted to get some kind of blog post out there so that folks could see that we were working and investigating the issue. I will grant you that maybe our initial execution on that was lackluster, but we wanted to make sure we had a better handle on what we were talking about. We've since updated the blog with additional information, you can read those here: https://www.backblaze.com/blog/privacy-update-third-party-tr....

Yev from Backblaze here -> thanks for being a Backblaze customer. We've finished our root cause analysis and have updated that blog post with additional information. We also have moved domain registrars to make sure that behavior doesn't happen again. Sincere apologies for the issues you've experienced.

Yev from Backblaze here - We've updated the blog post with additional information after completed our root causes analysis. You can read the updates: https://www.backblaze.com/blog/privacy-update-third-party-tr....

Yev from Backblaze here -> I chimed in below but wanted to let you know hat we've finished our root cause analysis and have updated our blog post with some additional information: https://www.backblaze.com/blog/privacy-update-third-party-tr....

Yev here - Tobr, thank you for being a customer. Wanted to let you know that we've updated our blog post after finishing our root cause analysis. You can read about what happened here: https://www.backblaze.com/blog/privacy-update-third-party-tr....

Yev here -> thanks for being a customer! We've finished our root cause analysis and updated our blog post with additional information -> https://www.backblaze.com/blog/privacy-update-third-party-tr....

Yev here -> we've since finished our root cause analysis and have updated our blog with additional information that you can find here: https://www.backblaze.com/blog/privacy-update-third-party-tr...

Yev here -> thank you for being a customer! We just finished root cause analysis and have updated our blog post with additional information -> https://www.backblaze.com/blog/privacy-update-third-party-tr...

Yev here -> thank you for being a customer. Wanted to let you know that we've finished our root cause analysis and have updated our blog post with additional information -> https://www.backblaze.com/blog/privacy-update-third-party-tr....

Yev here -> I think part of that was a mistake on the Twitter side of things. We've published a blog post with information after finishing our root cause analysis -> https://www.backblaze.com/blog/privacy-update-third-party-tr....

Yev here -> we wanted to make sure we were able to investigate the root cause so we knew what we were talking about. We've completed that root cause analysis and have updated our blog post with additional information -> https://www.backblaze.com/blog/privacy-update-third-party-tr...

Yev here - :)

Yev here -> Absolutely here you on that. We wanted to make sure we knew what we were talking about before we made any declarative statements. We just finished our root cause analysis and updated our blog post with updated information: https://www.backblaze.com/blog/privacy-update-third-party-tr....

Yev here -> we've published a blog post that has our findings thus far, we're still investigating and will be updating that post: https://www.backblaze.com/blog/privacy-update-third-party-tr....

Yev here with a brief update on the fix that was pushed out - we removed the offending code from the logged in web pages. We will continue to investigate and provide updates as we have them.

Yev here -> re: fixing the issue - we removed the offending code from the logged in web pages. Rest assured that we have are taking this very seriously internally and we will continue to investigate and provide updates as we have them.

Yev from Backblaze here -> we’ve looked into and verified the issue and have pushed out a fix. We will continue to investigate and will provide updates as we have them.

Yev from Backblaze here -> That's really nice of you, glad we could work together!

Yev from Backblaze here -> yes we are!

Yev from Backblaze here -> typically not - we've built most of our systems to be keep data up and flowing during those maintenance windows - if we anticipate longer windows or are doing things that can impact performance we typically announce it on our blog and twitter!

Yev from Backblaze here -> That's great! Glad the quick-start makes it simple.

Yev from Backblaze here -> Yea, it's pretty great! They're a great tool and we're glad to be involved!

Hey thanks! All things considered we got the site back up after 4 hours which is pretty speedy considering how long these things CAN last!

Yev from Backblaze here -> we're back up now, slowly propagating (as is the way with DNS) - but we're on the upswing now.

I've heard that a lot in the last hour. We'll be looking at all of our options once we get the service restored but that's priority #1.

Yev from Backblaze here - it's been that kind of day.

Yev from Backblaze here -> working to resolve it but can only move as quickly as they do. Also trying to figure out why the sudden "nope" stick.

Yev from Backblaze here -> we try to diversify vendors whenever possible.

Yev here -> of course we read it! It's a data-rich article about data failure! And the kudos is mutual - loved the post! :D