Telecom Call Drop Diagnostics

This dataset provides granular call records with comprehensive diagnostics for both dropped and completed calls, including network, device, and quality-of-service metrics. It enables telecom operators and analysts to perform in-depth troubleshooting, root cause analysis, and QoS optimization across networks and geographies. The data is ideal for identifying patterns in call drops, evaluating network performance, and improving customer experience.

  • opened 6 times
  • last updated 12 Jul 2025
  • by GoMask
The brief that made it

Root cause analysis of call drops and network failures

Sample rows

preview · 8 of 200 rows · all 24 columns
call_idstringcall_statusstringlatency_msfloatroamingbooleandrop_reason_codestringcaller_numberstringcallee_numberstringcall_start_timedatetimecall_end_timedatetimecall_duration_secondsintegerdrop_reason_descriptionstringnetwork_typestringsignal_strength_dbmfloatcell_idstringlocation_latitudefloatlocation_longitudefloatdevice_manufacturerstringdevice_modelstringos_versionstringqos_mosfloatpacket_loss_percentfloatjitter_msfloathandover_countintegersim_operatorstring
C00001completed18falseblank+14155550101+4420712345672023-10-12T14:11:23Z2023-10-12T14:21:53Z630blank5G-48.3NYC_CELL_10140.7128-74.006AppleiPhone 14 ProiOS 16.44.920.12.32AT&T
C00002dropped131falseNW_TIMEOUT+33123456789+49151234567892023-11-01T09:33:41Z2023-11-01T09:36:21Z160Network timeout during call4G-81.6PAR_CELL_20448.85662.3522SamsungGalaxy S21Android 133.187.947.11Orange
C00003failed687trueblank+81312345678+8210123456782023-09-27T20:04:12Zblank0blank3G-122.7TYO_CELL_08735.6895139.6917Nokia3310S30+1.0632.2142.80SK Telecom
C00004busy9falseblank+61291234567+120255512342023-07-19T13:48:40Zblank0blankVoLTE-58.4SYD_CELL_003-33.8688151.2093GooglePixel 7Android 134.700.50Telstra
C00005dropped309trueSIG_LOSS+911123456789+86138123456782023-08-06T16:28:05Z2023-08-06T16:31:20Z195Signal lost during handover2G-133.9DEL_CELL_02128.613977.209TecnoSpark 6Android 82.1219.481.71China Mobile
C00006completed11falseblank+5511998765432+349112345672023-04-23T18:49:19Z2023-04-23T18:59:30Z611blankWiFi-33.7SAO_CELL_034-23.5505-46.6333SonyXperia 5 IVAndroid 124.880.21.82Claro
C00007completed15falseblank+498912345678+331423456782023-12-03T22:13:15Z2023-12-03T22:23:43Z628blank5G-52.5MUC_CELL_06748.135111.582SamsungGalaxy S23Android 144.97013Vodafone DE
C00008failed1152trueblank+8613800138000+813123456792023-09-15T08:41:12Zblank0blank2G-146.8BJS_CELL_11939.9042116.4074AlcatelOneTouchKaiOS 2.51.0241.6188.20NTT Docomo

What the 200 rows show

from the 200-row sample

Failed (call status) stands out: mean latency_ms is 1,553, against 156.8 for the rest.

  • 38%roaming = true
  • 18.7median latency_ms
  • 6network types
  • 13device manufacturers
  • 33os versions
  • 267.5median call_duration_seconds
Mean latency_ms by call_status200 rows
01,0002,00012.9completed103 rows510.1dropped46 rows1,553failed22 rows107.6busy29 rows
latency_ms200 rows, in bands of 200
0701401402171531571001,0002,000latency_ms →

Median 18.7, from 5.2 to 2,000.

drop_reason_code46 rows with a value · 154 left blank
  1. CALL_DROP4
  2. CALL_FAIL3
  3. NW_CONGEST3
  4. LNK_FAIL3
  5. NR_LOST3
  6. NW_TIMEOUT2
  7. SIG_LOSS2
  8. RADIO_INT2
  9. LOW_QOS2
  10. SRV_LOST2
