dataset · OpenDataPhilly via Carto

Philly 311 service requests

Live snapshot of the City of Philadelphia's 311 service-and-information requests, queried directly against phl.carto.com through our Cloudflare worker proxy.

data through 2026-05-13 · 5,778,572 rows

About this dataset

The City of Philadelphia's 311 service-and-information requests, hosted by the city on a public Carto SQL endpoint. Each row is one resident-filed request — noise complaints, trash issues, pothole repairs, graffiti, etc. — with timestamps, status, and (for most rows) a geocoded location.

Source

  • Catalog page: OpenDataPhilly
  • Endpoint: https://phl.carto.com/api/v2/sql?q=<SQL>
  • Table: public_cases_fc (5,778,572 rows)

How we query it

All requests go through our Cloudflare Worker proxy at /api/carto/[domain]/[table]. The proxy hashes the SQL into a KV cache key and serves repeats from KV (TTL: 24h for schema probes, 1h for aggregates, 5min for raw rows). On a fresh deploy or a cache miss the proxy forwards to Carto and writes the response back. No API key is required for public Carto datasets.

Caveats

  • Self-reported. A "noise complaint" is what the resident chose to call it; categorization drift over time.
  • Geocoded address ≠ where the noise actually came from — it's where the report was filed from.
  • closed_datetime is sometimes blank for rows the city marks as "Closed" administratively without timestamping.

Citation

City of Philadelphia (2026). 311 Service and Information Requests. Retrieved 2026-05-13 via OpenDataPhilly / Carto.