Aggregated Burstable 95th Billing
What it is
Aggregated Burstable 95th pools your ZEC EIPs into a single meter, then bills the monthly 95th-percentile of their combined bandwidth — the max of ingress and egress — minus a commitment floor that you always pay for regardless of usage.
Any ZEC EIP that picks this billing method joins the aggregation. There is no "same kind" or "same city" restriction at the billing level — the 95th is computed across all EIPs that opt into the method on your account.
Why aggregation is the whole point
If you have 100 EIPs and you bill each one's 95th percentile independently, you pay for 100 separate peaks. In practice, those peaks don't happen at the same minute — batch jobs, user traffic, cron timers, all out of phase. When you aggregate first and take the 95th of the sum, the combined peak is almost always much smaller than the sum of the individual peaks.
Aggregated Burstable 95th is designed for fleet-scale workloads. The statistical averaging only produces meaningful savings when you have a large number of EIPs with uncorrelated peaks — typically 50 or more. For smaller deployments, Flat Rate or Data Transfer are simpler and usually more cost-effective.
How billing works
At the end of the month:
The platform collects 5-minute Mbps samples from every EIP opted into this method, for both ingress and egress.
The samples are summed across EIPs (so you get one sample per 5-minute interval, not one per EIP).
For each interval, the max of ingress and egress is taken.
The aggregated samples are sorted, and the top 5% are discarded.
The highest remaining sample is the billable 95th.
You pay for the commitment floor (Mbps) regardless of what the billable 95th turned out to be. The overage — the amount by which the billable 95th exceeds the commitment — is billed on top at the overage rate.
Setting a higher commitment usually unlocks a lower per-Mbps price on the commitment line, so it pays off when you know your sustained level.
When this is the right choice
Large fleet (50+ EIPs). The aggregation discount only becomes meaningful at scale.
Uncorrelated peaks. If your EIPs peak at different times — user-facing workloads in different timezones, batch jobs on staggered cron schedules — the aggregated 95th will be a lot lower than the sum of individual ones.
You want one commitment line, not per-EIP pricing. Simpler than sizing each EIP separately.
When to reach for something else
Fewer than 50 EIPs. The statistical discount is small; Flat Rate or Data Transfer will be simpler and usually cheaper.
All EIPs peak at the same moment. Aggregation only helps when peaks are spread out. If everything is driven by one upstream event (say, a scheduled release), the aggregated peak is the sum of the individual peaks.
Relationship to Flat Rate and Data Transfer
Aggregated Burstable 95th replaces per-EIP public-network billing for every EIP that opts into it. You don't also get a per-EIP Flat Rate or Data Transfer line for those EIPs — the aggregated meter is the meter.
Last updated