Fiber Backhaul and Fronthaul Connectivity
This dataset provides a comprehensive view of fiber optic backhaul and fronthaul infrastructure connecting cellular sites, detailing fiber routes, providers, capacity, latency, redundancy, and 5G fronthaul protocol support. It is ideal for telecom network planning, reliability analysis, and optimization of high-speed mobile connectivity.
Sample rows
preview · 8 of 301 rows · all 17 columns| fiber_route_idstring | route_statusstring | latency_msfloat | redundant_pathboolean | fronthaul_versionstring | cell_site_idstring | cell_site_namestring | cell_site_latitudefloat | cell_site_longitudefloat | fiber_providerstring | fiber_typestring | circuit_idstring | capacity_gbpsfloat | redundant_fiber_route_idstring | fronthaul_typestring | installation_datedate | last_maintenance_datedate |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| FR-001 | active | 1.2 | true | CPRI v7.0 | CS-1001 | San Francisco Downtown | 37.7749 | -122.4194 | FiberNet | carrier fiber | CIR-2001 | 120.5 | FR-002 | CPRI | 2020-06-18 | 2023-08-15 |
| FR-002 | active | 2.3 | true | CPRI v6.1 | CS-1002 | San Francisco SOMA | 37.7786 | -122.3893 | FiberNet | carrier fiber | CIR-2002 | 145.7 | FR-001 | CPRI | 2019-03-17 | 2022-12-21 |
| FR-003 | active | 1.8 | true | CPRI v8.0 | CS-1003 | Seattle Capitol Hill | 47.6257 | -122.3236 | MetroFiber | carrier fiber | CIR-2003 | 80.9 | FR-004 | CPRI | 2018-04-10 | 2024-01-30 |
| FR-004 | active | 1.1 | true | CPRI v7.0 | CS-1004 | Seattle Ballard | 47.6686 | -122.3861 | MetroFiber | carrier fiber | CIR-2004 | 93.2 | FR-003 | CPRI | 2021-10-05 | 2023-10-12 |
| FR-005 | active | 2 | true | CPRI v7.0 | CS-1005 | Downtown LA | 34.0522 | -118.2437 | Lightwave | carrier fiber | CIR-2005 | 200 | FR-006 | CPRI | 2022-03-18 | 2023-02-08 |
| FR-006 | active | 2.1 | true | CPRI v8.0 | CS-1006 | LA Hollywood | 34.0928 | -118.3287 | Lightwave | carrier fiber | CIR-2006 | 175.8 | FR-005 | CPRI | 2018-12-22 | 2022-11-02 |
| FR-007 | active | 1.5 | true | CPRI v6.0 | CS-1007 | London Canary Wharf | 51.5055 | -0.0235 | NextGen Fiber | carrier fiber | CIR-2007 | 110.4 | FR-008 | CPRI | 2023-01-17 | 2024-02-10 |
| FR-008 | active | 2.2 | true | CPRI v7.0 | CS-1008 | London Soho | 51.5139 | -0.1362 | NextGen Fiber | carrier fiber | CIR-2008 | 132.6 | FR-007 | CPRI | 2022-09-27 | 2023-08-23 |
| FR-009 | active | 1.9 | true | CPRI v8.0 | CS-1009 | New York Lower Manhattan | 40.7075 | -74.0113 | MetroFiber | carrier fiber | CIR-2009 | 152.9 | FR-010 | CPRI | 2020-04-11 | 2023-03-09 |
| FR-010 | active | 1.4 | true | CPRI v7.0 | CS-1010 | New York Midtown | 40.758 | -73.9855 | MetroFiber | carrier fiber | CIR-2010 | 128.1 | FR-009 | CPRI | 2019-07-08 | 2022-08-16 |
| FR-011 | active | 2.3 | true | CPRI v7.0 | CS-1011 | Chicago Loop | 41.8781 | -87.6298 | Lightwave | carrier fiber | CIR-2011 | 110.2 | FR-012 | CPRI | 2021-03-20 | 2023-07-18 |
| FR-012 | active | 1.9 | true | CPRI v8.0 | CS-1012 | Chicago Wicker Park | 41.9096 | -87.6778 | Lightwave | carrier fiber | CIR-2012 | 98.7 | FR-011 | CPRI | 2022-06-14 | 2023-11-09 |
| FR-013 | active | 1.3 | true | CPRI v6.0 | CS-1013 | San Jose Airport | 37.3626 | -121.929 | NextGen Fiber | carrier fiber | CIR-2013 | 180.6 | FR-014 | CPRI | 2023-05-23 | 2024-03-06 |
| FR-014 | active | 2.2 | true | CPRI v8.0 | CS-1014 | San Jose Downtown | 37.3382 | -121.8863 | NextGen Fiber | carrier fiber | CIR-2014 | 170.9 | FR-013 | CPRI | 2021-08-28 | 2023-09-17 |
| FR-015 | active | 2.8 | false | CPRI v7.0 | CS-1015 | Austin Central | 30.2672 | -97.7431 | FiberNet | metro fiber | CIR-2015 | 18.1 | blank | CPRI | 2012-04-15 | 2021-10-22 |
| FR-016 | active | 3.1 | false | eCPRI v2.0 | CS-1016 | Austin Riverside | 30.2449 | -97.7266 | FiberNet | metro fiber | CIR-2016 | 12.7 | blank | eCPRI | 2015-07-19 | 2023-03-15 |
| FR-017 | active | 4.7 | false | CPRI v6.0 | CS-1017 | Dallas Uptown | 32.8037 | -96.8073 | MetroFiber | metro fiber | CIR-2017 | 8.2 | blank | CPRI | 2010-09-28 | 2018-11-13 |
| FR-018 | active | 3.8 | false | eCPRI v2.0 | CS-1018 | Dallas Deep Ellum | 32.7849 | -96.7831 | MetroFiber | metro fiber | CIR-2018 | 9.7 | blank | eCPRI | 2015-03-21 | 2022-12-05 |
| FR-019 | active | 2.2 | false | CPRI v7.0 | CS-1019 | Houston Midtown | 29.7416 | -95.3725 | GlobalFiber | metro fiber | CIR-2019 | 23.4 | blank | CPRI | 2012-10-14 | 2020-06-12 |
| FR-020 | active | 4.1 | false | eCPRI v2.0 | CS-1020 | Houston Heights | 29.7974 | -95.4008 | GlobalFiber | metro fiber | CIR-2020 | 5.3 | blank | eCPRI | 2016-05-02 | 2021-12-20 |
What the 301 rows show
from the 301-row sampleInactive (route status) stands out: mean latency_
- 55%redundant_
path = true - 2.1median latency_
ms - 2fronthaul types
- 3fiber types
- 8fiber providers
- 110.2median capacity_
gbps
Median 2.1, from 0.60 to 10,000.
- string 10
- float 4
- date 2
- boolean 1
Columns
17 columns in four groups| column | type | description | example |
|---|---|---|---|
| Text 10 columns | |||
fiber_route_id | string | Unique identifier for the fiber route connecting cell sites.unique | FR-001 |
cell_site_id | string | Unique identifier for the cell site connected by the fiber route. | CS-1001 |
cell_site_name | string | Human-readable name or label for the cell site.optional | San Francisco Downtown |
fiber_provider | string | Name of the fiber provider or carrier.8 providers | FiberNet |
fiber_type | string | Type of fiber used for the route (e.g., carrier fiber, dark fiber, metro fiber).carrier fiber · dark fiber · metro fiber | carrier fiber |
circuit_id | string | Unique identifier for the fiber circuit.unique | CIR-2001 |
redundant_fiber_route_id | string | Identifier of the redundant fiber route, if applicable.optional | FR-002 |
fronthaul_type | string | Type of fronthaul protocol supported (e.g., CPRI, eCPRI).CPRI · eCPRI | CPRI |
fronthaul_version | string | Version of the fronthaul protocol (e.g., CPRI v7.0, eCPRI v2.0).optional | CPRI v7.0 |
route_status | string | Current operational status of the fiber route (e.g., active, inactive, under maintenance).active · inactive · under maintenance | active |
| Numbers 4 columns | |||
cell_site_latitude | float | Latitude coordinate of the cell site.-90 to 90 | 37.7749 |
cell_site_longitude | float | Longitude coordinate of the cell site.-180 to 180 | -122.4194 |
capacity_gbps | float | Maximum data transmission capacity of the fiber route in Gbps.0.1 or more | 120.5 |
latency_ms | float | Measured latency of the fiber route in milliseconds.0 or more · optional | 1.2 |
| Dates and times 2 columns | |||
installation_date | date | Date when the fiber route was installed or became operational.optional | 2020-06-18 |
last_maintenance_date | date | Date of the most recent maintenance activity on the fiber route.optional | 2023-08-15 |
| True or false 1 column | |||
redundant_path | boolean | Indicates if the fiber route has a redundant or diverse path for reliability. | true |
Use it for
A telecommunications dashboard
The redundant_
path rate, latency_ ms by route_ status and a breakdown of fronthaul_ version. Excel, Power BI or Tableau. Why do the 51 inactive rows have a mean latency_
ms of 6,485? A root-cause class exercise
Hand out the rows and one question. The answer is in the data, not in the brief.
- Fiber routes301FR-0011.2activeFR-0022.3activeFR-0152.8active
A software demo
Believable fiber routes with cell_
site_ id, cell_ site_ name and cell_ site_ latitude to fill a screen in front of a buyer.
This dataset301 rows17 columns
Yours1,000 rows17 columnscell_site_id: UK only
blueprint · fiber-backhaul-and-fronthaul-connectivity
Behind this dataset
Same schema. As many rows as you need.
These 301 rows came out of a blueprint — 17 columns with generation rules behind each one. Open it in Data Factory to retune a column, add your own, wire in foreign keys, and run it at the size you actually need.
Rules it was built with
- Site ID and fiber circuit ID
- Fiber provider: operator-owned, leased from Zayo/Level3/Lumen, dark fiber
- Fiber capacity: 1GE, 10GE, 100GE for backhaul throughput
- Latency: one-way delay (ms) critical for 5G fronthaul and cloud RAN
- Fronthaul interface: CPRI (LTE), eCPRI (5G), functional split options
- Redundancy: A-side and B-side diverse fiber paths for resilience
- Fiber route diversity: geographic separation to avoid common failures
- Cost: monthly recurring cost (MRC) per circuit
Open the blueprint in Data Factory
1 credit per row. Preview 20 rows free. Buy rows for the full run.
- Exports
- CSV, JSON, JSONL, Parquet, SQL, Excel, TSV, XML
- Licence
- yours to use, including commercially
- API slug
- fiber-backhaul-and-fronthaul-connectivity