Urban Sensor Uptime Monitoring

This dataset provides detailed operational uptime, alert history, and location information for urban IoT sensors deployed by city governments. It enables city managers and IT teams to monitor sensor reliability, prioritize maintenance, and support smart city resilience planning through comprehensive benchmarking and alert tracking. The dataset is ideal for infrastructure analysis, predictive maintenance, and urban technology optimization.

  • last updated 30 Dec 2025
  • by GoMask
The brief that made it

Benchmarking sensor reliability across districts and cities

Sample rows

preview · 8 of 120 rows · all 20 columns
sensor_idstringstatusstringalert_countintegerlast_alert_typestringsensor_typestringlocation_latitudefloatlocation_longitudefloatinstallation_datedatelast_maintenance_datedateuptime_percentagefloatmonitoring_period_startdatemonitoring_period_enddatelast_alert_timestampdatetimecitystringdistrictstringaddress_streetstringpostal_codestringcountrystringmanufacturerstringfirmware_versionstring
AQ-0001-NYConline1low_batteryair_quality40.7128-74.0062021-03-152024-02-2098.42024-01-012024-06-012024-04-12T10:22:33New YorkManhattan5th Avenue10001USASensAirTechv3.2.0
NO-0002-LONonline2data_anomalynoise51.5074-0.12782020-09-082023-11-3094.72024-01-012024-06-012024-05-29T14:18:55LondonWestminsterRegent StreetW1B 2ELUKNoisePro2.8.1
TR-0003-TYOonline0blanktraffic35.6895139.69172018-06-212024-01-1899.32024-01-012024-06-01blankTokyoShinjukuYasukuni Dori160-0022JapanTrafficFlowv5.1.0
WE-0004-BERonline1otherweather52.5213.4052019-11-302024-03-0397.82024-01-012024-06-012024-03-07T07:41:12BerlinMitteUnter den Linden10117GermanyWeatherWorks3.9.2
AQ-0005-SFonline0blankair_quality37.7749-122.41942023-03-20blank1002024-05-012024-06-01blankSan FranciscoMissionValencia Street94110USASensAirTechv4.0.0
NO-0006-PARmaintenance17maintenance_requirednoise48.85662.35222017-05-152022-12-2845.22024-01-012024-06-012024-02-15T15:34:20ParisMontmartreRue Lepic75018FranceNoisePro2.3.7-beta
TR-0007-MEXoffline22offlinetraffic19.4326-99.13322016-12-052023-09-1159.92024-01-012024-06-012024-02-03T10:03:45Mexico CityCentroAvenida Juárez06040MexicoTrafficFlow4.4.2
WE-0008-SYDonline2low_batteryweather-33.8688151.20932022-04-232024-02-1296.12024-01-012024-06-012024-03-20T03:12:18SydneyCBDGeorge Street2000AustraliaWeatherWorksv3.6.0

What the 120 rows show

from the 120-row sample

Offline status stands out: mean alert_count is 19.2, against 3.9 for the rest.

  • 1median alert_count
  • 5sensor types
  • 31manufacturers
  • 97.0median uptime_percentage
Mean alert_count by status120 rows
010200.81online79 rows19.2offline14 rows13.7maintena…19 rows11.5retired8 rows
alert_count120 rows, in bands of 5
0459081513125401530alert_count →

Median 1, from 0 to 27.

last_alert_type87 rows with a value · 33 left blank
  1. other25
  2. offline18
  3. maintenance_required17
  4. low_battery16
  5. data_anomaly11
20 columns by typefrom the column list below
  • string 11
  • integer 1
  • float 3
  • date 4
  • datetime 1

Columns

20 columns in three groups
blueprint · 20 columns
columntypedescriptionexample
Text 11 columns
sensor_idstringUnique identifier for each IoT sensor deviceuniqueAQ-0001-NYC
sensor_typestringType of sensor (e.g., air quality, noise, traffic, weather)air_quality · noise · traffic · weather · otherair_quality
last_alert_typestringType of the most recent alert (e.g., offline, low battery, data anomaly, maintenance required)5 values · optionallow_battery
statusstringCurrent operational status of the sensoronline · offline · maintenance · retiredonline
citystringCity where the sensor is deployedNew York
districtstringAdministrative district or neighborhood within the cityoptionalManhattan
address_streetstringStreet address of the sensor's locationoptional5th Avenue
postal_codestringPostal code of the sensor's locationoptional10001
countrystringCountry where the sensor is locatedUSA
manufacturerstringName of the sensor's manufactureroptionalSensAirTech
firmware_versionstringCurrent firmware version installed on the sensoroptionalv3.2.0
Numbers 4 columns
location_latitudefloatLatitude coordinate of the sensor's location-90 to 9040.7128
location_longitudefloatLongitude coordinate of the sensor's location-180 to 180-74.006
uptime_percentagefloatPercentage of time the sensor has been operational over the monitoring period (0-100)0 to 10098.4
alert_countintegerTotal number of operational alerts generated by the sensor during the monitoring period0 or more1
Dates and times 5 columns
installation_datedateDate the sensor was installed2021-03-15
last_maintenance_datedateDate of the most recent maintenance performed on the sensoroptional2024-02-20
monitoring_period_startdateStart date of the monitoring period for uptime calculation2024-01-01
monitoring_period_enddateEnd date of the monitoring period for uptime calculation2024-06-01
last_alert_timestampdatetimeTimestamp of the most recent alert triggered by the sensoroptional2024-04-12T10:22:33

Use it for

  • median alert c…1120 rowsmean alert count by s…0.81onli…19.2offl…13.7main…11.5reti…

    A government dashboard

    Alert_count by status and a breakdown of last_alert_type. Excel, Power BI or Tableau.

  • Why do the 14 offline rows have a mean alert_count of 19.2?

    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 sensors with sensor_type, location_latitude and location_longitude to fill a screen in front of a buyer.

Not quite right?

Make it yours.

Same 20 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 dataset120 rows20 columns
Yours1,000 rows20 columnslocation_latitude: UK only

blueprint · urban-sensor-uptime-monitoring

Behind this dataset

Same schema. As many rows as you need.

These 120 rows came out of a blueprint — 20 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
  • Logs every sensor status update (active/inactive/alert) per hour.
  • Includes sensor type, location code, and maintenance date.
  • Alerts must specify cause (power, network, hardware, external event).
  • Uptime calculated as percent per device per week.
  • Flag sensors below 95% weekly uptime for review.
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
urban-sensor-uptime-monitoring

What should your data show?

Preview 20 rows free
No signup. No card.