atYevP

Yev from Backblaze here -> Do you have a ticket number I can reference and ask about?

Yev from Backblaze here -> That sounds very strange. I've asked our ops team and they said if you can provide the serial number of the drive you have we can track it. Would you be able to write in a support ticket w/ the serial number of the drive you bought so I can personally flag it and investigate? Once done you can write the ticket # here and I'll follow up with the team -> https://help.backblaze.com/hc/en-us/requests/new.

Yev from Backblaze here -> It's quite a feat!

Good times...

/stares wistfully off into the distance

Yev from Backblaze here -> I'll forward that to our drive stats team to consider!

Yev from Backblaze here -> we LOVE this series (and so do a lot of folks in the industry) - Drive Stats Guru Emeritus Andy did retire, but we have a new team that's adding some interesting observations and data breakdowns into the mix.

Could you give me that ticket number so I can chase it down with legal?

Yev here from Backblaze - we'd be happy to chase that down if you're willing to reach out to support so they can take a look: https://help.backblaze.com/hc/en-us/requests/new

Basically yes, so they are a bit slow to send. We reset quite a few passwords so the system is overloaded a bit. More details from our CISO on our subreddit: https://www.reddit.com/r/backblaze/comments/1j67bte/comment/....

Yev from Backblaze here -> Interestingly we thought about this kind of thing. That's partially why we left the link "naked" instead of hyperlinking text and added alternative instructions underneath it for the password reset to give security-minded folks a way to take the action without clicking anything.

Kudos to you for thinking about this stuff!

Understood, thank you for the context. One of the items we're working on right now is revamping the web console which does need some TLC as you've mentioned. If you'd like me to re-up the ticket, I'm happy to give support the heads up if you're still in need - and I've let our product team know about the issue you had with the UX.

Yev from Backblaze here -> I'm sorry to hear that was the case and that you were affected by the fires in LA. It's true that Groups may not be required depending on what you were trying to do, but I'm saddened to hear that your experience with support was less than ideal. If you can send me your ticket number, I can have support management review the ticket.

Love that! I think I re-shared your tweet about it a few days ago! I've been kinda staring at it on a loop on my monitor, fun to watch the balls bouncing around :D

Yev from Backblaze here -> Y'all this is one of our favorite things and I've spread it internally. So cool <3

Yev from Backblaze here -> you're welcome! Glad you like and we also wish they did! That's one of the reasons we started doing it, we wanted to know :D

Yev from Backblaze here -> When we started this, we did so with the intent of sharing data and hoping that others would do the same. We see glimmers of that here and there but it's still so fun for us to do and we're expanding on it with Networking Stats and some additional content that's going to be coming soon including how these inform our infrastructure deployment. Fun stuff :)

Yev from Backblaze here -> thank you so much!

Yev here -> That's what I said!!! Great minds :P

Yev here -> we're actively looking into it, we can upload files >1TB so it's a bit tough to chase down.

Yev here from Backblaze -> This is something that our engineering team is taking a look at. We've been able to successfully upload files over 1TB internally, so we're trying to chase down what's triggering those error messages. From what I can gather the client should certainly upload files over 1TB, but something wonky is going on this case. We're looking at it though!

Lets go!

Lets goooooooo

Yev here - I confirmed that that's definitely a PATH towards not hitting those limits, but no reason to pay for 20TB if you're not using that much (especially if you're not using a reseller). I'm working with the team to change some of that messaging. The TL/DR is that most people will NOT see a change (we did a lot of analysis on the back end to see whether the throttling of <10TB customers would affect their behavior and most won't see a thing). This has been in production since Wednesday, so if you're not seeing any changes, your use-case is likely unaffected.

Yev here -> if you have a ticket number I'd love to know it b/c that's not accurate and I want to make sure support is trained properly. If you're using more than 10TB of storage you'll experience no change. We've updated our blog post w/ more explicit information (apologies for confusion on this one).

Yev from Backblaze here -> we've updated the post to make it more clear. This will ONLY affect about 5% of the Backblaze B2 Cloud Storage population with < 10TB of data. See below for additional information:

-> This policy is limited to Backblaze B2 Cloud Storage usage. Backblaze Computer Backup usage is not within the scope of this policy.

-> Customers storing 10TB or below will initially be provisioned for uploads up to 3,000 requests per minute and 800 megabits per second, and for downloads up to 1,200 requests per minute and 200 megabits per second, all per account. Other API operations may also be limited to keep traffic flowing, but again, this won’t be noticeable to most customers.

-> Customers storing more than 10TB, including all sales assisted customers whom we’ve supported during implementation and/or renewal, will experience no change at this time.

-> Traffic analysis and engineering is a dynamic activity, so we’ll likely revise limits over time in response to evolving usage patterns, improvements we roll out, and, of course, customer feedback. We will announce significant changes here on the blog.

Hope that clears things up and we have additional documentation on our API Documentation pages: https://www.backblaze.com/apidocs.

Yev here -> Ask in the blog comments and we can try to get some smarter eyes on than mine on it!

Yev from Backblaze here -> I LOVED the OKCupid data dumps, they were so fascinating! Pornhub used to do a great job of surfacing their data as well, but obviously the subject matter was much different.

Yev from Backblaze here -> we welcome the challenge!

Yev from Backblaze here -> Mwahaha :D I was going to post a link but you found it :)

Yev from Backblaze here -> I'm heading up the Computer Backup product, what would you like to see changed or updated? I can make sure to send it to the product team! Or you can fill out our product suggestion portal -> https://www.backblaze.com/product-portal.