^, assumably per object

Yeah but if I have like a 4Gb file is that still just one read?

If so that's amazing.

i would think so, guess we will find out soon

Edit: This logic is wrong because it assumes that every request is a read operation, R2 responses can be cached and these responses are free. R2 egress for objects larger than ~144KB is unbeatable, for smaller files the price shift toward requests makes it unreasonable because it's cheaper to pay per egress than requests, is there any plan to charge competitively per bandwidth? Bunny (~$5/TB) vs. R2 ($0.36/M) (1000/0.005)/(1000000/0.36) ≈ 72 KB G-Core/AH (~$2.5/TB) vs. R2 ($0.36/M) (1000/0.0025)/(1000000/0.36) ≈ 144 KB

Yeah, I'd assume. Though many S3-compatible providers charge based on egress rather than operations. The only one I can think of that charges for operations is Backblaze. They count a GET as a single operation no matter the object size.

i don't think it's comparing itself to bunny or g-core

I would assume that's why KV is still around.

anyone else getting this?

oop scrolling up i see yes

yea, access isn't out yet

ill make an assumption that we got added to the dashboard flag but not the api

yup

apparently

whooo

no api access yet, afaik

thats what greg is solving

Correct - per request regardless of size. That's what no egress is all about

Cool 👀

👀

One more question; are those free tier numbers per month or all time?

The GB looks like it's per month but the other ones aren't labelled as "month"

please let it be per month

I think generally all free usage is in "per month" units but I'll double-check. Could just be a UI bug

🤯

Amazing.

My bad. I misunderstood the question. It's 10GB total for the account

i think it was about the operations