What does the Montgomery County MD 311 data include?

One table, service requests, with one row per service request.

Do I need an account with Montgomery County MD 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. Each run adds requests created since the last run. A request changed later, for example when it is closed, keeps the values it had when first loaded.

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.

Montgomery County MD 311

Public data

Ready to useNo account needed

Service requests from Montgomery County, Maryland's MC311 system since 2012. 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.

7.9 millionservice requests as of September 2026
About 11,000new service requests a week
1 tableone row per service request

What people use it for

Analyze multi-year trendsTrack requests across years to understand how problems have changed.
Find seasonal patternsGroup requests by when they were submitted to spot recurring issues.

What you get

Table	Each row is
Service requests `records`	One service request

Good to know

Each run adds requests created since the last run. A request changed later, for example when it is closed, keeps the values it had when first loaded.

How it works

Choose Montgomery County MD 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

What does the Montgomery County MD 311 data include?: One table, service requests, with one row per service request.
Do I need an account with Montgomery County MD 311?: No. The data is public, so there is nothing to sign up for and nothing to paste in.
Which warehouses can Montgomery County MD 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. Each run adds requests created since the last run. A request changed later, for example when it is closed, keeps the values it had when first loaded.
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 montgomerycountymd_311, version 0.1.0, a REST source, status beta, authentication none.

Vendor documentation: https://data.montgomerycountymd.gov/d/xtyh-brr2

Configuration

No configuration required.

Resources

Resource	Status	Plan	Write	Primary key	Overrides
`records` Montgomery County MC311 service requests. Incremental sync follows creation time; later edits and late-arriving rows behind the saved cursor are not refreshed. A full refresh revisits history.	beta	watermark	merge	`sr_num`	backfill_days