Smart City Technology Failure Logs

This dataset provides granular logs of smart city technology failures, including device details, failure types, geolocation, severity, resolution status, and downtime. It enables city planners and technologists to monitor infrastructure health, prioritize maintenance, analyze root causes, and enhance urban resilience through data-driven decision making.

  • last updated 13 Jan 2026
  • by GoMask
The brief that made it

Prioritizing urban technology maintenance and repairs

Sample rows

preview · 8 of 127 rows · all 23 columns
failure_idstringdevice_typestringdowntime_minutesintegermaintenance_team_idstringdevice_idstringsystem_namestringfailure_datetimedatetimefailure_typestringfailure_severitystringlocation_street_addressstringlocation_citystringlocation_statestringlocation_postal_codestringlocation_countrystringlatitudefloatlongitudefloatreported_bystringresolution_statusstringresolution_datetimedatetimeaffected_servicesstringfailure_descriptionstringresolution_descriptionstringroot_causestring
SIG-4912_Rtraffic_signal322MT-02SIG-4821SmartTraffic2024-05-14T09:17:00Zpowercritical1520 Main StDallasTX75201USA32.7792-96.8008system_alertresolved2024-05-14T14:39:00Ztraffic_management, emergency_servicesCitywide traffic signal outage due to transformer malfunction during morning rush hour.Replaced faulty transformer and restored power to the intersection.Transformer short-circuit caused widespread device failure.
CAM-X8325Biot_camera48blankCAM-8325CityWatch2024-04-18T20:04:00Zconnectivityminor930 Border AveTijuanaBCN22010Mexico32.5252-117.0362operator_cam02openblankborder_surveillance, securityBorder surveillance camera intermittently lost connection to the network.blankblank
SS-7918_Xsmart_sensor1109MT-07SS-7918EnviroNet2024-03-23T13:56:00Zhardwaremajor298 King StNewcastleNSW2300Australia-32.9267151.7817system_alertresolved2024-03-24T09:15:00Zair_quality_monitoring, public_healthAir quality smart sensor reported abnormally high PM2.5 readings due to sensor miscalibration.Recalibrated air quality sensor and verified correct readings.Sensor miscalibration following firmware update.
EM-4039_Uenvironmental_monitor0blankEM-4039AquaTrack2024-06-01T03:48:00Zenvironmentalinformational17 Fjord RdLongyearbyenSvalbard9170Norway78.223215.6469system_auto_checkclosed2024-06-01T04:03:00Zwater_quality, environmental_monitoringRemote water quality monitor detected temporary turbidity spike due to rainfall.No action needed, readings normalized after precipitation event.Heavy rainfall caused temporary water turbidity spike.
LC-9823C_Tlighting_controller141MT-05LC-9823LightCity2024-04-11T18:24:00Zsoftwaremajor48 Rue Saint-PaulMontrealQCH2Y 1H2Canada45.5088-73.5617operator_lc03resolved2024-04-11T20:45:00Zstreet_lighting, public_safetyLighting controller failed to update schedule, resulting in street lights remaining off after sunset.Controller firmware was rolled back and schedule applied.Software bug in latest controller release.
OTH-3091-Dother19blankOTH-3091GreenNet2024-05-30T11:21:00Zunknownminor6122 Oak LaneBirminghamENGB20 2HTUK52.4862-1.8904operator_miscin_progressblankpark_monitoringUnclassified device failed to report status during scheduled polling.blankblank
SIG-4987_Ltraffic_signal325MT-04SIG-4987SmartTraffic2024-05-21T15:34:00Zhardwarecritical8431 Elm StLondonENGW1A 6USUK51.5074-0.1278system_alertresolved2024-05-21T20:59:00Ztraffic_management, emergency_servicesIntersection signal failed due to damaged relay, causing major traffic delays.Relay replaced and traffic signal tested for correct operation.Relay burned out due to excess voltage.
CAM-9145Eiot_camera62blankCAM-9145CityWatch2024-06-03T07:27:00Zsoftwareminor1129 Mission StSan FranciscoCA94103USA37.7749-122.4194operator_cam04openblanksecurity, surveillanceCamera firmware update failed, causing video stream interruptions.blankblank

