How Much Bandwidth Does Backup Internet Need?

A backup internet connection doesn't necessarily need to match the speed of your primary line. What matters is how much bandwidth your business will use when that line goes down. Payment systems, phone calls, cloud applications, and other essential services all need capacity, but the backup may not have to carry everything your network normally handles.

Table of Contents

1. Why Backup Internet Doesn't Have to Match Your Primary Connection
2. Decide What Must Keep Running During an Outage
3. Essential Operations or Almost-Normal Business Activity?
4. Measure the Bandwidth Your Critical Systems Use
5. Why Average Bandwidth Doesn't Tell the Whole Story
6. How Different Applications Affect Backup Capacity
7. Why Upload Bandwidth Needs Its Own Calculation
8. Keep Unnecessary Traffic Off the Backup Connection
9. Sizing Backup Bandwidth for a 1 Gbps Office
10. Allow for Headroom, Cellular Performance, and Data Consumption
11. A Final Backup Bandwidth Planning Checklist

1. Why Backup Internet Doesn't Have to Match Your Primary Connection

A company paying for 1 Gbps fiber may assume it needs another 1 Gbps connection for backup. Both connections serve the same building, after all. If the fiber goes down, the second connection takes over.

But having 1 Gbps available doesn't mean the company uses that much bandwidth throughout the working day.

On a normal network, traffic comes from all sorts of places. Employees download documents, join meetings, open cloud applications, and browse websites. Computers install updates, security systems exchange data, and connected equipment communicates with remote platforms.

Not all of that activity carries the same importance.

Take a retail store with payment terminals, inventory software, office computers, and guest Wi-Fi. If its primary connection fails, the store still needs to process sales and access inventory information. Customers browsing through guest Wi-Fi can probably wait until the main service returns.

An office may have a similar choice. Keeping customer calls and order processing online may matter much more than allowing every employee to continue large downloads or video meetings.

This is where backup bandwidth planning begins. Instead of replacing the full capacity of the primary connection, the company looks at what the remaining connection will need to carry.

Of course, some businesses have less room to reduce activity. A contact center that depends on cloud-based calls may need nearly all its normal communications capacity. A company handling large customer files throughout the day might also require substantial bandwidth on backup.

There isn't a standard percentage that works for every business. A 1 Gbps primary circuit could be paired with a much smaller backup, or it could require another high-capacity connection.

The difference comes down to what the business expects to keep running.

2. Decide What Must Keep Running During an Outage

Before looking at internet speeds, it is worth having a conversation with the people who will be using the backup connection.

Ask what work needs to continue if the primary internet disappears for several hours.

The answers aren't always obvious from network traffic reports. A payment terminal might use very little data, but without it, a retailer may struggle to complete sales. A computer downloading a large software update could be using much more bandwidth while doing nothing that needs immediate attention.

A warehouse may be concerned about scanners and inventory systems. A medical office might need access to scheduling and patient-management applications. At a corporate office, customer support and order processing could be the priorities.

Those activities should determine which applications receive bandwidth first.

A simple way to organize the discussion is to divide network traffic into three groups.

The categories will look different from one company to another. Email may be something an office can temporarily live without, while another business relies on it to manage time-sensitive customer requests.

There is also a detail that tends to get missed when people make these lists: applications rarely operate entirely on their own.

A payment terminal may depend on authentication or cloud register services. Employees using a business platform may need access to other systems before they can complete their work.

If those supporting services are overlooked, the bandwidth estimate won't reflect the full workload.

It is easier to identify those dependencies while the primary connection is working than during an outage when employees are already having trouble accessing something important.

3. Essential Operations or Almost-Normal Business Activity?

Two offices can have similar primary internet connections and still need very different backup speeds.

One may be prepared to work with fewer online services for a while. Another may have customers waiting on calls and employees who cannot do their jobs without continuous cloud access.

The backup has to be sized for whichever situation applies.

Keeping essential operations running

Some businesses are prepared to work with fewer online services until their primary connection returns.

A retail store, for example, may keep its payment terminals and inventory system connected while temporarily closing guest Wi-Fi access. Employees can still complete sales, even if a few other online services aren't available.

This arrangement can work well when the store knows which applications depend on the internet and has already decided what to restrict.

An office might take a similar approach, preserving customer calls and essential cloud systems while asking employees to postpone large file transfers or switch meetings to audio.

That could make a smaller backup connection practical, provided the remaining applications have enough capacity.

Keeping most normal activity available

Other businesses cannot reduce their workload very much.

A customer-service operation with forty agents may need most of them taking calls throughout an outage. A business whose employees work continuously with large cloud-hosted files may have limited scope for cutting traffic.

