Telecommunications
17 columns
200 rows
8 formats

Telecom Service Outage Reports

This dataset provides detailed records of telecom service outages, including report timestamps, affected service types, location, severity, cause, and impact metrics such as customer count and area affected. Designed for network reliability analysis, it enables trend identification, root cause analysis, and operational performance monitoring for telecom providers and regulators.

last updated 12 Jul 2025
by GoMask

The brief that made it

Network reliability and downtime analysis

Sample rows

preview · 8 of 200 rows · all 17 columns

outage_report_idstring	severity_levelstring	affected_customersinteger	is_resolvedboolean	outage_causestring	reported_atdatetime	resolved_atdatetime	duration_minutesinteger	service_typestring	affected_area_km2float	citystring	statestring	postal_codestring	countrystring	network_elementstring	reported_bystring	impact_descriptionstring
OR-000001	major	12875	true	hardware failure	2024-03-01T08:34:15Z	2024-03-01T13:44:15Z	310	mobile	45.8	Houston	Texas	77002	USA	cell tower	automated system	Major mobile outage caused significant connectivity loss for thousands of users in the metro area.
OR-000002	critical	250000	false	power outage	2024-03-02T16:05:44Z	blank	blank	broadband	940.2	Manchester	Greater Manchester	M4 1LE	UK	core network	customer	Widespread broadband outage due to regional power failure; service remains unavailable.
OR-000003	minor	38	true	maintenance	2024-03-03T10:10:12Z	2024-03-03T10:41:12Z	31	landline	0.6	Zurich	Zurich	8004	Switzerland	exchange	field engineer	Brief planned maintenance affected landline service for a limited number of customers.
OR-000004	major	6000	true	software issue	2024-03-04T14:22:50Z	2024-03-04T18:10:50Z	228	tv	19.5	Melbourne	Victoria	3000	Australia	cable headend	automated system	Software glitch led to an extended TV blackout, resolved after vendor patching.
OR-000005	critical	1550000	false	unknown	2024-03-05T07:50:02Z	blank	blank	mobile	3500.4	Berlin	Berlin	10115	Germany	core network	automated system	Critical, ongoing outage with unknown root cause affecting mobile services citywide.
OR-000006	informational	0	true	maintenance	2024-03-06T11:17:23Z	2024-03-06T11:18:53Z	1	other	0.01	Oslo	Oslo	0154	Norway	small cell	field engineer	Routine test outage for new experimental service, no customer impact reported.
OR-000007	major	16000	true	weather	2024-03-06T19:25:19Z	2024-03-07T00:30:19Z	305	broadband	121	Auckland	Auckland	1010	New Zealand	fiber trunk	customer	Severe weather damaged fiber lines, causing broadband outages for several hours.
OR-000008	critical	78000	false	power outage	2024-03-07T04:14:49Z	blank	blank	tv	320.7	Lagos	Lagos	101212	Nigeria	data center	automated system	Ongoing TV signal loss due to major power outage at regional data center.
OR-000009	minor	115	true	hardware failure	2024-03-08T06:02:11Z	2024-03-08T07:32:11Z	90	broadband	2.7	Brussels	Brussels	1000	Belgium	exchange	customer	Local broadband outage traced to malfunctioning exchange, impacting a small neighborhood.
OR-000010	minor	42	true	software issue	2024-03-09T15:09:37Z	2024-03-09T16:14:37Z	65	landline	0.5	Calgary	Alberta	T2P 1J9	Canada	exchange	automated system	Minor software configuration error briefly disrupted landline calls for a handful of users.
OR-000011	informational	0	true	maintenance	2024-03-10T21:55:11Z	2024-03-10T22:00:11Z	5	tv	0.04	Cork	Munster	T12 XN72	Ireland	cable headend	field engineer	Scheduled maintenance window for TV updates; no customer-facing impact expected.
OR-000012	critical	1950000	false	hardware failure	2024-03-11T13:41:32Z	blank	blank	mobile	14400	Jakarta	DKI Jakarta	10110	Indonesia	core network	automated system	Critical hardware failure in core network; mobile customers across multiple districts are offline.
OR-000013	major	19000	true	weather	2024-03-12T18:23:08Z	2024-03-12T22:18:08Z	235	broadband	84.5	Dallas	Texas	75201	USA	fiber trunk	customer	Thunderstorms knocked out broadband service in suburban neighborhoods for several hours.
OR-000014	informational	1	true	other	2024-03-13T03:30:20Z	2024-03-13T03:32:20Z	2	other	0.02	Tallinn	Harju	10111	Estonia	small cell	other	Test event for new IoT service; negligible outage, no customer disruption.
OR-000015	critical	180000	false	unknown	2024-03-13T11:44:55Z	blank	blank	tv	2100	Buenos Aires	Buenos Aires	C1000	Argentina	cable headend	customer	TV service is currently unavailable across the region due to an unidentified issue.
OR-000016	major	12000	true	software issue	2024-03-14T08:12:20Z	2024-03-14T12:12:20Z	240	broadband	88.7	Bangalore	Karnataka	560001	India	exchange	automated system	Software bug on router cards led to broadband downtime, resolved after firmware update.
OR-000017	minor	8	true	hardware failure	2024-03-15T18:50:45Z	2024-03-15T19:10:45Z	20	landline	0.09	Helsinki	Uusimaa	00100	Finland	exchange	field engineer	Minor landline service interruption; isolated hardware issue fixed rapidly.
OR-000018	critical	31000	false	power outage	2024-03-16T06:24:17Z	blank	blank	broadband	325.1	Cape Town	Western Cape	8001	South Africa	core network	automated system	Large-scale broadband service loss due to ongoing power outage in northern sector.
OR-000019	informational	0	true	maintenance	2024-03-16T13:18:29Z	2024-03-16T13:23:29Z	5	tv	0.03	Stockholm	Stockholm	111 20	Sweden	cable headend	field engineer	Short planned interruption for TV service upgrades; customers notified in advance.
OR-000020	major	97000	true	weather	2024-03-17T09:55:57Z	2024-03-17T19:55:57Z	600	mobile	400.2	Miami	Florida	33101	USA	cell tower	automated system	Severe storms caused mobile service outages, restoration took most of the day.