What the 127 rows show

from the 127-row sample

Smart_sensor (device type) stands out: mean downtime_minutes is 587.1, against 147.8 for the rest.

  • 120median downtime_minutes
  • 4failure severities
  • 4resolution statuses
  • 6failure types
  • 8system names
  • 18location countries
Mean downtime_minutes by device_type127 rows
0400800587.1smart…22 rows43.3iot_c…27 rows352.2traff…24 rows0.0envir…20 rows228.3light…25 rows20.6other9 rows
downtime_minutes127 rows, in bands of 200
040807332114222108001,600downtime_minutes →

Median 120, from 0 to 1,420.

maintenance_team_id71 rows with a value · 56 left blank
  1. MT-019
  2. MT-028
  3. MT-058
  4. MT-068
  5. MT-077
  6. MT-087
  7. MT-037
  8. MT-046
  9. MT-096
  10. MT-105
23 columns by typefrom the column list below
  • string 18
  • integer 1
  • float 2
  • datetime 2

Columns

23 columns in three groups
blueprint · 23 columns
columntypedescriptionexample
Text 18 columns
failure_idstringUnique identifier for each technology failure eventuniqueSIG-4912_R
device_idstringUnique identifier for the device or sensor that failedSIG-4821
device_typestringType of device (e.g., smart sensor, IoT camera, traffic signal)6 valuestraffic_signal
system_namestringName of the connected system or platform the device belongs to8 namesSmartTraffic
failure_typestringCategory of failure (e.g., hardware, software, connectivity, power)6 valuespower
failure_severitystringSeverity level of the failurecritical · major · minor · informationalcritical
failure_descriptionstringDetailed description of the failure eventoptionalCitywide traffic signal o…
location_street_addressstringStreet address where the failure occurredoptional1520 Main St
location_citystringCity where the failure occurredDallas
location_statestringState or region where the failure occurredTX
location_postal_codestringPostal code of the failure locationoptional75201
location_countrystringCountry of the failure locationUSA
reported_bystringName or identifier of the person/system that reported the failureoptionalsystem_alert
maintenance_team_idstringIdentifier for the maintenance team assigned to resolve the failure10 teams · optionalMT-02
resolution_statusstringCurrent status of the failure resolutionopen · in_progress · resolved · closed · escalatedresolved
resolution_descriptionstringDetails about how the failure was resolvedoptionalReplaced faulty transform…
root_causestringIdentified root cause of the failureoptionalSeasonal glacier runoff.
affected_servicesstringComma-separated list of city services impacted by the failureoptionalpark_monitoring
Numbers 3 columns
latitudefloatLatitude coordinate of the failure location-90 to 90 · optional32.7792
longitudefloatLongitude coordinate of the failure location-180 to 180 · optional-96.8008
downtime_minutesintegerTotal downtime in minutes caused by the failure0 or more · optional322
Dates and times 2 columns
failure_datetimedatetimeDate and time when the failure was detected2024-05-14T09:17:00Z
resolution_datetimedatetimeDate and time when the failure was resolvedoptional2024-05-14T14:39:00Z

Use it for

  • median downtim…120127 rowsmean downtime minutes…587.1smar…43.3iot_…352.2traf…0.0envi…

    A technology dashboard

    Downtime_minutes by device_type and a breakdown of maintenance_team_id. Excel, Power BI or Tableau.

  • Why do the 22 smart_sensor rows have a mean downtime_minutes of 587.1?

    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 failures with device_id, device_type and system_name to fill a screen in front of a buyer.

Not quite right?

Make it yours.

Same 23 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 dataset127 rows23 columns
Yours1,000 rows23 columnslocation_street_address: UK only

blueprint · smart-city-technology-failure-logs

Behind this dataset

Same schema. As many rows as you need.

These 127 rows came out of a blueprint — 23 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 row represents a unique failure event logged by a city system.
  • Includes device type, location, time to resolution, and impact assessment.
  • Events must be categorized by failure reason (e.g., power, connectivity, hardware).
  • Resolution actions and responsible department must be logged.
  • No two events share identical timestamp and device ID.
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
smart-city-technology-failure-logs

What should your data show?

Preview 20 rows free
No signup. No card.