Those companies will need to look at a much broader share of their normal network usage.

Even then, the backup doesn't automatically have to match the full primary circuit. A company with 1 Gbps fiber may discover that its busiest ordinary workday rarely pushes traffic anywhere close to that speed.

Outage duration is worth considering here as well.

An office might be comfortable restricting internet access for half an hour. If the interruption lasts an entire day, employees may need access to applications that weren't originally considered essential.

That possibility doesn't mean every backup must support full business activity. It means the company should decide in advance how long it can operate with restrictions and whether those restrictions are realistic.

4. Measure the Bandwidth Your Critical Systems Use

Once the business has agreed on what must remain available, the next step is to see how much bandwidth those applications use.

A surprising number of companies know the speed of their internet connection but have little idea what travels across it.

The firewall may show that the site used 180 Mbps at lunchtime. That sounds useful until someone asks how much came from the phone system, how much came from employee meetings, and how much came from downloads that could have waited.

The total doesn't provide enough information to size a backup connection.

Depending on the equipment, a business router or firewall may show traffic by device, application, interface, or network segment. Some monitoring systems also keep historical records, which can be useful when looking at regular busy periods.

At a small office, it may be possible to identify the most important devices and examine their usage directly. At a larger location, separating traffic into network groups or using application monitoring can provide a better picture.

There is no need to account for every packet. Start with the applications the company cannot operate without.

Watch what happens when those systems are busy. An order-processing platform might generate relatively little traffic during ordinary use but much more when employees produce reports or transfer records. A warehouse may see a predictable increase around inventory processing.

These variations matter because a short measurement taken during a quiet period may produce a much lower estimate than the site really needs.

Where historical information isn't available, application providers may offer bandwidth requirements that can be used as an initial guide. Those figures still need some judgment. A cloud platform used by five employees for occasional data entry will behave differently from the same platform used continuously by fifty people.

If the existing equipment can distinguish upstream and downstream traffic, collect those figures separately. We'll return to why that matters shortly.

The immediate goal is to replace assumptions with a reasonable picture of what the essential workload looks like on a normal working day.

5. Why Average Bandwidth Doesn't Tell the Whole Story

Imagine an office where the important applications use an average of 25 Mbps.

A 30 Mbps backup might look sufficient on paper. There is room above the average, and the company isn't expecting the backup to carry every application.

The problem appears when several things happen together.

Employees may begin customer calls while a cloud application transfers reports. Another system might synchronize information at the same time. Each application could be operating normally, but their combined traffic can push demand well above 25 Mbps.

The average conceals those periods.

Even monitoring software can miss short increases if it displays traffic in five-minute or fifteen-minute intervals. A brief period of heavy activity may barely change the average shown on the graph.

This doesn't mean the company should choose its backup capacity based on the largest spike ever recorded. If the spike came from a file transfer that can be postponed, it may have little relevance to the backup plan.

What matters is whether the traffic came from work that must continue.

Look at how many people are active at once

The number of employees is often used as a rough way to estimate bandwidth, but it can be misleading.

Consider two offices with forty people each.

At the first location, most employees work with browser-based records and administrative software. They enter information, review documents, and occasionally download reports.

At the second, employees spend much of the day in video meetings and exchange large files with customers.

The second office may need considerably more bandwidth even though both have the same number of people.

Connected equipment creates similar differences. A building with dozens of sensors might generate very little traffic, while three or four cameras uploading continuous video can account for a much larger share.

Rather than assigning a fixed allowance per person or device, look at how the activity overlaps during the busiest relevant periods.

Scheduled processes can sometimes be adjusted as well. If several systems synchronize data every morning, moving one of those processes to another time may reduce peak demand without affecting the business.

6. How Different Applications Affect Backup Capacity

Application bandwidth figures are useful, but they need context. A phone system, a cloud platform, and a camera installation can all behave differently depending on how they're configured.

Here are the areas worth examining when those systems will remain active on backup internet.

Payment systems and POS terminals

Individual payment transactions generally don't move large amounts of data. A modern POS setup, however, may also use cloud registers, authentication services, inventory platforms, and reporting tools.

Those supporting systems need to be included when determining how much bandwidth checkout operations require.

A small retail store may still have a modest overall requirement, while a larger location with additional connected services may need more.

VoIP and business phone systems

With VoIP, the number of simultaneous calls matters more than the number of extensions.

An office with thirty extensions might have eight active calls during a busy period. A contact center with thirty agents could have nearly everyone on the phone at once.

The bandwidth requirement will be different.

