Sign-related 311 requests reached 42 in the seven days ending September 21, 2026, 50 percent above the prior three-week weekly average of 28.0.
San Francisco's published 311 records list 126 requests in the category MTA Parking Traffic Signs High Priority with dates from August 25 through September 21, 2026. The seven days ending September 21, 2026 carry 42 of them. The 21 days before that, August 25 through September 14, total 84, a weekly average of 28.0. The seven-day figure sits 50.0 percent above that average.
Every calendar day in the span appears at least once. The heaviest days were September 16 with 10 requests and September 15 with 9, and August 28 also recorded 9. Single-request days were August 31, September 3 and September 14. The selection matches the dataset count for that exact query, 126 of 126.
A separate city service page for reporting a parking or traffic sign issue sets out how the process is meant to work. Residents can report a speed limit, permit parking, street name, street cleaning, stop sign or other sign in need of repair, and a reporter gets a tracking number from 311. An inspection is targeted within 1 to 5 business days and repairs are to start within 30 calendar days. The page states that the city handles only signs under city jurisdiction, and that reports about private, state or federal signs are closed.
These are intake requests, not verified incidents, and duplicates or follow-up requests are possible. The records carry no response-time or outcome measurement, so the inspection and repair windows above are the city's published targets rather than a record of what happened on any request. Recent days can be revised, and the records establish no cause for the difference.
Better 311 reads public service records for San Francisco and Oakland. Sources here are the city's 311 dataset at data.sf.gov, identifier vw6y-z8j6, and its sign-reporting service page.
DataSF vw6y-z8j6: San Francisco's 311 service-request dataset on DataSF, identifier vw6y-z8j6, queried on its public API for service_name = 'MTA Parking Traffic Signs High Priority' with requested_datetime from 2026-08-25T00:00:00 through 2026-09-21T23:59:59 and grouped into daily buckets. All 28 daily buckets in that span were present and each held at least one request; the buckets sum to the full 126-record selection. Unit: one 311 intake request. The seven days ending September 21 (September 15 to 21, 42 requests) compare with the prior 21 days (August 25 to September 14, 84 requests, 28.0 per week), an increase of 50.0 percent. Checked 2026-09-22T05:33:10-07:00. Latest record 2026-09-21T19:47:31-07:00. 126 of 126 source records reviewed.
SF.gov service page: Report an issue with a parking or traffic sign: Single published City and County of San Francisco service page for reporting a parking or traffic sign problem, reviewed as a document, unit: one page, reviewed in full. Establishes the reporting channel these requests enter, the tracking number a reporter receives from 311, and the city's stated response targets: inspection within 1 to 5 business days and repairs to start within 30 calendar days. The page also states the city handles only signs under city jurisdiction and that reports about private, state or federal signs are closed. It is a published process document, not a dataset, and it carries no counts. Checked 2026-09-22T05:33:10-07:00. Latest record 2026-09-22T05:33:10-07:00. 1 of 1 source records reviewed. Evidence limits: This brief compares one service category, MTA Parking Traffic Signs High Priority, across two spans of San Francisco's 311 intake records: 42 requests in the seven days ending September 21, 2026, against 84 requests across the prior 21 days, August 25 through September 14, 2026, an average of 28.0 per week. The counts are intake requests and not verified incidents; duplicates and follow-up requests are possible. The dataset holds no response-time or outcome measurement, so the inspection and repair windows are the city's published targets for the reporting channel, not a record of what occurred on any request. Recent days can be revised as records are updated. The records establish no cause for the difference, and no cause is asserted.