← Back to all datasets
phone 311 Service Requests πŸ›οΈ Houston 311 Customer Service stale

Houston 311 Service Requests

Every non-emergency request residents file with the City of Houston: potholes, missed trash, dead animals, water leaks, and more.

πŸ—‚οΈ
300
Records
🚩
20
Red flags
βœ…
80
Quality score
πŸ”„
daily
Update frequency

Data Detective

Tip

Scan the map for red dots and check the chart for spikes. Big jumps or drops are usually where the interesting questions live.

Source: The numbers above come straight from Houston Open Data.

πŸ“ Data quality breakdown

How healthy is this dataset across five dimensions?

Completeness 94/100
Freshness 15/100
Location 99/100
Consistency 91/100
Usefulness 100/100

πŸ—ΊοΈ Where the data lives

Up to 300 geolocated records. Red markers are flagged values.

πŸ“ˆ Activity over time

Record volume by month, or by status when no dates exist.

🚩 Open red flags

Suspicious values our scanner caught β€” see if you agree.

🚩 High · future date
95% sure

This record is dated in the future.

occurred_at 2026-07-28
A 311 request can't be created next year. A future date usually means someone typed the date wrong or a computer formatted it incorrectly.

Next step: Check for a typo or a time-zone/format bug at the source.

Houston 311 Service Requests Source β†—
🚩 High · future date
95% sure

This record is dated in the future.

occurred_at 2026-07-06
A 311 request can't be created next year. A future date usually means someone typed the date wrong or a computer formatted it incorrectly.

Next step: Check for a typo or a time-zone/format bug at the source.

Houston 311 Service Requests Source β†—
🚩 High · future date
95% sure

This record is dated in the future.

occurred_at 2026-06-27
A 311 request can't be created next year. A future date usually means someone typed the date wrong or a computer formatted it incorrectly.

Next step: Check for a typo or a time-zone/format bug at the source.

Houston 311 Service Requests Source β†—
🚩 High · impossible negative
85% sure

A count or amount is negative where that should be impossible.

numeric_value -12
You can't have negative days to fix a pothole, or negative permits. A negative number here is a sign of a data-entry or calculation mistake.

Next step: Confirm whether negatives represent refunds/corrections or are simply errors.

Houston 311 Service Requests Source β†—
🚩 High · impossible negative
85% sure

A count or amount is negative where that should be impossible.

numeric_value -40
You can't have negative days to fix a pothole, or negative permits. A negative number here is a sign of a data-entry or calculation mistake.

Next step: Confirm whether negatives represent refunds/corrections or are simply errors.

Houston 311 Service Requests Source β†—
🚩 High · impossible negative
85% sure

A count or amount is negative where that should be impossible.

numeric_value -12
You can't have negative days to fix a pothole, or negative permits. A negative number here is a sign of a data-entry or calculation mistake.

Next step: Confirm whether negatives represent refunds/corrections or are simply errors.

Houston 311 Service Requests Source β†—
🚩 High · stale dataset
80% sure

Expected updates every daily, but it has been 75 days, 12 hours.

last_source_update 2026-04-03
A dataset that's supposed to refresh daily but hasn't in 75 days, 12 hours is like a bus schedule nobody updated β€” you can't trust it to reflect what's happening now.

Next step: Ask the department whether updates stopped or moved elsewhere.

Houston 311 Service Requests Source β†—
🚩 Medium · missing value
90% sure

The field "reported_by" is empty in 33% of records.

reported_by 33% empty
Think of a class roster where most students never filled in their phone number. If "reported_by" is blank 33% of the time, we can't trust any total or map that depends on it.

Next step: Ask the owning department why this field is so often blank.

Houston 311 Service Requests Source β†—

⚠️ Known issues

  • β€’Some requests lack coordinates
  • β€’Status values are not always standardized

πŸ’‘ Public use cases

  • β€’Track how fast your neighborhood requests get closed
  • β€’Compare service levels across ZIP codes
  • β€’Spot service deserts

πŸ“ Geo fields

latitude longitude zip

πŸ•’ Time fields

created_date closed_date

Records: 300

Update frequency: daily

Last imported: 23 hours ago

Search the Houston Open Data catalog β†—