Telecommunications
19 columns
200 rows
8 formats

IP Transport and Backhaul Network Performance

This dataset provides granular, time-stamped performance metrics for IP/MPLS transport networks supporting mobile backhaul and fronthaul. It includes link utilization, latency, jitter, packet loss, MPLS LSP availability, DWDM optical power levels, and BGP route convergence, making it ideal for network reliability analysis, troubleshooting, and capacity planning in telecommunications environments.

last updated 1 Nov 2025
by GoMask

The brief that made it

Real-time monitoring and troubleshooting of mobile transport networks

Sample rows

preview · 8 of 200 rows · all 19 columns

record_idstring	network_segmentstring	link_utilization_percentfloat	resilience_event_detectedboolean	measurement_timestampdatetime	link_idstring	link_namestring	mpls_lsp_idstring	mpls_lsp_availabilityfloat	latency_msfloat	jitter_msfloat	packet_loss_percentfloat	dwdm_optical_power_dbmfloat	bgp_route_convergence_time_secfloat	site_idstring	site_namestring	citystring	statestring	countrystring
rec-00001	backhaul	79.2	false	2024-06-01T08:17:12Z	lnk00001	NYC-BK-Fiber01	lsp-0001	99.8	13.4	1.2	0.2	-4.3	8.2	S-NYC01-01	NYC Main Hub	New York	NY	USA
rec-00002	backhaul	65.8	false	2024-06-01T08:34:42Z	lnk00002	SFO-BK-Fiber02	lsp-0002	100	11.7	0.9	0	-7.2	6.9	S-SFO01-02	San Francisco Central	San Francisco	CA	USA
rec-00003	fronthaul	32.1	false	2024-06-01T08:58:36Z	lnk00003	London-FH-01	blank	blank	2.4	0.3	0	blank	blank	S-LON01-03	London West	London	ENG	UK
rec-00004	fronthaul	61.7	false	2024-06-01T09:11:14Z	lnk00004	blank	lsp-0003	97.6	3.2	0.7	0.1	-7.8	blank	S-LON02-04	London East	London	ENG	UK
rec-00005	backhaul	54.3	false	2024-06-01T09:31:55Z	lnk00005	Berlin-BK-Core	lsp-0004	100	7.9	0.5	0	-3.7	5.4	S-BER01-05	Berlin Zentrum	Berlin	BE	DE
rec-00006	fronthaul	0	false	2024-06-01T09:42:18Z	lnk00006	blank	blank	blank	0	0	0	blank	blank	S-BER02-06	Berlin Nord	Berlin	BE	DE
rec-00007	backhaul	91.2	true	2024-06-01T10:05:33Z	lnk00007	Mumbai-BK-Edge	lsp-0005	76.5	44.7	13.6	34.9	-15.4	122.8	S-MUM01-07	Mumbai Gateway	Mumbai	MH	IN
rec-00008	backhaul	100	true	2024-06-01T10:17:43Z	lnk00008	Delhi-BK-Core	lsp-0006	54.7	101.3	29.8	67.7	-19.5	290.5	S-DEL01-08	Delhi Hub	Delhi	DL	IN
rec-00009	fronthaul	72.5	false	2024-06-01T10:32:01Z	lnk00009	Paris-FH-01	lsp-0007	99.9	3.4	0.8	0.2	-8.7	blank	S-PAR01-09	Paris Centre	Paris	IDF	FR
rec-00010	fronthaul	12.4	false	2024-06-01T10:55:20Z	lnk00010	Paris-FH-02	blank	blank	1.4	0.2	0	blank	blank	S-PAR02-10	Paris Nord	Paris	IDF	FR
rec-00011	backhaul	82.7	false	2024-06-01T11:14:17Z	lnk00011	Tokyo-BK-Fiber02	lsp-0008	100	15.2	1.6	0	-2.1	8.5	S-TYO01-11	Tokyo Shinjuku	Tokyo	TK	JP
rec-00012	backhaul	0	true	2024-06-01T11:34:48Z	lnk00012	Tokyo-BK-Fiber03	lsp-0009	0	500	250	99.9	-25	400	S-TYO02-12	Tokyo Ginza	Tokyo	TK	JP
rec-00013	fronthaul	77.4	false	2024-06-01T11:59:23Z	lnk00013	Shanghai-FH-Edge	blank	blank	2.9	0.6	0.3	-5.9	blank	S-SHG01-13	Shanghai Pudong	Shanghai	SH	CN
rec-00014	fronthaul	81.6	false	2024-06-01T12:14:04Z	lnk00014	blank	lsp-0010	95.3	4.2	1	0.5	-6.5	blank	S-SHG02-14	Shanghai Central	Shanghai	SH	CN
rec-00015	backhaul	63.1	false	2024-06-01T12:26:55Z	lnk00015	Sydney-BK-Core	lsp-0011	98.6	17.6	1.1	0.1	-5.2	7.3	S-SYD01-15	Sydney Harbour	Sydney	NSW	AU
rec-00016	backhaul	12.3	true	2024-06-01T12:40:23Z	lnk00016	Sydney-BK-Edge	lsp-0012	0	87.5	30.8	13.2	-18.6	101.6	S-SYD02-16	Sydney North	Sydney	NSW	AU
rec-00017	fronthaul	23.9	false	2024-06-01T13:01:42Z	lnk00017	Toronto-FH-West	blank	blank	2.1	0.4	0	blank	blank	S-TOR01-17	Toronto West	Toronto	ON	CA
rec-00018	fronthaul	55.7	false	2024-06-01T13:16:15Z	lnk00018	blank	lsp-0013	99.1	4.6	0.9	0.3	-7.2	blank	S-TOR02-18	Toronto East	Toronto	ON	CA
rec-00019	backhaul	74.3	false	2024-06-01T13:34:29Z	lnk00019	MexicoCity-BK-Core	lsp-0014	98.5	18.3	2.2	0.4	-6.8	10.8	S-MEX01-19	Mexico City Centro	Mexico City	CMX	MX
rec-00020	backhaul	94.6	true	2024-06-01T13:52:17Z	lnk00020	MexicoCity-BK-Edge	lsp-0015	64.7	58.1	18.7	34.6	-14.2	122.4	S-MEX02-20	Mexico City Sur	Mexico City	CMX	MX

