SD-WAN and SASE Architecture Performance
This dataset provides detailed, timestamped metrics on SD-WAN and SASE architecture performance, covering underlay and overlay network characteristics, application steering policies, path selection algorithms, security service chaining, and cloud on-ramp latency. It enables comprehensive analysis of network health, security posture, and cloud connectivity, supporting operational optimization and strategic planning for modern enterprise networks.
Sample rows
preview · 8 of 350 rows · all 21 columns| record_idstring | underlay_typestring | overlay_packet_loss_pctfloat | security_chain_ztnaboolean | application_namestring | measurement_datetimedatetime | site_idstring | underlay_latency_msfloat | underlay_jitter_msfloat | underlay_packet_loss_pctfloat | overlay_tunnel_idstring | overlay_latency_msfloat | overlay_jitter_msfloat | application_idstring | application_steering_policystring | path_selection_algorithmstring | security_chain_casbboolean | security_chain_fwaasboolean | cloud_onramp_providerstring | cloud_onramp_latency_msfloat | notesstring |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| rec-0001 | MPLS | 0.02 | true | Salesforce | 2024-06-03T10:15:23Z | NYC-001 | 11.2 | 1.1 | 0.02 | tunnel-NYC001 | 13.8 | 1.6 | app-101 | preferred path | SLA-based | false | true | AWS | 19.1 | Stable, low latency/jitter, core business traffic from NYC branch. |
| rec-0002 | Internet | 2.7 | false | Zoom | 2024-06-03T10:17:30Z | SFO-002 | 78.5 | 14.9 | 1.2 | tunnel-SFO002 | 85.2 | 16.8 | app-203 | failover | load balancing | true | true | Azure | 94 | Moderate jitter/loss, remote/collab traffic, SFO site with Azure onramp. |
| rec-0003 | LTE | 5.1 | true | Google Workspace | 2024-06-03T10:20:13Z | LDN-007 | 64.3 | 17.6 | 3.9 | tunnel-LDN007 | 71.5 | 19.4 | app-309 | preferred path | load balancing | true | false | GCP | 78.3 | LTE link, moderate latency for Google Workspace; GCP onramp enabled. |
| rec-0004 | MPLS | 0.07 | false | SAP | 2024-06-03T11:02:05Z | NYC-001 | 17.3 | 0.5 | 0.07 | tunnel-NYC001B | 18.7 | 1 | app-105 | preferred path | SLA-based | false | true | AWS | 27.8 | Core business SAP traffic; excellent MPLS path and AWS onramp. |
| rec-0005 | Other | 74.2 | false | blank | 2024-06-03T11:18:04Z | DAL-005 | 302.6 | 80.7 | 58.2 | tunnel-DAL005 | 353.3 | 89.1 | blank | blank | blank | false | true | blank | blank | Edge case with extreme latency and packet loss, legacy network in Dallas. |
| rec-0006 | Internet | 1.1 | true | Teams | 2024-06-03T11:23:17Z | NYC-001 | 47.5 | 7.3 | 0.4 | tunnel-NYC001C | 55.7 | 9.2 | app-222 | failover | load balancing | true | false | Azure | 59.8 | Teams traffic over internet, moderate loss, Azure onramp for NYC. |
| rec-0007 | LTE | 8.6 | false | Slack | 2024-06-03T12:01:46Z | LDN-007 | 98.7 | 28.2 | 7.5 | tunnel-LDN007B | 107.3 | 31.2 | app-401 | failover | load balancing | true | true | AWS | 112.2 | Slack traffic over LTE, high jitter/loss, AWS onramp from London. |
| rec-0008 | Other | 100 | false | blank | 2024-06-03T12:12:27Z | SFO-002 | 400.2 | 95.8 | 99.3 | tunnel-SFO002B | 437.1 | 104.2 | blank | blank | blank | false | false | blank | blank | Test scenario, failed legacy overlay, SFO site. |
| rec-0009 | MPLS | 0.03 | true | Oracle | 2024-06-03T12:32:08Z | DAL-005 | 14.8 | 0.7 | 0.03 | tunnel-DAL005B | 16.1 | 1.1 | app-110 | preferred path | SLA-based | false | true | GCP | 24.6 | Oracle core traffic, low latency MPLS, GCP onramp. |
| rec-0010 | Internet | 8.2 | true | Surveillance | 2024-06-03T12:45:44Z | NYC-001 | 115.6 | 26.5 | 6.3 | tunnel-NYC001D | 121.9 | 29.4 | app-350 | failover | load balancing | true | true | AWS | 126.7 | IoT Surveillance feed, high loss/jitter, AWS onramp enabled. |
| rec-0011 | LTE | 6.9 | true | Analytics | 2024-06-03T13:01:12Z | CHI-003 | 75.1 | 22 | 5.2 | tunnel-CHI003 | 81.1 | 23.9 | app-425 | failover | load balancing | true | true | GCP | 87.5 | Analytics data, LTE transport with GCP onramp and full security chain. |
| rec-0012 | MPLS | 0.05 | true | Office 365 | 2024-06-03T13:14:31Z | SFO-002 | 12.9 | 0.3 | 0.05 | tunnel-SFO002C | 13.5 | 1 | app-123 | preferred path | SLA-based | false | true | Azure | 21.3 | Business O365 traffic over MPLS, low latency, SFO site. |
| rec-0013 | Internet | 1.5 | true | Teams | 2024-06-03T13:21:57Z | DAL-005 | 42.2 | 5.6 | 0.7 | tunnel-DAL005C | 46.9 | 6.8 | app-215 | failover | load balancing | true | false | Azure | 53.2 | Teams traffic, moderate internet path, Azure onramp for Dallas. |
| rec-0014 | Other | 76.4 | false | LegacyApp | 2024-06-03T13:34:44Z | LDN-007 | 286.1 | 87.4 | 61.8 | tunnel-LDN007C | 308.6 | 94.8 | app-987 | failover | load balancing | false | true | Other | 312.4 | Legacy app over extreme latency path, service chaining for compliance. |
| rec-0015 | LTE | 3.8 | false | Google Workspace | 2024-06-03T13:51:19Z | DAL-005 | 56.8 | 13.4 | 2.8 | tunnel-DAL005D | 62.7 | 15.6 | app-302 | preferred path | load balancing | true | false | GCP | 68.2 | Collab traffic, moderate LTE path, Dallas site GCP onramp. |
| rec-0016 | Internet | 0 | false | blank | 2024-06-02T23:59:00Z | NYC-001 | 0 | 0 | 0 | tunnel-NYC001E | 0 | 0 | blank | blank | blank | false | false | blank | blank | Test record, all zero values, midnight measurement for NYC sensor. |
| rec-0017 | MPLS | 0.01 | true | SAP | 2024-06-03T14:07:18Z | CHI-003 | 9.3 | 0.8 | 0.01 | tunnel-CHI003B | 12.2 | 1.3 | app-102 | preferred path | SLA-based | false | true | Azure | 16.9 | CHI SAP records, very low latency/jitter, Azure onramp. |
| rec-0018 | LTE | 9.5 | true | Surveillance | 2024-06-03T14:13:57Z | DAL-005 | 106.2 | 29.5 | 7.8 | tunnel-DAL005E | 112.4 | 31.7 | app-451 | failover | load balancing | true | true | AWS | 119.1 | Surveillance feed, LTE, with full security, AWS onramp Dallas. |
| rec-0019 | Internet | 2.4 | false | Teams | 2024-06-03T14:22:43Z | LDN-007 | 59.7 | 10.5 | 1.3 | tunnel-LDN007D | 69.1 | 13.6 | app-215 | failover | load balancing | true | true | Azure | 74.8 | London Teams traffic, internet link, moderate loss and Azure onramp. |
| rec-0020 | MPLS | 0.06 | true | Oracle | 2024-06-03T14:29:55Z | SFO-002 | 19.9 | 0.9 | 0.06 | tunnel-SFO002D | 21.3 | 1.2 | app-104 | preferred path | SLA-based | false | true | AWS | 28.6 | Oracle records, stable MPLS and AWS onramp for SFO. |
What the 350 rows show
from the 350-row sampleOther (underlay type) stands out: mean overlay_
- 54%security_
chain_ ztna = true - 3.7median overlay_
packet_ loss_ pct - 2application steering policies
- 2path selection algorithms
- 4cloud onramp providers
- 34sites
Median 3.7, from 0.0 to 120.0.
- string 10
- float 7
- datetime 1
- boolean 3
Columns
21 columns in four groups| column | type | description | example |
|---|---|---|---|
| Text 10 columns | |||
record_id | string | Unique identifier for each performance recordunique | rec-0001 |
site_id | string | Unique identifier for the network site or branch | NYC-001 |
underlay_type | string | Type of underlay transport used (e.g., MPLS, Internet, LTE)MPLS · Internet · LTE · Other | MPLS |
overlay_tunnel_id | string | Unique identifier for the SD-WAN overlay tunnel | tunnel-NYC001 |
application_id | string | Unique identifier for the application being steeredoptional | app-101 |
application_name | string | Human-readable name of the applicationoptional | Salesforce |
application_steering_policy | string | Policy applied for application steering (e.g., preferred path, failover)2 policies · optional | preferred path |
path_selection_algorithm | string | Algorithm used for path selection (e.g., SLA-based, load balancing)2 algorithms · optional | SLA-based |
cloud_onramp_provider | string | Name of the cloud provider for on-ramp (e.g., AWS, Azure, GCP)AWS · Azure · GCP · Other · optional | AWS |
notes | string | Additional notes or comments about the measurement or configurationoptional | Stable, low latency/jitte… |
| Numbers 7 columns | |||
underlay_latency_ms | float | Measured latency of the underlay transport in milliseconds0 or more · optional | 11.2 |
underlay_jitter_ms | float | Measured jitter of the underlay transport in milliseconds0 or more · optional | 1.1 |
underlay_packet_loss_pct | float | Packet loss percentage for the underlay transport0 to 100 · optional | 0.02 |
overlay_latency_ms | float | Measured latency of the overlay tunnel in milliseconds0 or more · optional | 13.8 |
overlay_jitter_ms | float | Measured jitter of the overlay tunnel in milliseconds0 or more · optional | 1.6 |
overlay_packet_loss_pct | float | Packet loss percentage for the overlay tunnel0 to 100 · optional | 0.02 |
cloud_onramp_latency_ms | float | Measured latency to cloud on-ramp in milliseconds0 or more · optional | 19.1 |
| Dates and times 1 column | |||
measurement_datetime | datetime | Timestamp when the performance metrics were recorded | 2024-06-03T10:15:23Z |
| True or false 3 columns | |||
security_chain_ztna | boolean | Indicates if Zero Trust Network Access (ZTNA) is part of the security service chainoptional | true |
security_chain_casb | boolean | Indicates if Cloud Access Security Broker (CASB) is part of the security service chainoptional | false |
security_chain_fwaas | boolean | Indicates if Firewall-as-a-Service (FWaaS) is part of the security service chainoptional | true |
Use it for
A telecommunications dashboard
The security_
chain_ ztna rate, overlay_ packet_ loss_ pct by underlay_ type and a breakdown of application_ name. Excel, Power BI or Tableau. Why do the 69 Other rows have a mean overlay_
packet_ loss_ pct of 73.6? A root-cause class exercise
Hand out the rows and one question. The answer is in the data, not in the brief.
- Records350rec-00010.02MPLSrec-00022.7Internetrec-00035.1LTE
A software demo
Believable records with measurement_
datetime, site_ id and underlay_ type to fill a screen in front of a buyer.
This dataset350 rows21 columns
Yours1,000 rows21 columnssite_id: UK only
blueprint · sd-wan-and-sase-architecture-performance
Behind this dataset
Same schema. As many rows as you need.
These 350 rows came out of a blueprint — 21 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
- SD-WAN edge device ID and location (branch office, data center, cloud)
- Underlay transport: MPLS, internet (broadband), LTE/5G wireless
- Overlay tunnel: IPsec, GRE, VXLAN for transport-agnostic connectivity
- Application identification: deep packet inspection (DPI) for steering decisions
- Path selection: latency-based, loss-based, jitter-based, policy-based
- Active/active load balancing across multiple underlays
- SASE security services: ZTNA (Zero Trust), CASB, SWG (Secure Web Gateway), FWaaS
- Cloud on-ramp: direct connect to AWS, Azure, GCP with optimized routing
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
- sd-wan-and-sase-architecture-performance