Austin 311: What the City Is Hearing About, and How Fast It Responds
Every non-emergency service request Austin residents file with the city, from potholes to code complaints, tracked from the city’s own open data, with the history Socrata itself doesn’t keep.
Live counts are unavailable right now. The tables and charts below still reflect the last successful sync.
City of Austin, all departments
Data current as of a sync that finished 58 min ago (Aug 4, 2026). Source: City of Austin Open Data Portal, dataset xwdj-i9he.
What Austin is filing 311 requests about
The most common request types in the last 90 days, with renamed and re-punctuated duplicates from twelve years of department reorganizations collapsed into one category each. Duplicate filings and cancelled/test rows are excluded.
No request data available for this window.
Is it getting fixed, and how fast
Time from filing to close, among requests opened in the last 365 days that have since closed. This measures requests that have finished, so a category with a lot of still-open, slow-moving cases will look faster here than it really is, because its slowest cases haven’t closed yet.
By request type
Not enough closed requests in this window to report response times by type.
By ZIP code(the finest geography this dataset supports; see the privacy note below)
Not enough closed requests in this window to report by ZIP.
Currently open, and how long
Every request still open or in progress right now, by how long it has been waiting.
No open requests to report.
No request type has enough of a backlog to report.
Volume over time
Requests opened and closed each month for the last 24 months. A growing gap between the two bars is a growing backlog.
No volume history available.
What changed recently
Status changes, closures and department reassignments this sync has observed. Socrata only ever shows a request’s current state; this history exists because something has been watching every day since this table was created.
No changes recorded yet.
Data & privacy
Many 311 requests are about a specific person or household, not a public asset: a noise complaint, a code officer request, a dangerous-dog investigation. Publishing those at street-address precision would make this a lookup tool for exactly the kind of complaint that shouldn’t be searchable by address.
So this page draws a line, enforced in the database rather than the page. Requests about public infrastructure, such as potholes, streetlights, traffic signals, park maintenance, trash and recycling collection, and storm drains and other public watershed work, are published at full precision, because they describe a street or a park, not a resident. Everything else, including anything about a person’s conduct or a private address, is reduced to ZIP-code precision only. The street address and coordinates for those requests are never stored in the first place, so there is no address-level lookup for this site, or any future page on it, to accidentally expose.
That is also why response time can be broken out by ZIP code but not by council district: the city’s own 311 data does not include a district field at all.
Frequently asked questions
What is Austin 311?
311 is the City of Austin's non-emergency service request line, the same system whether you call, use the app, or file online. It covers every city department that takes public requests: potholes and traffic signals (Transportation and Public Works), missed pickups (Austin Resource Recovery), code violations (Austin Code), loose or injured animals (Animal Services), noise complaints (Austin Police), and more.
How fast does the City of Austin respond to 311 requests?
Response time varies by request type and is broken out on this page. See the response-time tables for individual medians.
Why doesn’t this page show the exact address of every 311 request?
Because many 311 requests are about a specific person or household, not a public asset: a noise complaint, a code officer request, a dangerous-dog investigation. Publishing those at street-address precision would turn this into a lookup tool for exactly the kind of complaint that shouldn't be searchable by address. Requests about public infrastructure, such as potholes, streetlights, traffic signals, park maintenance, and trash and recycling collection, are shown at full precision, because they describe a street or a park, not a resident. Everything else is reported at ZIP-code precision only, at the database level, not filtered in the page.
How often is this 311 data updated?
A daily sync pulls new and updated requests from the City of Austin’s own open data portal. This page shows exactly when that last succeeded; see the freshness note near the top.
Where does this Austin 311 data come from?
Directly from the City of Austin's Open Data Portal, dataset xwdj-i9he (“Austin 311 Public Data”), which the city itself publishes and updates. Nothing here is estimated or modeled from a third party.