Network Outage Incident Logs

This dataset provides detailed logs of network outage incidents reported by telecom providers, including timing, affected regions and services, severity, root causes, and resolution actions. It enables in-depth analysis of downtime patterns, service reliability, and operational response effectiveness, supporting both real-time monitoring and long-term reliability improvements.

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

Analyzing outage patterns to improve network reliability

Sample rows

preview · 8 of 60 rows · all 15 columns
incident_idstringdetection_methodstringduration_minutesintegerroot_causestringprovider_namestringincident_start_timedatetimeincident_end_timedatetimeaffected_regionstringaffected_servicesstringseverity_levelstringcustomers_affectedintegerincident_statusstringreported_bystringresolution_summarystringlast_updated_timedatetime
INC20240601-0001automated monitoring208hardware failureTeleNet2024-06-01T02:18:00Z2024-06-01T05:46:00ZSan Francisco, CAmobile, broadbandcritical12500resolvedsystem_monitor_01Replaced faulty router card and rebooted segment2024-06-01T06:03:00Z
INC20240601-0002customer report47power outageCommuWave2024-06-01T13:25:00Z2024-06-01T14:12:00ZHouston, TXbroadband, VoIPmajor3400closedcs_rep_0023Power restored, rerouted traffic2024-06-01T14:18:00Z
INC20240601-0003manual check39maintenanceMegaLink2024-05-30T08:03:00Z2024-05-30T08:42:00ZBrooklyn, NYmobileminor1200resolvedops_mgr_07Planned maintenance completed2024-05-30T09:00:00Z
INC20240601-0004automated monitoring55software bugTeleNet2024-05-31T22:10:00Z2024-05-31T23:05:00ZSeattle, WAbroadbandmajor4800closedsys_alert_12Patch applied to affected systems2024-06-01T00:12:00Z
INC20240601-0005manual check7maintenanceFiberZone2024-06-01T03:15:00Z2024-06-01T03:22:00ZAustin, TXbroadbandinformational0closednet_ops_04Routine check completed; no customer impact2024-06-01T03:25:00Z
INC20240601-0006customer report152fiber cutCommuWave2024-05-29T23:59:00Z2024-05-30T02:31:00ZChicago, ILmobile, VoIPmajor10200resolvedcust_svc_11Repaired fiber line; service restored2024-05-30T02:45:00Z
INC20240601-0007automated monitoring21hardware failureMegaLink2024-05-31T11:48:00Z2024-05-31T12:09:00ZQueens, NYbroadbandminor300closedsysmon_003Replaced network switch2024-05-31T12:25:00Z
INC20240601-0008automated monitoring126power outageFiberZone2024-06-01T10:29:00Z2024-06-01T12:35:00ZSanta Clara, CAmobile, broadband, VoIPcritical9300investigatingsystem_monitor_02blank2024-06-01T12:40:00Z

What the 60 rows show

from the 60-row sample

Manual check (detection method) stands out: mean duration_minutes is 19.5, against 82.7 for the rest.

  • 44.5median duration_minutes
  • 4severity levels
  • 4incident statuses
  • 8provider names
  • 8affected serviceses
  • 949median customers_affected
Mean duration_minutes by detection_method48 rows
05010081.0automated mo…24 rows19.5manual check15 rows87.2customer rep…9 rows
duration_minutes48 rows, in bands of 25
0714131473421130125225duration_minutes →

Median 44.5, from 1 to 210.

root_cause55 rows with a value · 5 left blank
  1. hardware failure18
  2. maintenance9
  3. software bug9
  4. power outage7
  5. fiber cut5
  6. scheduled maintenance2
  7. brief service interruption2
  8. core router reboot1
  9. scheduled update1
  10. core router failure1
15 columns by typefrom the column list below
  • string 10
  • integer 2
  • datetime 3

Columns

15 columns in three groups
blueprint · 15 columns
columntypedescriptionexample
Text 10 columns
incident_idstringUnique identifier for each network outage incidentuniqueINC20240601-0001
provider_namestringName of the telecom provider reporting the incident8 namesTeleNet
affected_regionstringGeographical region or area impacted by the outage (e.g., city, state, zone)San Francisco, CA
affected_servicesstringComma-separated list of services impacted (e.g., mobile, broadband, VoIP)8 servicesesmobile, broadband
severity_levelstringSeverity of the outage (e.g., critical, major, minor, informational)critical · major · minor · informationalcritical
root_causestringPrimary cause of the outage (e.g., hardware failure, software bug, power outage, maintenance)10 causes · optionalhardware failure
detection_methodstringHow the outage was detected (e.g., automated monitoring, customer report, manual check)3 methods · optionalautomated monitoring
incident_statusstringCurrent status of the incident (e.g., open, investigating, resolved, closed)open · investigating · resolved · closedresolved
reported_bystringName or identifier of the person or system that reported the incidentoptionalsystem_monitor_01
resolution_summarystringSummary of actions taken to resolve the outageoptionalReplaced network switch
Numbers 2 columns
duration_minutesintegerTotal duration of the outage in minutes0 or more · optional208
customers_affectedintegerEstimated number of customers impacted by the outage0 or more · optional12500
Dates and times 3 columns
incident_start_timedatetimeTimestamp when the outage began2024-06-01T02:18:00Z
incident_end_timedatetimeTimestamp when the outage was resolvedoptional2024-06-01T05:46:00Z
last_updated_timedatetimeTimestamp of the last update to the incident record2024-06-01T06:03:00Z

Use it for

  • median duratio…44.548 rowsmean duration minutes…81.0automa…19.5manual…87.2custom…

    A telecommunications dashboard

    Duration_minutes by detection_method and a breakdown of root_cause. Excel, Power BI or Tableau.

  • Why do the 15 manual check rows have a mean duration_minutes of 19.5?

    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 incidents with provider_name, incident_start_time and incident_end_time to fill a screen in front of a buyer.

Not quite right?

Make it yours.

Same 15 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 dataset60 rows15 columns
Yours1,000 rows15 columnsaffected_region: UK only

blueprint · network-outage-incident-logs

Behind this dataset

Same schema. As many rows as you need.

These 60 rows came out of a blueprint — 15 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
  • Incidents must have start/end times
  • Outages affecting 100+ users prioritized
  • Root cause analysis required for each outage
  • Unresolved incidents escalated after 4 hours
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
network-outage-incident-logs

More in Telecommunications

Browse all
Also in TelecommunicationsGeospatial Telecommunications Outage LogsNetwork Element Alarms and Fault ManagementNetwork Performance Degradation and Quality IssuesAll 1,966 datasets

What should your data show?

Preview 20 rows free
No signup. No card.