Explore the VAST Networks California fiber map: about 1,346 miles drawn in the generalised public route layer and ninety city markers. Map-line mileage is not the total network footprint. Check availability for your address with an engineer.
Drawn from the plant records and generalised for publication: the fiber route in blue, the expanded network over it in its own colour. Pan and zoom to follow either one and read the city names — it is an orientation tool, not a serviceability lookup.
Routes are generalised from the plant records and provided for orientation. They do not represent surveyed route paths, and a city on the map does not confirm service at a specific address.
The map draws two things. The blue is the fiber route the map has always shown. Over it, in its own colour, is the expanded network — about 2,372 further miles of route on the same plate, following the valley the length of the state, running north past Redding toward the Oregon line, and turning west onto the central coast.
It is drawn under exactly the rules the network is. The same lattice snap that makes the geometry safe to publish, the same reduction and smoothing afterwards, the same refusal to mark a splice, a handhole or a facility at any zoom level. Nothing about the expanded network is published at a precision the network itself is not — and where the two layers share ground the blue is the one that reads, so a mile both of them use is not counted twice by eye.
What it changes is reach. 117 incorporated cities sit on the expanded network, and 44 of them are places the existing routes do not reach — Santa Maria, Vacaville, Chico, Tracy, Redding, Lodi, Woodland, San Luis Obispo and Hollister among them. Eleven counties appear on the map that were not on it before: Shasta, Siskiyou, Modoc, Tehama, Glenn, Butte, Solano, San Benito, San Luis Obispo, Santa Barbara and Ventura.
The expansion overlay shows about 2,372 drawn miles after generalisation. This is not a verified total of newly built or planned fiber. The layers can overlap, so their lengths must not be added to estimate the owned network. Ask an engineer about current serviceability.
This map is drawn from the network itself. Every route on it is real plant, generalised — snapped to a grid coarse enough that no line on the page can be dug against — and every one of the ninety cities marked is a California city the network actually reaches. It is an orientation tool. It is the fastest way to answer "do you operate anywhere near me", and it is not, and cannot be, an answer to "can you serve my building".
Those are two different questions, and most of what follows is about the distance between them. A network can be present throughout a city and still need a several-hundred-foot build to reach one particular suite; a site well outside any shaded area can turn out to be straightforward because a route already passes nearby. The map narrows the question. An engineer answers it.
The map draws the fiber route in blue and the expanded network in its own colour over the top. Both come from plant exports, both are generalised by exactly the same passes before they are published, and neither is drawn at a precision the other is not. Where the two run together the blue is the one that reads, so a shared mile is never counted twice by eye.
The public route layer draws about 1,346 miles after generalisation of the source records. This is map-line length, not surveyed mileage or the total owned network footprint. Use the ninety city markers for regional orientation; request an engineering review for an address.
Not the centre-lines. Every coordinate is snapped to a grid nearly two miles across before it is published, which keeps the shape of a route and destroys its position — and splice enclosures, handhole positions, regeneration sites and facility coordinates are not on the map at any zoom level at all. If you need route-level information for a diversity assessment, that is a conversation under a confidentiality agreement.
Presence means the network reaches an area. Availability means fiber can be delivered to your specific address, which depends on distance to usable plant, the physical route in, construction method, permitting, and whether the property will grant access. A shaded region on a map answers the first and says nothing about the second.
Two buildings on the same block can have completely different answers, because one sits across a road that needs a bore and the other does not. That last stretch is where cost and schedule are actually determined, and it is invisible at map scale — which is exactly why we do not put a green tick on an address and call it a quote.
Ninety cities are marked because ninety incorporated cities sit on the route. The network also passes unincorporated communities, farmland, packing houses and industrial sites that are not cities and have no name on this map — it was built specifically to reach places no consumer carrier would build to. Not seeing your town is a reason to ask, not a reason to stop.
Send the address and what the connection has to carry. A California-based engineer checks it against the network and tells you what is deliverable, what construction is involved, and what the timeline looks like — including, when it is the case, that a build there is not practical.
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.
Presence is a region. Availability is a building.
Plenty of carriers will take an address and return an instant yes. It is a good experience and frequently a wrong answer, because the things that decide whether fiber can reach a building — how far it sits from usable plant, what the route in crosses, whether the work needs a bore or a trench or an aerial run, which permits that triggers, and whether the property owner will grant access — are not in any database that answers in 200 milliseconds.
So this map stops where its honesty stops. It will show you that the network runs through your region, which is genuinely useful and is the point of publishing it. It will not claim to know what happens in the last few hundred feet to your door. That part gets checked by a person who can look at the plant records, and you get told what is actually involved — including when the answer is that a build there does not make sense.
Service availability depends on location, network proximity, capacity, and engineering review. Share an address and we will confirm what can be delivered there.
What can be delivered where the map shows reach.
No. The map shows where the network is present at a regional scale. Availability at a specific building depends on the distance from existing plant, the route in, construction requirements, permitting, and property access — none of which are visible at map scale. Presence tells you it is worth asking; an engineering review tells you the answer.
They are the actual routes, generalised. The map is generated from the plant records, but every coordinate is snapped to a grid nearly two miles across before it is published, so what survives is the shape of a route and not its position. That is deliberate: precise route geometry, splice locations and handhole positions make critical infrastructure easier to damage, and publishing them would be irresponsible regardless of the marketing value. Nothing on this map can be dug against.
The expanded network, drawn as its own layer over the fiber route. It adds about 2,372 drawn miles to the plate and puts 44 incorporated cities on the map that the existing routes do not reach, in eleven counties the map did not previously enter. It is generalised exactly as the network is — same lattice, same reduction — and it carries the same caveat: a line near a building is not an answer about that building.
Often, yes. The map and the market list reflect where we have enough local detail to publish, while the regional backbone and transport reach further. Rural, agricultural, and industrial sites outside any listed market are a large part of what this network was built for — send the address and we will tell you what reaching it involves.
It is approximate by design. Boundaries are drawn to communicate regional reach, not to be measured against a parcel line, and they are not a serviceability lookup. Where the map and an engineering review disagree about your address, the review is the authoritative answer — that is what it exists for.
Not from what is published here. Physical diversity depends on whether a second path shares a conduit, a bridge, or a right of way with the first, and establishing that requires route-level information this map intentionally omits. We will work through it with you directly, under a confidentiality agreement, as part of designing the circuit.
The map is a picture of where the network reaches. The availability check is a request that puts your address in front of an engineer, who checks it against the network and comes back with what can be delivered, what it involves, and how long it takes. The first is orientation; the second is an answer you can plan around.
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.
The map narrows the question to a region. This answers it for a building — send the address and the requirement, and an engineer comes back with what is deliverable there.
Service availability depends on location, network proximity, capacity, and engineering review. Share an address and we will confirm what can be delivered there.