Bentonville 311 exists; no public AV-identifiable request export verified.
Official Source ↗Reporting / City Records
Resident Complaints
Two cities publish AV-identifiable resident reports: San Francisco’s dedicated 311 category and Austin’s city-compiled Resident Feedback. Select a city section for its own issue and time breakdown. These sources use different intake systems and cannot be compared as complaint rates.
San Francisco · AV 311 Requests
979Explore SF 311 →Austin · Resident Feedback
150Explore Austin reports →San Francisco
311 Autonomous Vehicle Complaints
Records exactly matching the city’s “Autonomous Vehicle Complaints” service category, since April 2025. Published subtypes classify the submission; the public data do not identify the operator or a detailed behavioral issue. “Incident Report” is a 311 label, not a verified collision.
City Complaint Type
SF311 service subtype · all indexed requests
Requests by Month
Most Recent 12 Published Months · SF311 Only
2025-10 to 2026-09 · 775 reports
What the Public Records Can Tell Us
These vehicles use public curb and travel lanes. Parking, double parking, bike and bus lane obstruction, blocked traffic, and stand offs are useful questions for oversight. This SF311 export does not code those behaviors or name the vehicle operator, so its subtype counts cannot answer them. The chart above counts requests, not confirmed violations. We will add issue breakdowns when a public, linkable source identifies the behavior in individual records.
Where SF AV Complaints Occur
Geocoded SF311 autonomous-vehicle requests · all available records
The heat layer shows complaint density from records with published coordinates. Individual dots are clickable and link back to the underlying SF311 record. Records without coordinates remain in citywide totals but are not shown on the map.
Recent SF Requests (979 Total)
These are public 311 requests, not verified incidents. The published subtypes describe how SF311 classified a request, not the specific behavior alleged. Operator identity is unavailable; the AV category begins in April 2025. Last source update: 2026-09-29.
Austin
Resident Feedback on AVs
Austin Transportation and Public Works publishes 323 substantive AV reports. 150 are labeled “Resident Feedback”; these are the only records counted here as citizen reports. The remaining 173 include police, fire, school police, EMS, and other city reports. The source also contains 1 empty placeholder, excluded from the totals. The city says its log draws partly from 311; it does not say that every resident entry came through 311.
Higher-Severity Reports
Collisions, near misses, school-bus stop-arm violations, and ignored APD direction · all city sources
This is an analytical subset of Austin’s report categories, not a city severity classification. Reports are allegations/observations, not adjudicated findings.
Resident Feedback by Month
Most Recent 12 Months With Feedback · Austin Residents Only
2025-10 to 2026-09 · 75 reports
Public Right of Way
Austin labels 15 resident reports “Blocking Traffic” and 33 other city reports that way. Its broader “Nuisance” category covers 47 resident reports. Together these flags show where AV operation affects shared streets, but they do not independently establish double parking, bike or bus lane obstruction, or an unsafe stop. “Near Miss” and “Safety Concern” are also allegations, not adjudicated findings. The all-source issue chart below combines resident and department reports into one citywide total.
Reported Issues
City-defined issue categories across all 323 substantive reports · all reporting sources combined
Counts combine resident feedback, police, fire, EMS, school police, city employees, and other city records. Source type is not used to split the chart.
Recent Austin Resident Reports (150 Total)
Other City Reports by Source (173)
Recent Reports From Other City Sources
Austin compiles unvalidated reports received from residents, City departments, and other sources, including 311. The Resident Feedback label does not prove every record entered via 311. This series differs from San Francisco's dedicated 311 AV category and their raw counts should not be compared as rates. Public narrative and precise location are omitted from Observatory exports. Most recent incident date: 2026-09-12.
Coverage in Other Deployment Markets
Missing public AV-identifiable data are coverage gaps, not zero complaints.
Phoenix open-data portal identified; no AV-identifiable 311 export verified.
Official Source ↗LA MyLA311 open requests publish type but no AV identifier verified; other cities require separate source reviews.
Official Source ↗Denver 311 open requests identified; AV complaint classification not verified.
Official Source ↗Miami-Dade 311 publishes yearly requests; AV-identifiable fields not verified for these markets.
Official Source ↗ATL311 accepts requests; no AV-identifiable public request export verified.
Official Source ↗No AV-identifiable municipal 311 export verified.
Official Source ↗Documented trucking corridors do not map to a single municipal 311 jurisdiction.
Official Source ↗Las Vegas open-data service requests identified; AV complaint classification not verified.
Official Source ↗hubNashville open service requests identified; AV complaint classification not verified.
Official Source ↗Municipal 311 requests exist, but no validated AV-specific category or public classification has been indexed for these markets.
Official Source ↗