What the 200 rows show

from the 200-row sample

Critical (severity level) stands out: mean affected_customers is 599,789, against 7,154 for the rest.

71%is_resolved = true
10,350median affected_customers
4reported_by values
5service types
7network elements
54countries

Mean affected_customers by severity_level200 rows

affected_customers200 rows, in bands of 250k

Median 10,350, from 0 to 2,015,000.

outage_cause200 rows · 7 values

hardware failure63
maintenance37
power outage31
unknown20
software issue17
weather16
other16

17 columns by typefrom the column list below

string 11
integer 2
float 1
datetime 2
boolean 1

Columns

17 columns in four groups

blueprint · 17 columns
column	type	description	example
Text 11 columns
`outage_report_id`	string	Unique identifier for each outage report.unique	OR-000001
`service_type`	string	Type of telecom service affected (e.g., mobile, broadband, landline).mobile · broadband · landline · tv · other	mobile
`outage_cause`	string	Primary cause of the outage (e.g., hardware failure, weather, maintenance, unknown).7 values · optional	hardware failure
`severity_level`	string	Severity of the outage (e.g., critical, major, minor, informational).critical · major · minor · informational	major
`impact_description`	string	Detailed description of the outage impact.optional	Major mobile outage cause…
`city`	string	City where the outage occurred.	Houston
`state`	string	State or region where the outage occurred.	Texas
`postal_code`	string	Postal code of the outage location.optional	77002
`country`	string	Country where the outage occurred.	USA
`network_element`	string	Specific network element affected (e.g., cell tower, exchange, data center).7 elements · optional	cell tower
`reported_by`	string	Source of the report (e.g., customer, automated system, field engineer).customer · automated system · field engineer · other · optional	automated system
Numbers 3 columns
`duration_minutes`	integer	Total duration of the outage in minutes.0 or more · optional	310
`affected_customers`	integer	Number of customers affected by the outage.0 or more · optional	12875
`affected_area_km2`	float	Estimated geographic area affected by the outage in square kilometers.0 or more · optional	45.8
Dates and times 2 columns
`reported_at`	datetime	Timestamp when the outage was reported.	2024-03-01T08:34:15Z
`resolved_at`	datetime	Timestamp when the outage was resolved.optional	2024-03-01T13:44:15Z
True or false 1 column
`is_resolved`	boolean	Indicates whether the outage has been resolved.	true

Use it for

A telecommunications dashboard
The is_resolved rate, affected_customers by severity_level and a breakdown of outage_cause. Excel, Power BI or Tableau.
Why do the 59 critical rows have a mean affected_customers of 599,789?
A root-cause class exercise
Hand out the rows and one question. The answer is in the data, not in the brief.
Outage reports200
OR-00000112875major
OR-000002250000critical
OR-00000338minor
A software demo
Believable outage reports with reported_at, resolved_at and duration_minutes to fill a screen in front of a buyer.

This dataset200 rows17 columns

Yours1,000 rows17 columnscity: UK only

blueprint · telecom-service-outage-reports

Behind this dataset

Same schema. As many rows as you need.

These 200 rows came out of a blueprint — 17 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 report includes outage type and region
Duration and number of users affected provided
Root cause categorized (hardware, software, external)
Resolution timestamp and team assigned
Optional: customer complaint count

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: telecom-service-outage-reports

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?