Codec selection and packet overhead also affect traffic, so the phone system's actual technical specifications should be used rather than a single generic figure for every call.

Cloud business applications

Cloud applications are less predictable because employees can use the same platform in different ways.

Opening customer records or entering information may generate little traffic. Exporting a large report, downloading attachments, or synchronizing documents can increase demand considerably.

The distinction is useful when deciding which activities need to continue. Employees may require access to records without needing to run large exports during the outage.

Video meetings and collaboration

Video meetings consume bandwidth throughout the call, and multiple meetings can create a substantial combined workload.

Camera quality, screen sharing, and platform settings all influence the amount of traffic.

If a company can continue meetings using audio only, it may be able to reduce bandwidth use without interrupting the conversation. That won't work for every meeting, but it can be a practical restriction for an office operating on a smaller connection.

Remote access and VPN connections

Remote access could mean an administrator opening a device-management page or several employees transferring files through a VPN.

Those activities need very different amounts of bandwidth.

There is also the router to consider. Some equipment can handle ordinary internet traffic at much higher speeds than it can process encrypted VPN traffic. The backup may have sufficient internet capacity while the router becomes the limiting factor.

Cameras and monitoring systems

Camera traffic depends heavily on where recordings go.

A system storing footage locally and uploading occasional events might need relatively little internet bandwidth. A group of cameras continuously sending video to a cloud service can use much more, particularly upstream.

Check which recordings or remote feeds really need to continue during an outage before including the entire camera workload in the estimate.

These aren't fixed bandwidth allowances. They're the details that determine how much capacity each application may require at a particular site.

7. Why Upload Bandwidth Needs Its Own Calculation

Businesses often start comparing internet connections by looking at download speed.

That can cause trouble when the backup connection has much less upload capacity than the primary line.

A fiber service may provide similar speeds in both directions. With LTE/5G, upload and download performance can be quite different, and neither speed is necessarily constant throughout the day.

Consider a location where essential applications need 35 Mbps of download capacity and 18 Mbps upload during the busiest periods.

A backup that consistently delivers 60 Mbps download but only 10 Mbps upload is not sufficient. The download figure looks comfortable, but upstream traffic would already exceed what the connection can carry.

This is easy to overlook when network dashboards mainly show downloads or combined traffic.

An office may have modest download demand while employees are on cloud calls, accessing remote systems, or uploading documents. A monitoring installation could also be sending video to an external service throughout the day.

The business needs to know which direction carries the heavier workload.

It may be possible to reduce upstream demand without changing how essential systems operate. Some cameras can store more footage locally or send lower-quality streams during an outage. Certain background uploads can wait.

The important thing is to make that decision based on how the applications are used, not on an assumption that upload requirements will always be small.

Before selecting a backup, calculate the two directions separately. A connection needs enough usable capacity for both.

8. Keep Unnecessary Traffic Off the Backup Connection

A smaller backup connection can work perfectly well for the applications it was selected to support. Problems begin when the rest of the network continues using it as though nothing has changed.

Imagine an office where the essential workload has been measured at around 40 Mbps.

The company installs a backup connection with enough capacity for that traffic. But when it becomes active, employee computers continue downloading updates, cloud storage applications synchronize files, and guest devices remain connected.

The backup is now carrying far more than the original calculation allowed for.

Business routers and firewalls may support rules that apply when traffic moves onto a particular WAN connection. Depending on the equipment, those rules can limit downloads, restrict guest networks, or give important applications priority over less urgent traffic.

A company might preserve bandwidth for customer calls and transactions while temporarily reducing software updates and large file transfers.

These restrictions can make a smaller backup connection workable. But there is a limit to what traffic rules can accomplish. If payment systems, calls, and other essential applications already need more bandwidth than the connection provides, restricting guest Wi-Fi won't solve the problem.

The rules should reflect how the company has chosen to operate during an outage.

An office maintaining only essential services can use fairly strict restrictions. One that expects employees to continue most normal activity will have to allow more traffic and provide enough capacity for it.

The main thing is to make sure the traffic allowed onto the backup matches what the connection was sized to handle.

9. Sizing Backup Bandwidth for a 1 Gbps Office

A sixty-person office has a 1 Gbps fiber connection. Most of the day, employees use it for calls, cloud applications, file transfers, and video meetings. The office also runs order-processing software and several systems that need remote access.

The company is looking at LTE/5G backup. If the fiber fails, customer calls and order processing need to continue. Employees working with customers will still need their cloud applications, but software downloads and scheduled backups can wait. Video meetings can run without cameras for a while.

