A privately owned fiber network built and operated across California — engineered as a regional backbone rather than assembled from leased capacity, and reaching the agricultural, industrial, and municipal sites that commercial carriers passed over.
Vast Networks owns and operates its fiber. That is the single fact that explains most of what follows: the routes, the reach into places other carriers skipped, the ability to change capacity without asking a wholesale supplier, and the fact that the person who fixes a fault works for the same company that designed the circuit.
The network began as shared infrastructure for rural independent telephone companies in 1995 and became a regional backbone through a federally funded middle-mile project reaching across 18 California counties. It has been extended and modernised continuously since — most heavily since 2023, with more than 1,600 miles of new construction and roughly 1,500 miles of existing plant rebuilt.
The backbone exists to move traffic between regions at high capacity, which is a different design problem from serving households. It is why a processing plant outside Hanford and a district office in Modesto can sit on the same engineered network, and why extending service to a site that no consumer carrier would build to is a routine project rather than an exception.
The optical layer multiplexes many wavelengths onto the same fiber, so capacity grows by adding channels and changing optics rather than by trenching more glass. Practically, that is what makes a bandwidth increase a configuration change instead of a construction project, and what makes dedicated wavelengths available as a product in their own right.
The same physical network supports fully managed services and dark fiber leases. An organization that wants a circuit delivered and monitored gets one; an organization that wants to light strands with its own optics and control its own upgrade cycle gets that instead, on routes where strands are available.
Physical diversity — a second path that does not share a conduit, a bridge, or a right of way with the first — is the most effective protection against a fiber cut. It is also entirely site-specific: whether it can be built to your building depends on what exists nearby. We engineer it where it is achievable and say so plainly where it is not.
Buried fiber is less exposed to weather and to the ordinary hazards that take aerial plant down. It is not immune — construction equipment and agricultural work cause cuts every year across the state — which is why the design conversation always includes what happens during a repair, not only how the network behaves when everything is intact.
Engineering and network operations staff are based in California, with the company headquartered in Fresno. Faults are detected by monitoring rather than by customer report where possible, and escalation reaches people who can act on the network rather than a script.
Regional presence across California, with the deepest concentration in the Central Valley. Presence is not the same as availability at a given address — each market page explains what that means locally.
Operating outside these markets? The network extends beyond the cities listed here, and regional transport reaches further still. Ask us about your location.
Telecom marketing routinely blurs two different claims. Presence means the network reaches a region — there is fiber in the ground and traffic moving across it. Availability means fiber can actually be delivered to your building, which depends on how far that building sits from existing plant, what the route in would require, what construction and permitting are involved, and whether the property will grant access.
A network can be present throughout your city and still require a several-hundred-foot build to reach your suite. That is why we do not publish a coverage checker that returns a green tick for an address, and why nobody should trust one that does. What we publish instead is an honest process: send the address, an engineer checks it against the network, and you get a real answer — including when the answer is that a build is not practical.
Service availability depends on location, network proximity, capacity, and engineering review. Share an address and we will confirm what can be delivered there.
Detailed fiber route geometry, splice enclosures, handhole locations, regeneration sites, and facility coordinates are the kind of information that makes critical infrastructure easier to damage. Publishing an interactive map of them would be a marketing asset and an operational liability, and the trade is not close.
Regional presence, market coverage, and route availability for a specific requested path are all things we will discuss directly. If you are evaluating carriers and need route information for a diversity assessment, that is a conversation under a confidentiality agreement, not a web page.
Where the network itself is the product being evaluated.
Nearly three decades of infrastructure investment, phase by phase.
The regional backbone grew out of a middle-mile project spanning 18 California counties, and since 2023 the company has built more than 1,600 miles of new fiber while modernising roughly 1,500 miles of existing plant. The company history page covers each phase of that build in detail.
It owns and operates the physical plant. That is what allows capacity changes, route decisions, and repairs to happen inside one organization rather than across a wholesale boundary — and it is the difference between a network operator and a reseller with a service desk.
No. Detailed route paths, splice locations, handhole positions, and facility coordinates are infrastructure security information, and publishing them would be irresponsible regardless of the marketing value. We confirm availability privately for a specific address or route.
Presence means the network reaches a region. Availability means fiber can be delivered to your specific building, which depends on the distance from existing plant, the route in, construction requirements, and property access. A network can be present in your city and still require a build to reach your address.
Request an availability review. Send the address and what the connection has to carry, and an engineer checks it against the network and tells you what is deliverable, what construction is involved, and what the timeline looks like — including when a build is not practical.
Yes — that is what point-to-point circuits and wavelengths are for. Traffic between two of your locations rides a private path on the network and never enters the public internet, which is the usual requirement for control systems, clinical data, and replication.
Send us the address and a bandwidth target. A California-based engineer confirms what can be delivered there, what it involves, and how long it takes.
Give us the address and the requirement. You will get an engineer's assessment of what can be delivered there — not a coverage-map guess.
Service availability depends on location, network proximity, capacity, and engineering review. Share an address and we will confirm what can be delivered there.