Fresno is where the Central Valley concentrates: the largest metro between Sacramento and Bakersfield, a regional health system with facilities spread across the city, a state university, county and municipal networks, and the carrier and data-centre presence that follows all of it. Organizations at that scale eventually run into the same wall — an Ethernet service that was correctly sized three years ago is now carrying replication, imaging, and backup traffic that behaves more like transport than like internet access.
A wavelength is the answer to that specific problem. Rather than a shared platform allocating you a rate, you take an optical channel on the fiber and use all of it: your protocol, your framing, and a capacity that does not vary with anyone else. It sits deliberately between a managed Ethernet circuit and dark fiber — more capacity and more control than the first, none of the equipment ownership and lifecycle of the second.
The transition is usually gradual and then obvious. Storage replication between two facilities, imaging archives moving continuously, a backup target that now holds a meaningful fraction of the organization, research data that arrives in bursts large enough to be scheduled — these are transport workloads, and they are unusually sensitive to variance and unusually indifferent to price per megabit at small sizes. When the conversation turns to whether a scheduled transfer will complete rather than whether users are happy, a dedicated optical channel is generally the cheaper instrument for the same work.
A defined optical channel between two endpoints, at a rate agreed in the contract, with the provider operating the transport equipment. Because the channel is yours, latency is a function of the physical route rather than of a shared platform, and the traffic on it is not queued behind anyone else. What it does not give you is the ownership dark fiber gives: you are not buying strands, you are not procuring optics, and you are not carrying the spares or the equipment refresh. For most organizations that is the correct trade, and dark fiber becomes the right answer only when the capacity trajectory or the protocol requirement outgrows what a channel can be bought as.
For transport between two Fresno facilities, the physical path is the specification that determines both latency and resilience. Two channels that follow the same conduit share every failure on that path, however they are priced or labelled. Where continuity is the objective, ask for the routes on a map, look specifically at the points where paths tend to be forced together — bridges, rail corridors, and the entrance to each building — and have the divergence documented. Sometimes the honest answer at a given pair of addresses is that a genuinely separate route does not exist yet.
This page does not assert that any particular Fresno address can be served with a wavelength. Delivery depends on network proximity at both ends, the construction required to reach them, easements along the route, and the specific service addresses involved. Because a wavelength is a two-ended service, both ends have to work — and a straightforward downtown endpoint paired with a difficult one at the other end produces one answer, not two. An engineering review establishes it for your specific pair before anything is committed.
Full service detail lives on the Wavelength Services page, and the wider market context is on the Fresno location page.
A point-to-point Ethernet service hands you a rate on a shared transport platform; a wavelength hands you an optical channel and lets you decide what runs on it. In practice the difference shows up at higher capacities and with protocols that are not plain Ethernet — Fiber Channel for storage, for instance — and in the fact that the channel is not queued behind other traffic.
Dark fiber is unlit strands you light with your own equipment: you own the optics, the spares, the monitoring, and the refresh cycle, and the capacity ceiling is whatever your equipment supports. A wavelength leaves all of that with the provider and sells you a channel at an agreed rate. Dark fiber is the better answer when capacity growth is steep or unpredictable and you already operate optical equipment; a wavelength is the better answer when you want the channel without the asset.
At a defined rate agreed in the contract for the specific route. Rather than quoting a general figure here, we scope it against the route and the equipment at both ends, because what can be delivered depends on the path — distance and the transport in place along it — rather than on a product tier.
No. It is transport between two points you specify. Organizations frequently pair one with dedicated internet access at a hardened site and carry internet inward across their own network, but the wavelength itself carries whatever you put on it and nothing more.
That is one of the more common uses — connecting a primary site to equipment in a colocation facility at a capacity that makes replication practical. As with any two-ended service, both endpoints are reviewed, and the facility end is usually the simpler of the two.
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.
Send the Fresno address and what the connection needs to carry. An engineer confirms whether it can be served, what the build involves, and how long it takes.
Service availability depends on location, network proximity, capacity, and engineering review. Share an address and we will confirm what can be delivered there.