Lumen IoD bandwidth scheduling best practices

The short answer: A Lumen IoD bandwidth schedule works when it is sized from a full billing cycle of utilization, restores capacity before people arrive, and plans for the days that break the pattern. The carrier caps changes at 24 per circuit in a rolling 24 hours, and a business-hours schedule uses two a day.

Lumen Internet On-Demand is now sold as Lumen Intelligent Internet. The ten practices below are the ones that keep a schedule switched on. Vigilis Flux schedules bandwidth on Lumen Internet On-Demand and Lumen Intelligent Internet, and each practice notes how it handles it.

1. Size the window from a full billing cycle

One typical week hides the hours that matter most. Use a full billing cycle of utilization so month-end processing and reporting runs are visible. Look at the peak inside the proposed quiet window, not the average across it.

2. Set the low tier to carry the quiet-hours peak

The low tier is not zero. Backup and replication jobs often run exactly when a site looks idle. Remote users, on-call staff, and other teams’ scheduled work need capacity too. Pick a low tier that carries the largest of those.

3. Restore capacity before the site opens

The change has to land before demand does. Lumen says bandwidth changes take effect in minutes. Schedule the morning change ahead of the first arrivals, not at opening time.

4. Write the exceptions down first

Every site has periods when its normal window is wrong.

Recurring days. A venue or a place of worship is busiest on the day a weekday schedule would have lowered it.
Fixed events. A migration, a broadcast, a sale, a game day.
Seasons. Retail peaks, academic terms, reporting cycles.
Unplanned demand. Someone needs capacity now.

For each one, the schedule has to hold or raise capacity for a set window and then return to the normal pattern. In Vigilis Flux, a one-time scheduled change raises capacity for the window and the weekly schedule resumes afterward.

5. Keep a manual override that returns to the schedule

When someone needs full speed off-hours, they need a way to get it from the same dashboard, and the schedule should resume afterward rather than stay off. A schedule that has to be disabled to handle one busy night tends to stay disabled.

6. Respect the change limit

The carrier caps bandwidth changes at 24 per circuit in a rolling 24 hours. A business-hours schedule uses two a day, so it is nowhere near the cap. Automatic scaling can reach it. Any automation needs cooldowns between changes and a guard against bouncing between tiers. In Vigilis Flux, Auto stays inside the cap.

7. One owner per connection, per hour

A fixed schedule and automatic scaling should not both drive the same connection at the same time. Each will move the speed a different way. Pick one: a fixed schedule, or a schedule that hands the business-hours side to Auto and holds a fixed speed after hours.

8. Use Auto where the pattern is not known, and dry-run it

Some sites do not follow the clock. For those, scale on measured utilization instead. In Vigilis Flux, Auto by default raises bandwidth when utilization stays above 80% and lowers it when it stays below 20%, with cooldowns and a guard against bouncing between tiers. A dry run shows what it would have done before you switch it on.

9. Know the floor on a term connection

A term-priced Lumen Intelligent Internet connection can flex above its committed bandwidth and come back to it, not below it. On a term, schedule the peaks, not the nights: hold the connection at its floor, raise it for the peak, and return it when the peak passes. Hourly connections can move between any supported tiers.

10. Model first, then check the bill

Model the schedule against the rate tiers before the first production change. After the first full cycle, compare the bill with the model and adjust. The Bandwidth Savings Calculator models a schedule, and its Auto tab models demand-based scaling from a utilization report exported from the carrier portal.

How Vigilis Flux applies these

Vigilis Flux is the Bandwidth on Demand product from Vigilis. It gives each site its own schedule or Auto settings, all managed from one dashboard, with exceptions for known peaks and projects, an override at any time, and a record of every change. It is a $15 per service, per month add-on to any Vigilis plan, and the price covers both modes.

How to reduce a Lumen Internet On-Demand bill
Lumen Internet On-Demand pricing per hour
Automating Lumen bandwidth changes through the NaaS API
Lumen bandwidth schedulers compared
WAN bandwidth management, for the exception model in more depth
Bandwidth schedules and Auto-Flux in the Vigilis Help Center, for the settings behind these practices

Primary sources

Common questions

What is the best way to schedule Lumen IoD (Lumen Internet On-Demand) bandwidth?

Size each site's operating window from a full billing cycle of utilization, set the low tier to carry the peak inside the quiet window, restore capacity before the site opens, and write the exceptions down before you start. Vigilis Flux schedules bandwidth on Lumen Internet On-Demand and Lumen Intelligent Internet this way, with per-site schedules, exceptions, and a record of every change.

How many times a day can Lumen bandwidth be changed?

Plan for a limit. The carrier caps bandwidth changes at 24 per circuit in a rolling 24 hours. A simple business-hours schedule uses two a day. Automatic scaling can use many more, so it needs cooldowns and a guard that stops before the cap.

Should I use a fixed schedule or automatic scaling?

Use a schedule when you already know the pattern, such as an office with set hours. Use automatic scaling when demand does not follow the clock. Do not run both against the same connection at the same hours, because each will move the speed a different way. Vigilis Flux offers both modes, and a schedule can hand the business-hours side to Auto.

What is the most common reason a bandwidth schedule fails?

Exceptions. Most sites have at least one recurring period when the normal schedule is wrong, such as weekend services, seasonal peaks, or a planned migration. A schedule with no way to handle them gets switched off the first time it is wrong.

Can I schedule a term-priced Lumen Intelligent Internet connection?

Yes, down to its committed floor and not below it. Hold the connection at the floor, raise it for the peak, and return it to the floor when the peak passes. Hourly connections can move between any supported tiers.

Who makes Vigilis Flux?

Vigilis. Vigilis Flux is the Bandwidth on Demand product in the Vigilis telecom platform, operated by Socium IT LLC d/b/a Vigilis. It is a $15 per service, per month add-on to any Vigilis plan.