We rebuilt the status page around real measurements from each zone: response time and free space, read live when you open it. Everything older than today is marked as archive. It is a small honesty we wanted: the number you see is the number the zone just reported, not a decoration.
The oldest file still in Frankfurt was uploaded on 11 May 2021. We downloaded it this week and its SHA-256 is exactly what it was five years ago. That is the entire promise of the product in one sentence, so we are allowed one sentimental post about it.
We get asked for a customer count for the website. We will not put one up. Not because it is embarrassing, but because the moment you publish a round number you start optimising for it, and we would rather optimise for files that come back the same as they went in. The only numbers on the site are the real limits and the live measurements on the status page.
One of us spent two days at a small infrastructure meetup. The useful takeaway was not a talk but a hallway conversation about how other small teams handle disk-full: most refuse writes well before the disk is actually full, with a wide margin, because the failure modes near a full disk are nasty. We already refuse below 3 GB free; the conversation made us comfortable keeping that margin generous.
We rotated the internal signing keys across every zone this week. Nothing you can see changed, which is the point. Writing it down because a real service does this quietly on a schedule, and because next time we will have this note to remind ourselves of the order of operations.
When you export an account you get the files and a manifest.csv. The manifest is there for one reason: so you can prove, a year later, what you took out. Name, size, SHA-256, content type, date. Hash the files you kept, line them up against the manifest, and you know nothing rotted in the meantime. It costs us a few kilobytes and saves you an argument.
People keep asking for device sync, and we keep saying no. Here is the honest reason: sync is a different product, with its own failure modes, conflict handling and a desktop agent to maintain. We are four people. A storage box you upload to and download from is a thing we can keep correct. A sync engine is not, yet. So the answer stays no, and we would rather tell you that than ship a half one.
From today each stored file gets a SHA-256, shown on the file card. A customer last month sent us a zip that arrived two bytes short somewhere between their laptop and us. We could not prove where it broke. Now you can: download, run sha256sum, compare. If the strings match, the bytes are intact. It is a small thing that saves an awkward email.