Burst capacity gives you extra bandwidth for migrations, backups, launches, and traffic spikes without over-provisioning year round. PacketFabric offers hourly and burstable billing for backbone virtual circuits. Provision an hourly circuit on its own, or configure hourly bursting above a monthly or longer term circuit, all from the portal or REST API.
Bill by the hour. Turn up a 10 Gbps EVPL for an hour, ready to use minutes after you click.
Burst above your term. Add hourly bandwidth on top of a monthly or longer term circuit when demand spikes.
Across the footprint. Backbone circuits run between your ports across hundreds of global PoPs.
Trusted by leading brands
When to Use Burst Capacity
Burst capacity fits any workload that spikes and then settles. You add the bandwidth for the event, not the calendar.
Cover a product launch, seasonal peak, or unexpected surge.
Move a large data migration or a backup window without paying for that bandwidth all year.
Feed an AI or model-training run that needs short bursts of high throughput.
Run a disaster recovery failover test at full capacity, then scale back.
How hourly burst capacity billing works
PacketFabric bills burst capacity by the hour, in full-hour increments. You have two ways to use it. Provision a standalone hourly circuit for a one-off job, ready minutes after you create it. Or set hourly bursting above a monthly or longer term circuit, so your baseline stays on a low unit price and you pay for extra bandwidth only when demand climbs. Either way, you match cost to use instead of buying peak capacity you seldom touch.
Common burst capacity questions
By the hour, on its own or on top of a term circuit.
Minutes from the time you create it in the portal or API.
Burst capacity is extra bandwidth you add on demand for a spike, then remove when it passes. PacketFabric delivers it as hourly, burstable backbone circuits you provision in minutes, so you do not pay for peak capacity year round.
Burstable billing charges for bandwidth by the hour, in full-hour increments. You pay for the hours you use rather than committing to the peak on a long-term contract.
For migrations, backup windows, product launches, seasonal traffic peaks, disaster recovery tests, and short high-throughput jobs like model training.
No. You can provision a standalone hourly circuit with no term, or burst above a longer-term circuit only when you need it.