Geospatial Telecommunications Outage Logs

This dataset provides detailed, spatially-tagged logs of telecommunications network outages, restoration actions, and impact zones, enabling advanced analytics for resilience, service restoration, and risk assessment. It includes precise geolocation, event timing, affected customers, and severity, making it invaluable for operational monitoring and strategic planning.

  • last updated 21 Aug 2025
  • by GoMask
The brief that made it

Real-time outage monitoring and response optimization

Sample rows

preview · 8 of 200 rows · all 19 columns
outage_idstringoutage_causestringimpact_zone_radius_kmfloatservice_typestringnetwork_segment_idstringoutage_start_datetimedatetimeoutage_end_datetimedatetimerestoration_event_idstringrestoration_methodstringrestoration_datetimedatetimeimpact_zone_idstringimpact_zone_namestringimpact_zone_latitudefloatimpact_zone_longitudefloataffected_customers_countintegerseverity_levelstringreported_bystringoutage_descriptionstringrestoration_notesstring
OTG001equipment failure2.4broadbandNSG-A12024-05-01T07:42:13Z2024-05-01T09:23:00ZREST-01manual repair2024-05-01T11:10:34ZZONE-1001Downtown40.7128-74.006740majorautomated systemBroadband outage detected in downtown area, affecting multiple commercial and residential customers.Technicians replaced a faulty switch and restored connectivity to all affected customers.
OTG002weather0.9mobileNSG-B22024-05-01T13:18:41Z2024-05-01T15:02:19ZREST-02automated reroute2024-05-01T15:15:56ZZONE-1002Plaza34.0522-118.2437315majorautomated systemMobile service interruption due to heavy rainfall and localized flooding near Plaza.Traffic rerouted automatically and service restored.
OTG003maintenance0.7voiceNSG-C32024-05-02T06:21:08Z2024-05-02T06:24:08ZREST-03remote reset2024-05-02T06:25:50ZZONE-1053Estate51.5074-0.127812minortechnicianScheduled maintenance led to brief voice service disruption in Estate neighborhood.Routine restart completed, no customer action required.
OTG004unknown1.1fiberNSG-D42024-05-02T09:50:00ZblankblankblankblankZONE-1200Central Point35.6895139.69170blankautomated systemUnidentified outage detected at Central Point; investigation ongoing.blank
OTG005weather35.8satelliteNSG-E52024-05-03T14:32:17Z2024-05-03T17:20:00ZREST-04manual repair2024-05-03T19:09:17ZZONE-1111Valley37.7749-122.41948500criticalcustomerWide-area satellite outage reported by several customers in Valley region after severe thunderstorms.Crews deployed to repair uplink infrastructure and restore service.
OTG006maintenance1.5fiberNSG-F12024-05-03T21:04:13Z2024-05-03T21:04:14ZREST-05remote reset2024-05-03T21:05:10ZZONE-1042District48.85662.35222minortechnicianRoutine fiber maintenance in District caused a brief service interruption.System restarted remotely, connectivity restored.
OTG007equipment failure3.9mobileNSG-G22024-05-04T04:12:00Z2024-05-04T08:00:00ZREST-06manual repair2024-05-04T10:15:02ZZONE-1007City Center41.8781-87.6298654criticalautomated systemCritical mobile outage affected hundreds of users in City Center after a major hardware failure.Hardware replaced, full service restored.
OTG008weather0.8broadbandNSG-H32024-05-04T11:00:18Z2024-05-04T11:03:18ZREST-07automated reroute2024-05-04T11:05:10ZZONE-1058Plaza29.7604-95.3698100majorautomated systemShort broadband interruption at Plaza due to lightning strike.Traffic rerouted automatically.

What the 200 rows show

from the 200-row sample

Weather (outage cause) stands out: mean impact_zone_radius_km is 30.8, against 1.5 for the rest.

  • 2.0median impact_zone_radius_km
  • 3restoration methods
  • 3severity levels
  • 3reported_by values
  • 348median affected_customers_count
Mean impact_zone_radius_km by outage_cause195 rows
0204030.8weather53 rows2.4equipm…54 rows1.9cybera…19 rows0.95mainte…49 rows0.10unknown20 rows
impact_zone_radius_km195 rows, in bands of 10
07515014791312732204080impact_zone_radius_km →

Median 2.0, from 0.0 to 80.0.

service_type200 rows · 5 values
  1. broadband48
  2. mobile44
  3. fiber41
  4. satellite34
  5. voice33
19 columns by typefrom the column list below
  • string 12
  • integer 1
  • float 3
  • datetime 3

Columns

19 columns in three groups
blueprint · 19 columns
columntypedescriptionexample
Text 12 columns
outage_idstringUnique identifier for each outage eventuniqueOTG001
network_segment_idstringIdentifier for the affected network segment or assetNSG-A1
restoration_event_idstringIdentifier for the restoration event associated with the outageoptionalREST-01
restoration_methodstringMethod or process used to restore service (e.g., manual repair, automated reroute)4 values · optionalmanual repair
impact_zone_idstringIdentifier for the geographic impact zone affected by the outageoptionalZONE-1001
impact_zone_namestringHuman-readable name of the impact zone (e.g., city, neighborhood)optionalDowntown
outage_causestringPrimary cause of the outage (e.g., weather, equipment failure, cyberattack)5 values · optionalequipment failure
service_typestringType of telecommunications service affected (e.g., mobile, broadband, voice)mobile · broadband · voice · fiber · satellitebroadband
severity_levelstringSeverity level of the outage (e.g., minor, major, critical)minor · major · critical · optionalmajor
reported_bystringSource that reported the outage (e.g., automated system, customer, technician)3 values · optionalautomated system
outage_descriptionstringDetailed description of the outage eventoptionalBroadband outage detected…
restoration_notesstringAdditional notes or comments about the restoration processoptionalSystem reset remotely.
Numbers 4 columns
impact_zone_latitudefloatLatitude coordinate for the center of the impact zone-90 to 9040.7128
impact_zone_longitudefloatLongitude coordinate for the center of the impact zone-180 to 180-74.006
impact_zone_radius_kmfloatRadius of the impact zone in kilometers0 or more · optional2.4
affected_customers_countintegerNumber of customers affected by the outage0 or more · optional740
Dates and times 3 columns
outage_start_datetimedatetimeTimestamp when the outage began2024-05-01T07:42:13Z
outage_end_datetimedatetimeTimestamp when the outage was resolvedoptional2024-05-01T09:23:00Z
restoration_datetimedatetimeTimestamp when restoration actions were completedoptional2024-05-01T11:10:34Z

Use it for

  • median impact …2.0195 rowsmean impact zone radi…30.8weat…2.4equi…1.9cybe…0.95main…

    A telecommunications dashboard

    Impact_zone_radius_km by outage_cause and a breakdown of service_type. Excel, Power BI or Tableau.

  • Why do the 53 weather rows have a mean impact_zone_radius_km of 30.8?

    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 outages with network_segment_id, outage_start_datetime and outage_end_datetime to fill a screen in front of a buyer.

Not quite right?

Make it yours.

Same 19 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 rows19 columns
Yours1,000 rows19 columns

blueprint · geospatial-telecommunications-outage-logs

Behind this dataset

Same schema. As many rows as you need.

These 200 rows came out of a blueprint — 19 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
  • Outage start and end time recorded
  • Latitude and longitude of affected area
  • Outage cause classified
  • Number of users impacted estimated
  • Restoration crew assignment included
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
geospatial-telecommunications-outage-logs

What should your data show?

Preview 20 rows free
No signup. No card.