Copies of your site between nodes no longer count toward your usage
TL;DR: When a node copies a site's package from another node, those bytes no longer count toward the customer's usage or the serving operator's deliveries. Only what visitors receive counts, and nodes now prove a copy with a signed ticket.
To serve your site, an operator node first takes a copy of its package, often from another node that already holds it. Until now, the bytes of that copy counted as if a visitor had received them. A large site placed on several nodes could show gigabytes of usage on its deploy day from copying alone. From 10 November, copies between nodes no longer count. Only what visitors receive does.
What changes
- Site owners: copies between nodes no longer add to your usage. The Usage tab and Insights count only what visitors receive: copies aren’t in your bandwidth, requests, cache, error or latency figures, or in your project’s or site’s.
- Operators: you’re no longer credited for copies your node serves to other nodes. What you deliver to visitors is credited exactly as before.
- Copies need a ticket. From v0.0.133, a node asks the control plane for a ticket signed for that site before copying it, and the node serving the copy checks it. A request counts as a copy only with a valid ticket. A request that merely claims to be a copy is counted as an ordinary delivery.
Limits
- Figures already recorded aren’t recalculated. Days before 10 November keep the copies they counted.
- Nodes older than v0.0.133 still treat any request that claims to be a copy as one, until a minimum node version is required.
- If a node can’t get a ticket, the copy still goes ahead, but it’s counted as a delivery.
There’s no billing and there are no payouts during the open beta. This decides what counts for when they begin.
What you need to do
- Site owners: nothing.
- Operators: update your node to v0.0.133 or later.