Do I need an account with Hartford CT 311?

No. The data is public, so there is nothing to sign up for and nothing to paste in.

How fresh is the data?

As fresh as your schedule: daily by default, or weekly or monthly. Schedules as often as every 15 minutes are on the Enterprise plan.

Will running it again create duplicate rows?

No. Each row is stored once, by its key: when a run reads a row that is already there, it replaces that copy instead of adding a second one.

Do I need to write code?

No. Ingest builds, runs and maintains the connector. Someone with access to your warehouse connects it once, following a short guide.

Hartford CT 311

Public data

Ready to useNo account needed

Hartford CT 311 data, published as Hartford CT 311 publishes it. Ingest delivers this data to a data warehouse you own as one table, and updates it on the schedule you choose. There is no code to write and nothing to install.

11,800rows as of September 2026
About 230new rows a week
1 tablein your warehouse

What you get

Table Each row is

Table	Each row is
featureserver `featureserver`	Layer 9 "Service Request Current Year": Hartford 311 service requests for the current calendar year. Each run performs a full offset scan of the whole layer (11,800 rows measured via the layer's count operation on 2026-09-16) at the server's documented 2,000-record page cap and merges on the vendor's own request number USER_Record_Number, so re-runs pick up later status/address edits and deduplicate by the same request identity; requests dropped from the layer are retained in the destination. USER_Opened_Date and USER_Closed_Date are published as 'YYYY-MM-DD' strings and kept as such (USER_Closed_Date is the empty string for requests that are still open). The remaining columns are the layer's geocoder output (Match_addr, Score, DisplayX/DisplayY, ...), included as published.

featureserver

featureserver

Layer 9 "Service Request Current Year": Hartford 311 service requests for the current calendar year. Each run performs a full offset scan of the whole layer (11,800 rows measured via the layer's count operation on 2026-09-16) at the server's documented 2,000-record page cap and merges on the vendor's own request number USER_Record_Number, so re-runs pick up later status/address edits and deduplicate by the same request identity; requests dropped from the layer are retained in the destination. USER_Opened_Date and USER_Closed_Date are published as 'YYYY-MM-DD' strings and kept as such (USER_Closed_Date is the empty string for requests that are still open). The remaining columns are the layer's geocoder output (Match_addr, Score, DisplayX/DisplayY, ...), included as published.

How it works

Choose Hartford CT 311. The data is public, so there is nothing to sign in to.
Pick where it goes. BigQuery, Snowflake, Databricks, Redshift and 10 more, in an account you own.
Pick a schedule. Daily is the default, and weekly and monthly are there too.
Ingest runs it from then on. If a run fails, your dashboard shows which table and why.

Questions

Do I need an account with Hartford CT 311?: No. The data is public, so there is nothing to sign up for and nothing to paste in.
Which warehouses can Hartford CT 311 data go to?: Amazon S3, Google Cloud Storage, Azure Blob Storage, Apache Iceberg, Ingest Managed Lakehouse, MotherDuck, Postgres, Amazon Athena, Databricks, Redshift, BigQuery, ClickHouse, MySQL / generic SQL and Snowflake, in an account you own.
How fresh is the data?: As fresh as your schedule: daily by default, or weekly or monthly. Schedules as often as every 15 minutes are on the Enterprise plan.
Will running it again create duplicate rows?: No. Each row is stored once, by its key: when a run reads a row that is already there, it replaces that copy instead of adding a second one.
Do I need to write code?: No. Ingest builds, runs and maintains the connector. Someone with access to your warehouse connects it once, following a short guide.

For your data team: technical reference

Connector hartford_311, version 0.1.0, a REST source, status beta, authentication none.

Vendor documentation: https://utility.arcgis.com/usrsvcs/servers/2185af186dda46caa1e59323407d1daf/rest/services/Service_Requests_2015_to_Current/FeatureServer/9

Configuration

No configuration required.

Resources

Resource	Status	Plan	Write	Primary key	Overrides
`featureserver` Layer 9 "Service Request Current Year": Hartford 311 service requests for the current calendar year. Each run performs a full offset scan of the whole layer (11,800 rows measured via the layer's count operation on 2026-09-16) at the server's documented 2,000-record page cap and merges on the vendor's own request number USER_Record_Number, so re-runs pick up later status/address edits and deduplicate by the same request identity; requests dropped from the layer are retained in the destination. USER_Opened_Date and USER_Closed_Date are published as 'YYYY-MM-DD' strings and kept as such (USER_Closed_Date is the empty string for requests that are still open). The remaining columns are the layer's geocoder output (Match_addr, Score, DisplayX/DisplayY, ...), included as published.	beta	full	merge	`USER_Record_Number`	-

Setting up the destination is its own short guide, one per warehouse or lake: Amazon S3, Google Cloud Storage, Azure Blob Storage, Apache Iceberg, Ingest Managed Lakehouse, MotherDuck, Postgres, Amazon Athena, Databricks, Redshift, BigQuery, ClickHouse, MySQL / generic SQL, Snowflake.

Other sources Ingest connects for government teams: Abilene TX 311, Albany NY 311, Ann Arbor MI 311, Anne Arundel County MD 311, Auburn WA 311, Aurora IL 311.

Get Hartford CT 311 data into your warehouse

Last updated 2026-10-16.