Fill the Server: 80% off your first 4 monthly invoices, monthly billing. Ends Nov 30, 2026. 25 spots in this batch.FILL25
Fill the Server, annual: about 29.63% off your first annual invoice. Ends Nov 30, 2026.FILL25Y
Fill the Server, 2 year term: about 15.69% off your first biennial invoice. Ends Nov 30, 2026.FILL25B
Fill the Server, 3 year term: about 11.11% off your first triennial invoice. Ends Nov 30, 2026.FILL25T
80% off your first 3 months, monthly billing. Ends Dec 25, 2027.3MONTHS80
50% off your first annual Shared term. Ends Dec 31, 2027.50SHARED
Shared Starter, 3 year term: C$105.84 total.MOOSE294
20% off your first 3 monthly VPS invoices. Ends Dec 31, 2027.20VPS3
25% off your first annual base VPS term.25VPS

← All guides

Web hosting

Bandwidth capacity planning: size links from real traffic peaks and transfer windows

Published August 2026 · 2 min read · Updated 2026-09-05

Bandwidth capacity planning estimates sustained and peak transfer, but the useful metric depends on the service: web response bytes, backup windows, API traffic, software downloads, media, or replication. “Unlimited bandwidth” plan wording does not eliminate network interface, fair-use, CPU, origin, or user-latency constraints.

Measure bytes and peak rate separately

Monthly transfer answers billing/aggregate volume questions; Mbps/Gbps over short intervals answers whether links saturate during peaks. Record both inbound and outbound because backups/imports can differ from customer traffic.

Use percentiles and time-series measurements across representative periods.

Map traffic classes

Separate public web/CDN traffic, API responses, database replication, backups, package updates, uploads, mail, and administrative transfers. Large background transfers can be scheduled or rate-limited independently from latency-sensitive traffic.

Do not serve large media downloads from a web-hosting path without checking storage/CPU/cache architecture.

Estimate growth from actual payloads

Multiply page/API/download response sizes by observed request counts and account for cache/CDN hit rate when relevant. Compression, image optimization and caching can reduce origin bytes, but measure their actual effect on your workload.

For backups, use daily changed bytes and allowed backup window.

Plan headroom and monitoring

Alert on sustained interface utilization, packet drops/retransmissions, transfer-duration overruns, and abrupt usage changes. Upgrade network/service architecture when measured peaks approach the safe operating envelope.

  • Track transfer and peak rate.
  • Classify traffic types.
  • Model measured payloads/growth.
  • Reserve headroom for bursts.

Next step

Use sustained throughput, burst demand, backup or replication windows and protocol overhead to decide whether a network link has enough usable capacity.

Explore DotMoose web hosting

Keep reading

Related guides.

Backup capacity planning: estimate storage from change rate and retention

Model source size, daily change, compression, deduplication, retention and growth so backup storage is sized from the workload instead of one full-copy estimate.

Read the guide

Backup encryption basics: protect copies at rest and in transit

Choose where backup data is encrypted, how keys are stored and recovered, and how restore operators gain access without putting the only key beside the backup.

Read the guide

Backup recovery drills: prove the restore process before an outage

Run isolated recovery tests, measure restore time, verify application state and record missing dependencies so the backup plan is based on tested recovery.

Read the guide

More backups guides

We will handle the move. You check it first.

Your current site stays online until your new one is ready. You approve the copy first, and if anything is not right we switch you back right away. The price you pick is the price you renew at.

Start my free moveSee plans and prices
See pricesFree move