Baltimore street lights & signals 311 requests
Street Lights & Signals 311 requests filed in Baltimore since January 2024.
Current release
Data through April 12, 2026
Data from January 2024 through April 12, 2026
Source data: ArcGIS ↗
File a 311 request in Baltimore → This page shows historical data only.
Total Requests
26.8K
in the street lights & signals category
Latest Month
469
April 2026
Share of total
1.9%
of all Baltimore 311 requests
Median Resolution
18.6h
half of requests close faster
Monthly street lights & signals requests
How many street lights & signals 311 requests Baltimore residents file each month.
How this category is defined
What counts as street lights & signals: Broken street lights, outages, damaged signs, and malfunctioning traffic signals or pedestrian crossings.
In Baltimore’s raw 311 data, the following 2 service_type values are counted as street lights & signals:
- BGE-StLight(s) Out
- TRT-Traffic Signal Repairs
To reproduce these counts against the raw feed
SELECT count(*)
FROM <baltimore_311_raw>
WHERE service_type IN (
'BGE-StLight(s) Out',
'TRT-Traffic Signal Repairs'
)Analyst tip: Austin splits street lights ('AE Street Light Issue - Address') from traffic signals ('TPW - Traffic Signal - Maintenance') and signs ('TPW - Traffic Sign Maintenance'). Calgary uses the 'Roads -' prefix for all three. Oakland uses the terse 'ELECTRICAL' and 'TRAFFIC_ENGIN' abbreviations.
See how street lights & signals is defined for every tracked city →
Source & provenance
Counts on this page are derived from Baltimore’s official open 311 data feed, covering January 2024 through April 12, 2026. Category assignment uses an AI-generated mapping from the city’s raw service types to a normalized cross-city category. View the underlying dataset at services1.arcgis.com.