How to Reduce Your Lumen IoD Bill by 30–40% with Bandwidth Scheduling

*Updated July 2026 with a per-tier rate reference, a spend-benchmarking framework, how scheduling compares to the alternatives, and an MSP fleet workflow.*

The Problem with Always-On IoD Pricing

Internet-on-Demand (IoD) is billed by the hour at whatever bandwidth tier your circuit is currently ordered at. If you provision a 1 Gbps circuit and never change it, you pay the 1 Gbps hourly rate 24 hours a day, 7 days a week — including nights, weekends, and holidays when utilization is often below 10%.

This is the core inefficiency that bandwidth scheduling solves.

How IoD Hourly Billing Works

Every hour, your IoD provider records your current ordered bandwidth tier and bills accordingly. The billing is based on what you ordered, not what you used. A circuit sitting at 1 Gbps overnight costs the same as one running at full capacity during peak hours.

IoD tiers typically range from 1 Mbps to 100 Gbps. The price difference between a 100 Mbps tier and a 1 Gbps tier can be substantial — and scheduling your circuit to drop to the lower tier during off-peak hours can eliminate a significant portion of your monthly bill.

A Real-World Example

Consider a circuit that runs at 1 Gbps during business hours (8am–6pm, Monday–Friday) but only needs 100 Mbps overnight and on weekends.

• • Business hours: 50 hours/week × ~52 weeks = ~2,600 hours/year at 1 Gbps
• • Off-peak: ~6,160 hours/year at 1 Gbps (current) vs 100 Mbps (scheduled)

If the hourly rate difference between 1 Gbps and 100 Mbps is even $0.50/hour, that’s $3,080 in annual savings from a single circuit — for software that costs $600/year.

The Right Way to Schedule IoD Changes

Manual scheduling through the provider portal is error-prone and time-consuming. Each change requires logging in, navigating to the circuit, submitting an order, and waiting for confirmation. For recurring changes — every weeknight, every weekend — this is unsustainable.

Automated scheduling through the NaaS API handles this programmatically. You define the schedule once: “Drop to 100 Mbps at 6pm weekdays, return to 1 Gbps at 7:45am.” The system submits the API order at the right time, every time.

What to Schedule First

Start with the highest-bandwidth circuits that have predictable off-peak windows:

1. Overnight windows — Most enterprise circuits can drop 70–90% overnight with zero business impact. 2. Weekends — Saturday and Sunday are often the biggest savings opportunity for B2B workloads. 3. Holiday windows — Schedule reduced tiers for known low-traffic periods.

Per-Tier Rate Reference

The savings depend entirely on the gap between your peak tier and your off-peak tier. Lumen IoD publishes an hourly rate for each of its bandwidth tiers, and those rates vary by market (metro area) and contract term, so treat the numbers below as public reference points rather than a quote for your specific circuit:

The pattern that matters: the jump from 1 Gbps down to 100 Mbps saves roughly $0.60/hr, and the jump from 1 Gbps down to a 1 Mbps backup tier saves nearly a full dollar per hour. Multiply that gap by the number of genuinely idle hours in your month and you have your ceiling. For your circuit's exact published rates, check the Lumen Marketplace portal or the Apptifi pricing calculator, which reflects NaaS pricing across all tiers and adds the separate UNI port cost so your total-contract-value estimate is complete. [UNCERTAIN: these are publicly-referenced rates that vary by market and term; they are not a substitute for your circuit's quoted pricing.]

Benchmarking Your IoD Spend: Where Does Your Bill Sit?

Before you schedule anything, it helps to know whether your bill is already lean or full of slack. A quick self-benchmark:

1. Divide your monthly IoD charge by 720 to get your blended hourly rate. Compare it to the published rate for the tier you *think* you are running. If your blended rate is close to the full peak-tier rate, you are running flat-out around the clock and have the most to gain. 2. Estimate your true duty cycle. For most B2B workloads, only 30–45% of the hours in a month carry meaningful traffic. If you are paying peak rates for 100% of hours but using the circuit for 40% of them, roughly 55–60% of your bandwidth spend is recoverable. 3. Weight it by circuit size. A 100 Mbps circuit left always-on wastes tens of dollars a month; a 1 Gbps or 10 Gbps circuit left always-on wastes hundreds to thousands. Rank your circuits by peak tier and start at the top.

The point of benchmarking is to set a realistic target. A single circuit with clean nights and weekends can land in the 30–40% reduction range. A circuit that already runs lean, or one that legitimately needs high bandwidth around the clock, will save less — and scheduling honestly won't manufacture savings that the duty cycle doesn't support.

Scheduling vs. the Alternatives

Bandwidth scheduling is not the only lever for a high IoD bill, but it is usually the fastest and the lowest-risk. The alternatives:

Permanently downgrading the tier. Simple, but it caps your peak capacity. If you drop a 1 Gbps circuit to 100 Mbps to save money, you also lose the headroom on Tuesday at 10am. Scheduling keeps full peak capacity when you need it and only trims the idle hours.

Renegotiating or moving to committed/DIA bandwidth. A fixed Dedicated Internet Access contract can be cheaper per megabit *if* your utilization is steady and high. The whole point of IoD, though, is elasticity — if your traffic is spiky or seasonal, a flat committed rate often costs more than a well-scheduled IoD circuit, and you give up the minute-by-minute flexibility. Benchmark both before switching.

Manual tier changes through the portal. Free, but it only works if someone remembers to do it every night and every Friday. In practice, manual changes capture a fraction of the available savings and reintroduce the risk of leaving a circuit stranded at a high tier. Automation is what makes the savings durable.

Scheduling wins when your traffic is predictable and your off-peak windows are real. That describes most enterprise and MSP-managed IoD circuits.

Reducing IoD Bills Across a Fleet

The math above is per-circuit. Across a fleet — an MSP running IoD for dozens of clients, or an enterprise with sites in many metros — the same lever compounds, but the operational problem changes. You need per-circuit schedules, per-customer reporting so each tenant can see its own savings, and an audit trail of every tier change. Doing that by hand across 50 circuits is not realistic.

For the fleet-scale workflow — tenant isolation, aggregated savings reporting, and bulk schedule templates — see the [MSP Guide to Lumen IoD Management at Scale](/blog/msp-guide-lumen-iod-management). For a side-by-side of the tools that automate this, see [Lumen IoD Schedulers Compared](/blog/lumen-iod-schedulers-compared-2026).

Calculating Your Savings

Use the savings calculator on the Apptifi homepage to estimate your monthly and annual savings based on your current IoD spend and peak hours per day. Most customers see 30–40% bill reduction within the first billing cycle.

For a per-tier breakdown of Lumen IoD hourly rates and how the math actually pencils out, see [Lumen IoD Pricing: How Hourly Bandwidth Billing Works](/blog/lumen-iod-pricing-per-hour). If you also run Layer 2 EVCs, the same scheduling lever cuts [Lumen Ethernet on Demand](/features/ethernet-on-demand) costs by 30–50%.

The Apptifi Core plan starts at $50/month — for most circuits, the first month’s savings exceed the annual subscription cost.