We publish early and update often. Spot missing information or an error? Or have a suggestion? Get in Touch →

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

311 Autonomous Vehicle Complaints

Official Dataset ↗

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

Incident Report
777
Other Feedback
163
General Complaint
39

Requests by Month

Most Recent 12 Published Months · SF311 Only

100025-1026-0126-0426-0726-09

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)
2026-09-28 · incident report · OpenSF-202000116511 ↗
2026-09-28 · incident report · OpenSF-202000116396 ↗
2026-09-28 · other · OpenSF-202000116046 ↗
2026-09-28 · other · OpenSF-202000114986 ↗
2026-09-28 · other · OpenSF-202000114361 ↗
2026-09-26 · incident report · OpenSF-202000109724 ↗
2026-09-26 · incident report · OpenSF-202000109722 ↗
2026-09-26 · other · OpenSF-202000109504 ↗
2026-09-26 · incident report · OpenSF-202000108844 ↗
2026-09-25 · incident report · OpenSF-202000106462 ↗
2026-09-25 · incident report · OpenSF-202000103401 ↗
2026-09-24 · incident report · OpenSF-202000101780 ↗
2026-09-23 · incident report · OpenSF-202000099492 ↗
2026-09-23 · other · OpenSF-202000098866 ↗
2026-09-23 · incident report · OpenSF-202000098495 ↗
2026-09-22 · incident report · OpenSF-202000096242 ↗
2026-09-22 · other · OpenSF-202000093736 ↗
2026-09-21 · incident report · ClosedSF-202000090697 ↗
2026-09-21 · incident report · ClosedSF-202000088994 ↗
2026-09-20 · incident report · ClosedSF-202000088964 ↗

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

Official City Dashboard ↗

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

110of 323 reports · 34.1%
Near Miss
41
Ignore APD Direction
29
School bus stop arm violation
26
Collision
14

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

10025-1026-0126-0426-0726-09

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

Safety Concern
104
Nuisance
54
Blocking Traffic
48
Near Miss
41
Ignore APD Direction
29
School bus stop arm violation
26
Collision
14
Safety Issue - School
5
Unspecified
2

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)
2026-09-12 · Near Miss · WaymoATX-347 ↗
2026-09-11 · Nuisance · WaymoATX-354 ↗
2026-09-09 · Nuisance · WaymoATX-355 ↗
2026-09-08 · Nuisance · WaymoATX-349 ↗
2026-09-08 · Nuisance · TeslaATX-348 ↗
2026-09-05 · Nuisance · WaymoATX-350 ↗
2026-09-02 · Near Miss · TeslaATX-345 ↗
2026-09-02 · Safety Concern · WaymoATX-340 ↗
2026-09-01 · Nuisance · WaymoATX-341 ↗
2026-08-25 · Nuisance · WaymoATX-338 ↗
2026-08-22 · Nuisance · WaymoATX-335 ↗
2026-08-19 · Nuisance · WaymoATX-337 ↗
2026-08-15 · Safety Concern · WaymoATX-336 ↗
2026-08-15 · Safety Concern · TeslaATX-326 ↗
2026-08-13 · Safety Concern · WaymoATX-328 ↗
2026-08-04 · Safety Concern · AV RideATX-329 ↗
2026-07-11 · Nuisance · WaymoATX-321 ↗
2026-06-24 · Nuisance · TeslaATX-318 ↗
2026-06-22 · Near Miss · WaymoATX-313 ↗
2026-06-14 · Nuisance · WaymoATX-299 ↗
Other City Reports by Source (173)
APD
65
City Employee
38
AFD
33
AISD Police
31
EMS
5
Unspecified
1
Recent Reports From Other City Sources
2026-09-12 · APD · Ignore APD Direction · TeslaATX-346 ↗
2026-08-13 · City Employee · Safety Concern · WaymoATX-327 ↗
2026-08-04 · City Employee · Blocking Traffic · WaymoATX-330 ↗
2026-08-02 · APD · Safety Concern · TeslaATX-325 ↗
2026-07-27 · APD · Near Miss · WaymoATX-331 ↗
2026-07-23 · APD · Blocking Traffic · WaymoATX-332 ↗
2026-07-23 · City Employee · Near Miss · WaymoATX-320 ↗
2026-06-30 · APD · Ignore APD Direction · WaymoATX-316 ↗
2026-06-23 · APD · Ignore APD Direction · TeslaATX-314 ↗
2026-06-19 · AFD · Collision · WaymoATX-315 ↗
2026-06-19 · City Employee · Nuisance · WaymoATX-308 ↗
2026-06-13 · AFD · Safety Concern · WaymoATX-307 ↗
2026-06-10 · APD · Near Miss · WaymoATX-312 ↗
2026-06-10 · City Employee · Blocking Traffic · WaymoATX-309 ↗
2026-06-02 · AFD · Safety Concern · WaymoATX-305 ↗
2026-05-28 · EMS · Ignore APD Direction · WaymoATX-297 ↗
2026-05-28 · AFD · Safety Concern · WaymoATX-296 ↗
2026-05-27 · APD · Blocking Traffic · WaymoATX-304 ↗
2026-05-24 · City Employee · Near Miss · WaymoATX-303 ↗
2026-05-16 · Unspecified · Safety Concern · WaymoATX-289 ↗

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.

AR · Northwest Arkansas

Bentonville 311 exists; no public AV-identifiable request export verified.

Official Source ↗
AZ · Phoenix

Phoenix open-data portal identified; no AV-identifiable 311 export verified.

Official Source ↗
CA · Los Angeles, San Diego, San Francisco Bay Area

LA MyLA311 open requests publish type but no AV identifier verified; other cities require separate source reviews.

Official Source ↗
CO · Denver

Denver 311 open requests identified; AV complaint classification not verified.

Official Source ↗
FL · Miami, Orlando, Tampa, Altamonte Springs, Lake Nona

Miami-Dade 311 publishes yearly requests; AV-identifiable fields not verified for these markets.

Official Source ↗
GA · Atlanta, South Metro Atlanta

ATL311 accepts requests; no AV-identifiable public request export verified.

Official Source ↗
MN · Eden Prairie, Grand Rapids

No AV-identifiable municipal 311 export verified.

Official Source ↗
NE · Nebraska trucking corridors

Documented trucking corridors do not map to a single municipal 311 jurisdiction.

Official Source ↗
NV · Las Vegas

Las Vegas open-data service requests identified; AV complaint classification not verified.

Official Source ↗
TN · Nashville

hubNashville open service requests identified; AV complaint classification not verified.

Official Source ↗
TX · Dallas, Houston, San Antonio, Fort Worth

Municipal 311 requests exist, but no validated AV-specific category or public classification has been indexed for these markets.

Official Source ↗