24 columns by typefrom the column list below
  • string 12
  • integer 2
  • float 7
  • datetime 2
  • boolean 1

Columns

24 columns in four groups
blueprint · 24 columns
columntypedescriptionexample
Text 12 columns
call_idstringUnique identifier for each call record.uniqueC00001
caller_numberstringPhone number of the caller (E.164 format).+14155550101
callee_numberstringPhone number of the recipient (E.164 format).+442071234567
call_statusstringStatus of the call: completed, dropped, failed, or busy.completed · dropped · failed · busycompleted
drop_reason_codestringStandardized code indicating the reason for call drop (if applicable).optionalNW_TIMEOUT
drop_reason_descriptionstringHuman-readable description of the call drop reason.optionalRadio interface failure
network_typestringType of network used for the call (e.g., 2G, 3G, 4G, 5G, VoLTE, WiFi).6 values5G
cell_idstringIdentifier of the cell tower handling the call.NYC_CELL_101
device_manufacturerstringManufacturer of the caller's device.optionalApple
device_modelstringModel of the caller's device.optionaliPhone 14 Pro
os_versionstringOperating system version of the caller's device.optionaliOS 16.4
sim_operatorstringMobile network operator of the caller's SIM card.optionalAT&T
Numbers 9 columns
call_duration_secondsintegerDuration of the call in seconds.0 or more630
signal_strength_dbmfloatSignal strength in dBm at the time of the call.-150 to 0 · optional-48.3
location_latitudefloatLatitude of the caller's location at call start.-90 to 90 · optional40.7128
location_longitudefloatLongitude of the caller's location at call start.-180 to 180 · optional-74.006
qos_mosfloatMean Opinion Score (MOS) for call quality (1.0 to 5.0).1 to 5 · optional4.92
packet_loss_percentfloatPercentage of packet loss during the call.0 to 100 · optional0.1
jitter_msfloatJitter measured in milliseconds during the call.0 or more · optional2.3
latency_msfloatNetwork latency in milliseconds during the call.0 or more · optional18
handover_countintegerNumber of network handovers during the call.0 or more · optional2
Dates and times 2 columns
call_start_timedatetimeTimestamp when the call started.2023-10-12T14:11:23Z
call_end_timedatetimeTimestamp when the call ended.optional2023-10-12T14:21:53Z
True or false 1 column
roamingbooleanIndicates if the caller was roaming during the call.optionalfalse

Use it for

  • roaming38%76 of 200 rowsmean latency ms by ca…12.9comp…510.1drop…1.6kfail…107.6busy

    A telecommunications dashboard

    The roaming rate, latency_ms by call_status and a breakdown of drop_reason_code. Excel, Power BI or Tableau.

  • Why do the 22 failed rows have a mean latency_ms of 1,553?

    A root-cause class exercise

    Hand out the rows and one question. The answer is in the data, not in the brief.

  • A software demo

    Believable calls with caller_number, callee_number and call_start_time to fill a screen in front of a buyer.

Not quite right?

Make it yours.

Same 24 columns, your size and your rules. See 20 rows before you pay.

Preview 20 rows free

1,000 rows: $1.99 · 10,000: $12.99One-time. No subscription. All prices

This dataset200 rows24 columns
Yours1,000 rows24 columnslocation_latitude: UK only

blueprint · telecom-call-drop-diagnostics

Behind this dataset

Same schema. As many rows as you need.

These 200 rows came out of a blueprint — 24 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
  • Each call logs duration, start/end location
  • Diagnostics: signal strength, network type, handover events
  • Dropped calls include reason codes
  • User device anonymized
  • Peak/off-peak time flagged
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
telecom-call-drop-diagnostics

What should your data show?

Preview 20 rows free
No signup. No card.