Summary

  • Lumen Intelligent Internet lets an eligible business activate and resize dedicated internet through a portal or API, in some cases in as little as five minutes. The claim applies after an eligible Fabric Port or partner access path is ready, not from an arbitrary building address to newly installed fiber.
  • Hourly service is charged for the selected bandwidth, rounded up by the hour until disconnection. Term pricing creates a committed bandwidth floor for 12 to 60 months while allowing temporary increases above it.
  • The product’s market significance is the separation of a physical access layer from an elastic service layer. Buyers gain real operating control inside that envelope, while the port, contract, partner path and billing permissions still determine the limits of that control.

Five minutes is an attractive unit for buying a network. It resembles cloud compute: choose a capacity, press a control, and receive a usable service before a conventional order could reach a provisioning desk. Lumen’s 21 September launch of Intelligent Internet makes that experience credible for enterprise connectivity—but only after a less glamorous unit has already been bought, delivered and connected.

That unit is the Fabric Port. Lumen calls it the on-ramp to its Network-as-a-Service platform. Once the port is eligible and linked to the customer’s equipment, Lumen Connect or an API can activate internet service and change bandwidth in minutes. The physical port therefore does not disappear. It becomes the fixed substrate on which a faster market for logical capacity can operate.

The distinction changes how the offer should be valued. Intelligent Internet is not simply bandwidth rented by the hour, and it is not merely a conventional circuit with a better dashboard. It is a layered contract. The access path establishes where service can exist and how much capacity can ever pass. The selected internet service establishes what the customer pays for and can use at a given moment. Software shortens the second clock; it does not abolish the first.

The five-minute clock starts after readiness

Lumen says the service is available to enterprise customers at more than 10 million U.S. business locations and can scale to 100 Gbps. Its product material adds the boundary that matters: Intelligent Internet starts with a Fabric Port, and speed availability depends on the location, equipment and access type. An address checker distinguishes sites already enabled for self-service from sites that require sales assistance.

The readiness process is physical. Lumen’s port guidance asks for property-management access, the handoff type and the customer-equipment path. Fiber is recommended for higher speeds; a copper handoff cannot exceed 1 Gbps. An earlier port FAQ describes a technician visit and a typical three-to-five-business-day readiness window before the customer extends the connection to its own equipment. Those steps are not defects in the product. They are the work that makes the five-minute control truthful.

Colocation can move the boundary but not erase it. Lumen’s architecture guide shows access through Equinix Fabric, Digital Realty ServiceFabric and Flexential Cloud Fabric. In each case, the customer needs a presence and an active partner connection. The customer initiates a cross-connect or virtual connection, the partner provides access, and Lumen supplies the internet service above it. For off-net delivery, partner access capacity becomes the maximum scalable envelope.

This is why “10 million locations” is an addressable footprint, not proof that every site is already equipped, approved or capable of 100 Gbps. The commercial question is how many requested sites convert from address match to eligible port, how long readiness takes and how often the requested burst fits inside available access capacity.

Elasticity has a billing floor

Lumen offers two service clocks. Hourly pricing is the most cloud-like. The legal schedule says charges begin as soon as online activation notice is issued and continue for every consecutive hour, rounded up, until the customer disconnects the service. Billing follows the selected bandwidth, not measured traffic. A quiet 10 Gbps connection is therefore not priced as if it carried 100 Mbps.

The public starting rates are US$0.37 an hour for 50 Mbps, US$0.47 for 100 Mbps, US$1.06 for 1 Gbps and US$3.93 for 10 Gbps. Running those figures continuously for a 720-hour month yields simple arithmetic of US$266.40, US$338.40, US$763.20 and US$2,829.60. None is an all-in quote: taxes, fees, port and access charges, security add-ons, location eligibility and other terms remain outside the calculation.

Term pricing is a different bargain. The datasheet describes terms of 12 to 60 months and a fixed monthly rate for a committed bandwidth floor. A customer can scale above that floor when demand rises and return when the peak passes. Lumen’s support instructions make the asymmetry explicit: a monthly-billed connection may add bandwidth, then decrease only to its original contracted bandwidth.

The floor protects budget predictability for the buyer and base revenue for the operator. The burst layer monetizes spare capacity without forcing a permanent upgrade. That may reduce waste compared with provisioning every circuit for the largest imagined peak, but no public evidence yet quantifies utilization, savings, uptake, revenue or margin. The right claim is architectural, not financial: the purchase separates committed access from variable increments.

Control is real but bounded

The customer can change bandwidth, configuration and billing method through Lumen Connect. The architecture also exposes service-availability, quoting, ordering, order-status, diagnostics, billing, ticketing and maintenance APIs. This is meaningful operating control because the network team no longer has to route every change through a manual provider queue.

Yet the control plane does not grant an unlimited right to capacity. A request can take effect only when provisioning succeeds, the port supports it and the user has the necessary permissions. A physical ceiling remains. The customer also bears the consequence of an accidental activation until it disconnects or changes the service. API governance—identity, approval, spending limits, idempotency and an auditable change record—therefore becomes part of network-cost control.

Partner delivery creates another boundary. Lumen’s service schedule makes the customer responsible for separate contracts and permissions with the access provider. Lumen disclaims responsibility for the provider’s technical interoperation and may terminate the service if it loses the directed physical or logical connection. One portal may present a single operating surface, but it does not merge the underlying liabilities.

The same discipline applies to security. Intelligent Internet carries an availability commitment of up to 99.99%. DDoS Essentials and Defender can add network-level protection, but they are optional layers with their own scope. An SLA is a remedy framework, not proof that an outage cannot happen, and a security add-on does not transfer every customer-side responsibility to the carrier.

Evidence boundary

The launch date, footprint, named early users and service positioning come from Lumen’s announcement. Speeds, starting rates, SLA and eligibility qualifications are published on the product page and in the datasheet. Physical and partner boundaries come from the architecture guide, port-readiness guide and service schedule; the bandwidth-change instructions confirm the monthly floor. The floor-and-burst interpretation is editorial analysis; the named customer examples are issuer evidence, not independent performance audits.