The Workload Will Change. The Fiber Decisions Will Remain.

The architecture inside a data center can change several times over the life of the fiber beneath it. The provider you choose today can still be part of the campus several workload generations from now.

This article explores the importance of AI data center fiber infrastructure in powering the future of technology.

By Alexander Lee, Senior Account Director, Neocloud and Superscale, Lightpath

I’ve worked with data center and AI campus buyers for more than twenty-five years, and I’ve watched many of the same customers move through several generations of infrastructure.

One customer who contracted for colocation space early in my career started with a few cabinets, expanded into suites, adopted cloud on-ramps after that, and is now developing an AI campus.

Same customer. Four architectures.

The infrastructure inside the building kept changing. The consequences of the original fiber-planning decisions lasted much longer… and that was when data centers were in a city surrounded by existing fiber options.

Today, the data centers I am building fiber into are in the most remote areas where fiber infrastructure will take between 18-24 months to build.

Each architectural shift can feel transformational. Often, it is. But every new generation of workloads still depends on physical routes, conduit, fiber capacity, diversity, and connectivity decisions made years earlier.

AI Data Center Fiber Infrastructure Outlasts the Workload

No developer can predict every workload a campus will support over its lifetime. That isn’t the goal.

What matters is building a network foundation that can handle growth, changing capacity requirements, and technologies that aren’t in the plan yet. The duct, routes, and entrance facilities established today will shape what the campus can support long after its first workloads are deployed.

The AI campus fiber provider selected today may still be there after the workloads have changed more than once.

That’s why I think of it as a relationship decision disguised as a technology decision.

The physical layer often outlives the workload architecture it was designed to support. That’s why fiber decisions deserve more scrutiny than they sometimes get. While developers don’t need to predict the next computing architecture, they do need to:

1. budget 18-24 months for the fiber build, and
2. balance capacity for today versus growth in the future.

Data Center Developers and Network Operators Bring Different Expertise

Many data center developers entering today’s AI infrastructure market come from construction, energy, and commercial real estate. They know land acquisition, power procurement, entitlements, and complex construction schedules. Network planning, however, may not yet have a dedicated owner inside the organization.

Field note: One large data center developer I know hired its first network lead in the last three months. Until then, no one inside the organization had direct responsibility for long-term network planning.

When that expertise isn’t involved early, delays can follow. Before a developer starts pitching the site to potential tenants, there should always be a plan for duct count, entrance paths, route diversity, and fiber capacity.

Those early decisions provide speed to market for both the data center and tenant.

Plan Fiber Infrastructure Before the Tenant Is Signed

Developers often ask a reasonable question: How do you design a network for a campus before the prospective tenant has signed a lease?

Start with what others in their tenant class have consumed at other locations.

GPU cloud providers and hyperscalers often repeat the same basic infrastructure and capacity patterns from site to site. Those patterns don’t replace tenant-specific planning, but they give you something concrete to design against.

Field note: I recently met with a developer whose preliminary plan included two conduits. At comparable locations, the prospective tenant had required seven conduits with two-inch innerduct.

Two conduits weren’t simply a smaller version of the right design. That plan could have meant reopening the site in year two to install infrastructure we could have anticipated in year one. The point isn’t to overbuild. It’s to preserve options for what the campus and tenant are reasonably likely to need without creating avoidable cost, delay, and disruption later.

Start AI Data Center Network Planning Early

If you’re developing a data center campus and nobody owns network planning yet, have that conversation before the site plan is finalized.

Our team can look at what comparable tenants have deployed elsewhere, map that back to the physical infrastructure the site will need and flag the decisions that could limit future growth.

To talk through the network foundation for your next data center development, contact the Lightpath Major Infrastructure Solutions team or connect with me on LinkedIn.