Network Performance Degradation and Quality Issues
This dataset provides granular records of network performance degradation events, capturing details such as event type, severity, affected KPIs, user impact, and resolution status. It enables telecom operators to analyze quality issues, correlate degradations with network metrics, and improve service reliability through actionable insights.
Sample rows
preview · 8 of 700 rows · all 20 columns| event_idstring | network_segment_typestring | affected_users_countinteger | reported_by_userboolean | event_typestring | event_start_timedatetime | event_end_timedatetime | network_segment_idstring | severity_levelstring | user_report_idstring | kpi_affectedstring | kpi_value_beforefloat | kpi_value_duringfloat | kpi_thresholdfloat | location_latitudefloat | location_longitudefloat | root_causestring | resolution_statusstring | resolution_timedatetime | additional_notesstring |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| EVT-0001 | backbone | 10043 | false | congestion | 2024-06-03T08:14:32Z | 2024-06-03T11:56:32Z | BKB-112 | critical | blank | throughput | 87.2 | 6.1 | 15 | 37.7749 | -122.4194 | Upstream ISP overload | resolved | 2024-06-03T12:08:19Z | Traffic rerouted, normal operation restored. |
| EVT-0002 | cell | 0 | false | packet_loss | 2024-06-02T20:05:09Z | 2024-06-02T22:10:15Z | CELL-4082 | major | blank | packet_loss_rate | 0.01 | 0.67 | 0.15 | 40.7128 | -74.006 | Severe weather interference | resolved | 2024-06-02T22:25:10Z | Cell returned to service after storm passed. |
| EVT-0003 | site | 1 | true | user_reported_issue | 2024-06-04T09:23:44Z | blank | SITE-2038 | minor | USR-45823 | latency | 34.5 | 143.8 | 60 | 51.5074 | -0.1278 | User device misconfiguration | investigating | blank | User contacted support, analysis ongoing. |
| EVT-0004 | region | 8943 | true | slow_data_speed | 2024-06-05T13:11:56Z | blank | REGION-502 | critical | USR-45824 | throughput | 70.1 | 2.4 | 10 | 35.6895 | 139.6917 | Fiber cut due to construction accident | open | blank | Field team dispatched for emergency repair. |
| EVT-0005 | region | 27 | false | intermittent_connectivity | 2024-06-03T03:17:09Z | 2024-06-03T05:49:15Z | REGION-914 | minor | blank | availability | 99.92 | 87.3 | 95 | -33.8688 | 151.2093 | Temporary traffic rerouting | resolved | 2024-06-03T06:02:31Z | Connectivity stabilized after routing update. |
| EVT-0006 | site | 188 | false | high_latency | 2024-06-02T15:41:21Z | 2024-06-02T17:09:12Z | SITE-6012 | major | blank | latency | 44.7 | 211.8 | 120 | 48.8566 | 2.3522 | Software update caused delays | resolved | 2024-06-02T17:29:33Z | Rollback applied, latency returned to baseline. |
| EVT-0007 | site | blank | false | threshold_violation | 2024-06-04T19:26:05Z | 2024-06-04T22:10:31Z | SITE-6078 | minor | blank | latency | 29.8 | 87.6 | 60 | 52.52 | 13.405 | Temporary backhaul congestion | resolved | 2024-06-04T22:25:14Z | Thresholds re-applied, event closed. |
| EVT-0008 | cell | 87 | true | intermittent_connectivity | 2024-06-01T21:00:12Z | blank | CELL-1034 | major | USR-45825 | availability | 99.8 | 92.1 | 95 | -90 | 180 | Unstable cell tower firmware | investigating | blank | Firmware patch scheduled for next maintenance window. |
| EVT-0009 | backbone | 13021 | false | congestion | 2024-06-03T12:33:44Z | 2024-06-03T13:12:32Z | BKB-113 | critical | blank | throughput | 92.5 | 1.2 | 20 | 55.7558 | 37.6173 | DDoS attack on core routers | investigating | blank | Security team engaged, mitigation in progress. |
| EVT-0010 | cell | 178 | true | packet_loss | 2024-06-05T06:15:44Z | blank | CELL-5129 | major | USR-45826 | packet_loss_rate | 0.02 | 0.41 | 0.1 | 34.0522 | -118.2437 | Interference from nearby broadcast station | open | blank | FCC notified, investigation pending. |
| EVT-0011 | site | 6823 | false | slow_data_speed | 2024-06-03T18:21:34Z | 2024-06-03T19:29:33Z | SITE-9023 | critical | blank | throughput | 83.4 | 4.3 | 15 | 41.8781 | -87.6298 | Router failure at aggregation point | resolved | 2024-06-03T19:45:01Z | Hardware replaced, speeds normal. |
| EVT-0012 | region | 13 | false | threshold_violation | 2024-06-04T00:22:11Z | blank | REGION-613 | minor | blank | jitter | 3.8 | 14.9 | 8 | -23.5505 | -46.6333 | Traffic rerouting during peak hours | open | blank | Event ongoing, monitoring continues. |
| EVT-0013 | region | 9 | false | high_latency | 2024-06-01T10:41:19Z | 2024-06-01T11:02:12Z | REGION-418 | minor | blank | latency | 36.2 | 92.5 | 60 | 19.4326 | -99.1332 | Coverage gap during maintenance | closed | 2024-06-01T11:13:54Z | Event closed after coverage restored. |
| EVT-0014 | cell | 1 | true | user_reported_issue | 2024-06-05T16:44:45Z | blank | CELL-2293 | minor | USR-45827 | jitter | 2.6 | 14.2 | 10 | 40.4168 | -3.7038 | Account misconfiguration | investigating | blank | User escalated to L2 support. |
| EVT-0015 | backbone | 12009 | false | congestion | 2024-06-02T16:23:17Z | blank | BKB-114 | critical | blank | availability | 99.97 | 65.4 | 80 | 28.6139 | 77.209 | Power outage at data center | open | blank | Backup generators active, partial service. |
| EVT-0016 | cell | 31 | true | threshold_violation | 2024-06-04T07:09:23Z | 2024-06-04T08:44:32Z | CELL-9621 | major | USR-45828 | latency | 32.4 | 115.6 | 90 | 39.9042 | 116.4074 | Firmware bug in eNodeB | resolved | 2024-06-04T09:02:12Z | Patch deployed, latency within limits. |
| EVT-0017 | region | 41 | false | intermittent_connectivity | 2024-06-02T02:11:16Z | 2024-06-02T03:40:27Z | REGION-919 | minor | blank | availability | 99.88 | 94.2 | 97 | -1.2921 | 36.8219 | Planned maintenance window | closed | 2024-06-02T03:45:13Z | Event closed after maintenance completion. |
| EVT-0018 | site | 423 | false | slow_data_speed | 2024-06-04T18:17:59Z | 2024-06-04T18:51:21Z | SITE-9038 | major | blank | throughput | 65.9 | 3.1 | 12 | 59.9343 | 30.3351 | Unexpected traffic spike | resolved | 2024-06-04T19:11:12Z | Traffic normalized, speeds recovered. |
| EVT-0019 | site | 145 | false | high_latency | 2024-06-05T05:31:18Z | 2024-06-05T07:22:44Z | SITE-6063 | major | blank | latency | 39.4 | 183.2 | 120 | 60.1695 | 24.9354 | Routing loop in local switches | resolved | 2024-06-05T07:41:27Z | Loop resolved, latency normal. |
| EVT-0020 | site | 7241 | false | packet_loss | 2024-06-03T21:17:38Z | blank | SITE-9052 | critical | blank | packet_loss_rate | 0.02 | 0.82 | 0.2 | 55.9533 | -3.1883 | Upstream fiber link cut | open | blank | Repairs scheduled for next morning. |
What the 700 rows show
from the 700-row sampleBackbone (network segment type) stands out: mean affected_
- 35%reported_
by_ user = true - 29.5median affected_
users_ count - 3severity levels
- 4resolution statuses
- 5kpi affecteds
- 39.8median kpi_
value_ before
Median 29.5, from 0 to 14,480.
- string 10
- integer 1
- float 5
- datetime 3
- boolean 1
Columns
20 columns in four groups| column | type | description | example |
|---|---|---|---|
| Text 10 columns | |||
event_id | string | Unique identifier for each network performance degradation eventunique | EVT-0001 |
event_type | string | Type of degradation event (e.g., slow_data_speed, high_latency, packet_loss, intermittent_connectivity, congestion, threshold_violation, user_reported_issue)7 values | congestion |
network_segment_id | string | Identifier for the affected network segment (cell, site, region, etc.) | BKB-112 |
network_segment_type | string | Type of network segment (e.g., cell, site, region, backbone)cell · site · region · backbone | backbone |
severity_level | string | Severity of the event (e.g., minor, major, critical)minor · major · critical | critical |
user_report_id | string | Reference to the user report if availableoptional | USR-45823 |
kpi_affected | string | Key network performance indicator affected (e.g., throughput, latency, packet_loss_rate, jitter, availability)5 values | throughput |
root_cause | string | Identified root cause of the event if availableoptional | Upstream ISP overload |
resolution_status | string | Current status of the event resolution (e.g., open, investigating, resolved, closed)open · investigating · resolved · closed | resolved |
additional_notes | string | Additional notes or comments about the eventoptional | Device sweep scheduled. |
| Numbers 6 columns | |||
affected_users_count | integer | Number of users affected by the event0 or more · optional | 10043 |
kpi_value_before | float | Value of the affected KPI before the eventoptional | 87.2 |
kpi_value_during | float | Value of the affected KPI during the event | 6.1 |
kpi_threshold | float | Threshold value for the KPI that was violatedoptional | 15 |
location_latitude | float | Latitude of the affected network segment-90 to 90 · optional | 37.7749 |
location_longitude | float | Longitude of the affected network segment-180 to 180 · optional | -122.4194 |
| Dates and times 3 columns | |||
event_start_time | datetime | Timestamp when the degradation event started | 2024-06-03T08:14:32Z |
event_end_time | datetime | Timestamp when the degradation event endedoptional | 2024-06-03T11:56:32Z |
resolution_time | datetime | Timestamp when the event was resolvedoptional | 2024-06-03T12:08:19Z |
| True or false 1 column | |||
reported_by_user | boolean | Indicates if the event was reported by a user | false |
Use it for
A telecommunications dashboard
The reported_
by_ user rate, affected_ users_ count by network_ segment_ type and a breakdown of event_ type. Excel, Power BI or Tableau. Why do the 82 backbone rows have a mean affected_
users_ count of 12,152? A root-cause class exercise
Hand out the rows and one question. The answer is in the data, not in the brief.
- Events700EVT-000110043backboneEVT-00031siteEVT-00048943region
A software demo
Believable events with event_
type, event_ start_ time and event_ end_ time to fill a screen in front of a buyer.
This dataset700 rows20 columns
Yours1,000 rows20 columnslocation_latitude: UK only
blueprint · network-performance-degradation-and-quality-issues
Behind this dataset
Same schema. As many rows as you need.
These 700 rows came out of a blueprint — 20 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
- Degradation event ID and detection timestamp
- Issue type: slow data throughput, high latency, packet loss, intermittent disconnects
- Affected area: cell ID, region, service type
- KPI thresholds violated: e.g., latency >100ms, packet loss >1%, throughput <1Mbps
- Duration: minutes or hours of degraded performance
- User-reported issues: complaint correlation from customer care
- Root cause: network congestion, backhaul capacity, RF interference, configuration
- Impact severity: minor (few users), moderate, significant (widespread complaints)
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
- network-performance-degradation-and-quality-issues