What the 200 rows show

from the 200-row sample

Backhaul (network segment) stands out: 36 of its 96 rows have resilience_event_detected = true, against 1 of 104 for the rest.

19%resilience_event_detected = true
63.5median link_utilization_percent
98.7median mpls_lsp_availability
6.8median latency_ms
1.0median jitter_ms
0.10median packet_loss_percent

Resilience event detected rate by network_segmentresilience_event_detected = true

Backhaul (network segment)'s mean link_utilization_percent is 70.1, against 40.6 for fronthaul.

link_utilization_percent200 rows, in bands of 10

Median 63.5, from 0.0 to 100.0.

19 columns by typefrom the column list below

string 10
float 7
datetime 1
boolean 1

Columns

19 columns in four groups

blueprint · 19 columns
column	type	description	example
Text 10 columns
`record_id`	string	Unique identifier for each network performance recordunique	rec-00001
`network_segment`	string	Type of network segment (e.g., backhaul, fronthaul)backhaul · fronthaul	backhaul
`link_id`	string	Unique identifier for the network link being measured	lnk00001
`link_name`	string	Human-readable name or label for the network linkoptional	NYC-BK-Fiber01
`mpls_lsp_id`	string	Identifier for the MPLS Label Switched Path (LSP) if applicableoptional	lsp-0001
`site_id`	string	Identifier for the physical site or location of the network segmentoptional	S-NYC01-01
`site_name`	string	Human-readable name of the siteoptional	NYC Main Hub
`city`	string	City where the network segment or site is locatedoptional	New York
`state`	string	State or province where the network segment or site is locatedoptional	NY
`country`	string	Country where the network segment or site is locatedoptional	USA
Numbers 7 columns
`mpls_lsp_availability`	float	Availability percentage of the MPLS LSP during the measurement period0 to 100 · optional	99.8
`link_utilization_percent`	float	Percentage of link bandwidth utilized during the measurement period0 to 100	79.2
`latency_ms`	float	Measured latency in milliseconds for the network segment0 or more · optional	13.4
`jitter_ms`	float	Measured jitter in milliseconds for the network segment0 or more · optional	1.2
`packet_loss_percent`	float	Percentage of packets lost during the measurement period0 to 100 · optional	0.2
`dwdm_optical_power_dbm`	float	Measured DWDM optical power level in dBmoptional	-4.3
`bgp_route_convergence_time_sec`	float	Time taken for BGP route convergence in seconds0 or more · optional	8.2
Dates and times 1 column
`measurement_timestamp`	datetime	Date and time when the network metric was measured	2024-06-01T08:17:12Z
True or false 1 column
`resilience_event_detected`	boolean	Indicates if a resilience event (e.g., failover, reroute) was detected during measurementoptional	false

Use it for

A telecommunications dashboard
The resilience_event_detected rate and link_utilization_percent by network_segment. Excel, Power BI or Tableau.
Why do 37 of 200 rows have resilience_event_detected = true?
A root-cause class exercise
Hand out the rows and one question. The answer is in the data, not in the brief.
Records200
rec-0000179.2backhaul
rec-0000791.2backhaul
rec-00008100backhaul
A software demo
Believable records with measurement_timestamp, network_segment and link_id to fill a screen in front of a buyer.

This dataset200 rows19 columns

Yours1,000 rows19 columnssite_id: UK only

blueprint · ip-transport-and-backhaul-network-performance

Behind this dataset

Same schema. As many rows as you need.

These 200 rows came out of a blueprint — 19 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

Link ID and circuit endpoints (router/switch interfaces)
Link capacity (1GE, 10GE, 100GE) and utilization percentage
MPLS LSP (Label Switched Path) availability percentage (>99.99% target)
Latency (one-way delay) and jitter (delay variation) in milliseconds
Packet loss rate (<0.01% for carrier-grade transport)
DWDM optical power levels (Tx/Rx dBm) and OSNR (Optical SNR)
BGP routing updates and convergence time after link failure
QoS class performance: EF (Expedited Forwarding) for voice, AF for data

Rows1,000 rows10,000 rows100,000 rows1,000,000 rows

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: ip-transport-and-backhaul-network-performance

What should your data show?

No signup. No card.

Sample rows

What the 200 rows show

Columns

Use it for

A telecommunications dashboard

A root-cause class exercise

A software demo

Make it yours.

Same schema. As many rows as you need.

More in Telecommunications

What should your data show?