Congestion Data

Public congestion numbers for the U.S. urbanized areas that can apply to the federal Congestion Relief Program

The federal Congestion Relief Program funds projects only in urbanized areas of more than 1,000,000 people, and the 2020 Census counted 45. Each has a page here with its federal congestion measures, the tests the program's notice sets, and which of the numbers an application needs are public.

Applications for the Fiscal Years 2025 and 2026 Congestion Relief Program (FHWA-CRPP-27-001, up to $100 million) are due December 17, 2026, 11:59:59 p.m. Eastern, on Grants.gov.

The 45 urbanized areas

Largest first, by 2020 population. The travel time and planning time indexes are for the whole metropolitan area, from FHWA's Urban Congestion Report for July through September 2026; the notice's tests (1.07 and 1.35) apply to a project's own corridor. Delay is FHWA's annual hours of peak-hour excessive delay per person, with the latest year reported.
Urbanized areaPopulationMetro TTIMetro PTIDelay, latestAgainst the 2025 target
New York–Jersey City–Newark, NY–NJ19,426,4491.302.0121.3 (2024)Worse than target
Los Angeles–Long Beach–Anaheim, CA12,237,3761.592.4737.6 (2024)Worse than target
Chicago, IL–IN8,671,7461.362.0912.2 (2024)Better than target
Miami–Fort Lauderdale, FL6,077,5221.302.14—Not published
Houston, TX5,853,5751.322.0116.7 (2024)Better than target
Dallas–Fort Worth–Arlington, TX5,732,3541.302.0115.1 (2024)Worse than target
Philadelphia, PA–NJ–DE–MD5,696,1251.201.7012.9 (2024)Better than target
Washington–Arlington, DC–VA–MD5,174,7591.342.0917.3 (2024)Better than target
Atlanta, GA5,100,1121.322.1317.5 (2024)Better than target
Boston, MA–NH4,382,0091.271.8919.2 (2022)No target reported
Phoenix–Mesa–Scottsdale, AZ3,976,3131.161.524.6 (2024)Better than target
Detroit, MI3,776,8901.131.589.3 (2024)Better than target
Seattle–Tacoma, WA3,544,0111.352.0319.1 (2024)Better than target
San Francisco–Oakland, CA3,515,9331.372.0920.5 (2024)Worse than target
San Diego, CA3,070,3001.251.7914.3 (2024)Worse than target
Minneapolis–St. Paul, MN2,914,8661.191.653.8 (2022)No target reported
Tampa–St. Petersburg, FL2,783,0451.261.94—Not published
Denver–Aurora, CO2,686,1471.301.9612.9 (2024)Better than target
Riverside–San Bernardino, CA2,276,7031.271.8419.3 (2024)Worse than target
Baltimore, MD2,212,0381.241.9316.3 (2024)Better than target
Las Vegas–Henderson–Paradise, NV2,196,6231.171.5810.9 (2024)Better than target
St. Louis, MO–IL2,156,3231.031.276.1 (2024)Better than target
Portland, OR–WA2,104,2381.332.07—Not published
San Antonio, TX1,992,6891.181.7512.1 (2024)Better than target
Sacramento, CA1,946,6181.171.6312.1 (2024)Worse than target
Orlando, FL1,853,8961.171.66—Not published
San Juan, PR1,844,4101.332.268.2 (2024)Worse than target
San Jose, CA1,837,4461.452.1717.1 (2024)Worse than target
Austin, TX1,809,8881.321.98—Not published
Pittsburgh, PA1,745,0391.081.3910.3 (2024)Better than target
Cleveland, OH1,712,1781.051.295.6 (2024)Better than target
Indianapolis, IN1,699,8811.151.63—Not published
Cincinnati, OH–KY1,686,7441.151.666.8 (2024)Better than target
Kansas City, MO–KS1,674,2181.101.43—Not published
Columbus, OH1,567,2541.111.526.3 (2024)Better than target
Virginia Beach–Norfolk, VA1,451,5781.161.78—Not published
Charlotte, NC–SC1,379,8731.221.8614.0 (2024)Better than target
Milwaukee, WI1,306,7951.201.686.6 (2024)Better than target
Providence, RI–MA1,285,8061.131.53—Not published
Jacksonville, FL1,247,3741.111.53—Not published
Salt Lake City, UT1,178,5331.161.726.9 (2024)Better than target
Nashville-Davidson, TN1,158,6421.221.77—Not published
Raleigh, NC1,106,6461.101.50—Not published
Richmond, VA1,059,1501.061.39—Not published
Memphis, TN–MS–AR1,056,1901.121.548.0 (2024)Better than target

Also here

Method

Every figure links to where it came from and says when it was retrieved. Files carry their SHA-256, so anyone can check they have the same copy. When a number an application needs isn't public, the page says so.

The Urban Congestion Report covers 45 of the 45 areas' metropolitan areas; its indexes are for each metro's monitored roads as a whole. Travel time and planning time indexes for a project corridor come from the National Performance Management Research Data Set (NPMRDS), which state DOTs and MPOs get through RITIS. It isn't public, and its license doesn't allow publishing data sets built from it, so these pages can't show it; the corridor tool works with it on your own computer.