The firewall's traffic history gives the network team a place to start. After separating the essential applications from the rest, the estimated download traffic during a busy period looks like this:

These are example figures, not recommended speeds for the applications listed. They represent traffic occurring at the same time, rather than each application's theoretical maximum.

How much spare capacity should be included?

The 30 Mbps estimate leaves no allowance for traffic rising above the measured level. For this example, the team uses an additional 30%. It's a planning assumption, not a standard requirement.

30 Mbps × 1.30 = 39 Mbps

That puts the initial download target at 39 Mbps. A backup that can consistently deliver around 50 Mbps could be worth considering.

Upload may change the answer

The traffic records also show 12 Mbps of upload demand during busy periods. Using the same provisional allowance:

12 Mbps × 1.30 = 15.6 Mbps

Now the company needs a connection that can sustain the required throughput in both directions. A service delivering 50 Mbps down but only 10 Mbps up won't cover the measured workload.

The router's VPN and security throughput also need checking. Its internet interface might support the required speed while its encrypted traffic capacity is lower.

What if everyone needs normal access?

The numbers above assume employees can postpone certain activities. If the company wants all sixty people to continue video meetings, large file transfers, and their usual cloud work, that 30 Mbps estimate is no longer useful.

The network team would have to include those applications in a new measurement. The resulting backup requirement could be several times higher, even though the primary connection and employee count haven't changed.

10. Allow for Headroom, Cellular Performance, and Data Consumption

The bandwidth measured at an office is only one side of the calculation. The other is what the backup connection can consistently deliver.

This matters with LTE/5G, where available throughput can change during the day. A speed test might show excellent results in the morning and noticeably lower speeds when the surrounding cellular network becomes busy. Equipment placement and radio conditions can make a difference as well.

For capacity planning, the highest speed recorded during a test is not necessarily the most useful number.

A backup that occasionally reaches 150 Mbps could still be unsuitable for applications requiring 100 Mbps continuously if its throughput regularly falls below that level.

It is better to look at the speeds the connection can sustain under conditions typical of the location, including the busier periods when the business may need it.

The router matters too. VPN encryption, security inspection, and other features may reduce the amount of traffic some equipment can process. That limitation should be checked separately from the available internet speed.

The requirements won't stay the same forever

A site that needs 40 Mbps today may need more next year.

Perhaps the company adds a cloud application, introduces new monitoring equipment, or has more employees working with online systems. Even changes in application configuration can alter traffic volumes.

For businesses with many locations, creating a few standard backup-capacity profiles can make this easier to manage.

A small retail store may fit one profile, while a larger branch or office requires another. The profiles can be adjusted for sites with unusual requirements rather than giving every location the same allowance.

Cellular performance will still differ from one site to another. Two branches using the same equipment and connectivity plan may not have identical available throughput.

Bandwidth and data allowances are different things

There is another consideration when backup internet runs over a metered cellular plan.

Bandwidth describes how quickly data can move. Data consumption describes how much data moves over time.

A connection may provide enough bandwidth for the applications but still use a substantial amount of data during a long outage.

For example, an average traffic rate of 10 Mbps sustained continuously for eight hours would transfer approximately 36 GB of data.

That doesn't mean every business using a 10 Mbps connection will consume 36 GB over eight hours. Actual consumption depends on how applications and connected devices behave. Some communicate only occasionally, while others generate more traffic than expected through background updates, synchronization, or repeated data exchanges.

It shows why capacity and data allowance need separate calculations.

A company may need only modest bandwidth for its critical applications but a relatively large data allowance if those systems exchange information around the clock.

This becomes particularly relevant for businesses with multiple locations or those expecting cellular backup to carry traffic for extended periods.

11. A Final Backup Bandwidth Planning Checklist

Before selecting backup internet, the business should be able to answer a few practical questions.

• Which applications and services must remain connected when the primary internet is unavailable?
• Will employees continue most normal work, or will some activity be restricted?
• How much traffic do those applications generate during the busiest relevant periods?
• What are the download and upload requirements?
• Which downloads, updates, or background processes can wait until the primary connection returns?
• Can the proposed backup and its router sustain the required throughput under normal site conditions?
• If the backup is cellular, will the data allowance cover the likely duration and volume of traffic?

These answers won't produce a perfect prediction of every situation. They should, however, provide a reasonable basis for comparing backup options and identifying where more measurements are needed.

Once a connection has been selected, its capacity should be checked against the intended workload. The estimate is also worth revisiting when new applications, devices, or operating requirements are introduced.

A backup that worked comfortably when a branch first opened may not have the same spare capacity after several years of changes.