Data Center Corridor Air Monitoring
DEQ describes the goal of the project as an exploratory trend analysis of the sensor measurements, meant to establish whether areas with high numbers of data centers need additional regulatory air monitoring (DEQ staff, correspondence, 2026-08-16). The network exists to answer that question. It was not built to measure compliance, and most misreadings of these numbers start by treating it as though it were.
This page presents Virginia DEQ's Data Center Air Monitoring Project measurements for Loudoun County, March to August 2026, alongside the regulatory reference monitor collocated at one sensor site. The sensors are not regulatory instruments, and DEQ's statement of that limitation appears below, before any measurement does. Almost every hour in the record sits below the level of the federal standards, and the highest values coincide with a wildfire smoke episode that reached Virginia from roughly 1,500 miles away. What follows describes what was measured and where; it does not establish what produced any of the values, and no health data appears on this page.
DEQ's limitation statement · Full limitations · Data and methods
What DEQ says about this data
Quoted verbatim from Virginia DEQ
Important: This information is published as soon as the values are detected, and does not imply that the data have passed quality assurance validation procedures.
The sensors displayed on this page are not regulatory instruments as specified in the Code of Federal Regulations (CFR), that is, they cannot be used in determining attainment or non-attainment of the National Ambient Air Quality Standards (NAAQS). Only Federal Reference/Equivalent Method designed monitors can. However, they are still useful to get a general idea of pollutant trends and general concentrations.
These sensors are capable of collecting pollutant concentration data and establishing pollutant concentration trends, but they are not regulatory instruments as specified in the Code of Federal Regulations (CFR). They cannot be used in determining attainment or non-attainment of the National Ambient Air Quality Standards (NAAQS). Only Federal Reference/Equivalent Method designated monitors can.
GENARCH's own wording, from here on
A single hourly reading above 35 µg/m³ is not measured against the 24-hour PM2.5 standard and does not by itself show that the standard has been surpassed. The regulatory form of that standard is the 98th percentile of daily 24-hour averages, averaged over three consecutive years. The separate annual standard is 9.0 µg/m³, as revised in 2024. DEQ's published analysis makes the same point about hourly values.
Sensor measurements come from the public Kunak Cloud export, by the download method DEQ staff confirmed on 2026-08-10, and are redistributable with credit to Virginia DEQ. Regulatory monitor measurements were released under Virginia FOIA request 26-4646 on 2026-08-11, in full, and are public at vadeq.nextrequest.com/requests/26-4646.
Where the sensors sit
DEQ identified 22 potential locations in Loudoun County and has deployed seven sensors so far, two of which have been relocated once each. The network measures where it sits, and a finding drawn from these six records describes those six locations rather than the corridor as a whole. DEQ's wind rose analysis in its August 7 report concludes that the collocated Ashburn site and the Dulles-area site are good upwind reference locations relative to the corridor.
Sensors are identified here by DEQ site identifier and locality rather than by DEQ's published site label. Four of the nine locations are hosted at schools, and placing a school name beside a concentration figure invites an inference about children at that school that nothing in this data supports. The identifier crosswalk in section 9 maps every identifier to DEQ's exact published label, so this page can still be checked against DEQ's report.
Three of the nine site records are not reachable through the public dashboard, which shows those locations without a device. Their historical measurements are not downloadable, so they carry no series anywhere on this page. Three absent site records are not the same thing as no data at those locations.
| Site | Area | Unit | Occupancy | Status | Valid hours | Collocated |
|---|---|---|---|---|---|---|
| ashburn-collocated | Ashburn | APEX 14, APEX 5 | 2026-03-03 to present | Collecting | 3,695 | Yes |
| belfort-park | Sterling | APEX 14 | 2026-05-14 to present | Collecting | 2,092 | No |
| dulles-area | Sterling | not confirmed | 2026-03-03 to present | Collecting | 3,610 | No |
| farmwell-middle | Ashburn | not confirmed | 2026-04-08 to present | Collecting | 2,961 | No |
| golf-course | Ashburn | not confirmed | 2026-04-08 to present | Collecting | 2,973 | No |
| heritage-farm | Sterling | not confirmed | 2026-03-03 to 2026-06-18 | No export available | — | No |
| newberry-condo | Sterling | APEX 14 | 2026-03-03 to 2026-05-14 | No export available | — | No |
| sterling-ms | Sterling | APEX 6 | 2026-06-18 to present | Collecting | 1,282 | No |
| steuart-weller | Ashburn | APEX 6 | 2026-03-03 to 2026-06-18 | No export available | — | No |
Occupancy windows and hardware unit assignments come from DEQ's site history. One site shows two units because the hardware was swapped in place on 2026-04-08; those two deployments are treated separately throughout. 3 sites carry no valid-hour count because no export exists for them: heritage-farm, newberry-condo, steuart-weller. Sensor coordinates are not published in machine-readable form, so no map is drawn here.
Hourly PM2.5, sensors and regulatory monitor
Hourly PM2.5 by site
Show per-site summary, with and without the smoke-transport window
| Site | Class | Hours | Mean µg/m³ | Max µg/m³ | Hours excl. smoke | Mean excl. smoke | Max excl. smoke |
|---|---|---|---|---|---|---|---|
| ashburn-collocated (Ashburn) | Sensor | 3,695 | 8.09 | 123.11 | 3,599 | 7.12 | 34.04 |
| belfort-park (Sterling) | Sensor | 2,092 | 9.24 | 132.18 | 1,996 | 7.46 | 37.17 |
| dulles-area (Sterling) | Sensor | 3,610 | 5.62 | 114.71 | 3,514 | 4.77 | 33.54 |
| farmwell-middle (Ashburn) | Sensor | 2,961 | 8.01 | 157.91 | 2,865 | 6.56 | 48.07 |
| golf-course (Ashburn) | Sensor | 2,973 | 7.48 | 119.76 | 2,877 | 6.18 | 38.48 |
| sterling-ms (Sterling) | Sensor | 1,282 | 11.21 | 149.53 | 1,186 | 8.40 | 37.91 |
| ashburn regulatory monitor (Ashburn) | Regulatory | 3,040 | 8.44 | 282.50 | 2,944 | 6.46 | 28.50 |
Every summary figure near this chart is given twice, once over the whole record and once with 2026-07-16 to 2026-07-19 removed. A statistic pooled across the smoke episode and ordinary conditions sits between two regimes and describes neither. At the regulatory monitor the mean over the full record is 8.44 µg/m³ across 3,040 valid hours, and 6.46 µg/m³ across 2,944 hours with the smoke window removed. The highest single hour in the whole record, 282.5 µg/m³, falls inside that window; outside it the highest hour is 28.5 µg/m³.
Four separate periods are voided in the source data, and the chart shows each as a gap. DEQ's August 7 report records regulatory PM2.5 voided 2026-05-07 to 05-10 and 2026-06-16 to 07-14 for failed data quality analysis and instrumentation issues, regulatory NO2 voided 2026-05-07 to 05-10, sensor PM2.5 voided 2026-03-03 to 03-08 at every site for high humidity and sensor data quality, and PM2.5 collection at one retired site ending 2026-05-30 after an air flow failure in the particle sensor. In the released record the fully void days are narrower than the stated windows, 05-08 to 05-09 and 06-17 to 07-13, because the days at each boundary are partly valid.
Sensor against regulatory monitor at the collocated site
DEQ operates one sensor at the same location as its regulatory reference monitor, and has published a regression between the two every week since the project began. Two different hardware units have occupied that position: APEX 14 from 2026-03-03 to 2026-04-08 and APEX 5 from 2026-04-08 onward. They are treated separately throughout, since pooling two instruments into one regression describes neither.
The table sets DEQ's coefficients beside coefficients computed by GENARCH's pipeline from the source tables. This is a verification of that pipeline against an authoritative source, not a new result: DEQ published the analysis first and publishes it on a weekly cycle.
| Comparison | DEQ | GENARCH | n |
|---|---|---|---|
| APEX 14 PM2.5 | y = 1.3 + 0.83x, R² = 0.73 | y = 1.299 + 0.831x, R² = 0.725 | 697 |
| APEX 5 PM2.5 | y = -4.7 + 1.7x, R² = 0.84 | y = -4.678 + 1.665x, R² = 0.837 | 2,111 |
| APEX 14 NO2 | y = 2.2 + 1.1x, R² = 0.49 | y = 2.186 + 1.075x, R² = 0.497 | 589 |
| APEX 5 NO2 | y = 1.8 + 0.32x, R² = 0.21 corrected by DEQ; see the note below the table | y = 1.835 + 0.319x, R² = 0.207 | 2,745 |
APEX 5 NO2: the August 7, 2026 edition published y = 1.9 + 0.29x, R² = 0.17. DEQ later corrected that fit, and the August 21, 2026 edition prints the corrected form at y = 1.8 + 0.31x, R² = 0.2 over that edition's longer record (Virginia DEQ, Office of Air Quality Monitoring, "Data Center Air Quality Analysis", August 21, 2026). The column above holds the corrected fit over the August 7, 2026 window instead, because that is the window the GENARCH column is computed on. DEQ supplied those coefficients by correspondence on 2026-08-19.
The DEQ column is the August 7 edition apart from the daggered row, and the GENARCH column stops at 2026-08-07 07:00 EST. DEQ produces each edition on Friday morning from data through 07:00 that day. The cutoff is the agency's specification, not an assumption made here (DEQ staff, correspondence, 2026-08-16). DEQ reissues this analysis every week, so a comparison that names no edition is measured against a target that moves.
Two later editions have since shipped, and the column stays on August 7 anyway. That is the window the GENARCH column is computed over, and it is where the record released under FOIA ends. Setting a coefficient refitted on a longer record beside a fit that stops at August 7 would compare two spans rather than two calculations.
The APEX 14 collocation period closed on 2026-04-08, which fixes the two APEX 14 regressions: no later week of data can enter them, and they read the same in all three archived editions. The APEX 5 window is still open, so each edition refits those two on more data than the last.
All four comparisons reproduce DEQ's coefficients to within the tolerance the build enforces, which is 0.05 on slope and intercept and 0.03 on R². DEQ publishes these coefficients to two significant figures, so part of every difference in the table is that rounding rather than a difference in the underlying fit.
The fourth took a round of correspondence to get there. The APEX 5 NO2 figure printed in the August 7 edition did not reproduce here, so the question went to DEQ. DEQ traced it to the plotting call behind the chart: the axis limits there bounded the model fit as well as the plotted view, so points outside them never entered the regression. Refitting without the limits over the August 7 window gives y = 1.8 + 0.32x, R² = 0.21, and DEQ sent the paired hourly measurements the regression runs on (DEQ staff, correspondence, 2026-08-19).
The correction is now in print. The August 21, 2026 edition carries the unbounded fit, at y = 1.8 + 0.31x, R² = 0.2 over a record two weeks longer than the one this table compares on. Those coefficients describe that longer window, so this page cites them here rather than setting them in the column above.
The same fit computed from the source tables gives y = 1.835 + 0.319x, R² = 0.207 on 2,745 paired hours, inside tolerance of the corrected coefficients. That fit keeps the sensor's exact-zero readings, 17.6 percent of the APEX 5 window's NO2 hours in runs as long as 45 hours, because DEQ keeps them (DEQ staff, correspondence, 2026-08-19). Everywhere else on this page they stay excluded as a per-pollutant floor clamp. Dropping them here returns slope 0.340 and R² 0.199 on 2,261 pairs, the figure this page carried before, which left zero handling as the only remaining difference between the two calculations.
Agreement on the coefficients does not make the relationship a strong one. At an R² near 0.21 this is the weakest of the four, and its coefficients are loosely determined. At 10 ppb on the sensor the two lines sit 0.02 ppb apart, on a series whose regulatory mean is 3.5 ppb.
Applying the same null-code and flag exclusions and an 18-of-24 completeness rule, recomputed daily averages match DEQ's published daily file on 118 of 119 comparable days after truncation to one decimal, with a mean absolute difference of 0.0017 µg/m³. DEQ truncates published values rather than rounding them.
The single day that differs is 2026-03-10, where the recomputation gives 5.0 against a published 5.2. DEQ staff reviewed that date, said that recomputing from hourly values also gives 5.0, and noted that they were unsure why the invalid hour at 10:00 was not excluded from the published daily export (DEQ staff, correspondence, 2026-08-16).
DEQ's analysis: Data Center Air Quality Analysis, August 7, 2026. Project page: Virginia DEQ Data Center Air Monitoring.
Record length and the percentile comparison
Table 4 of DEQ's August 7 report states that one sensor is the only one whose 98th percentile of daily PM2.5 averages sits above 35 µg/m³. That sensor, sterling-ms, also has the shortest record in the network. It began collecting on 2026-06-18 and has 51 days, against 152 at ashburn-collocated. Its entire record falls in high summer and includes the smoke-transport weekend, which is 7.8 percent of its record against 2.6 percent of the longest one.
| DEQ figure for sterling-ms | Aug 7 | Aug 14 | Aug 21 | Aug 7 to Aug 21 |
|---|---|---|---|---|
| 98th percentile of daily PM2.5 averages (µg/m³) | 40.4 | 38.2 | 36.0 | -4.4 |
| 98th percentile of hourly PM2.5 (µg/m³) | 69.1 | 62.3 | 56.8 | -12.3 |
| Mean hourly PM2.5 (µg/m³) | 11.3 | 11.1 | 10.8 | -0.5 |
The sentence naming this sensor as the only one whose 98th percentile of daily averages sits above 35 µg/m³ is word for word the same in all three editions. The figure that sentence describes has fallen in each one: 40.4 µg/m³ on August 7, 2026, 38.2 on August 14, 2026, 36.0 on August 21, 2026. DEQ staff said they expected it to keep falling as the record lengthens (DEQ staff, correspondence, 2026-08-16). All three editions are archived under docs/deq-reports/, because DEQ's published page carries only the current one.
DEQ staff note that the wildfire smoke data heavily skews the 98th percentiles at every site, and that before the smoke arrived they sat at or below about 20 µg/m³ everywhere (DEQ staff, correspondence, 2026-08-16). The percentiles in the table below include that window.
Restricting every sensor to the window in which all six were collecting, 2026-06-18 to 2026-08-07, changes the ordering. Five of six sites sit above 35 µg/m³ on matched windows, and sterling-ms ranks fourth rather than first. The apparent difference between sites is a difference in record length.
| Site | Days, own record | p98, own record | Rank, own record | Days, common | p98, common | Rank, common |
|---|---|---|---|---|---|---|
| farmwell-middle | 120 | 27.20 | 117th–118th of 120 | 50 | 45.40 | 49th–50th of 50 |
| belfort-park | 84 | 30.72 | 82nd–83rd of 84 | 50 | 40.19 | 49th–50th of 50 |
| golf-course | 122 | 24.88 | 119th–120th of 122 | 51 | 40.12 | 50th of 51 |
| sterling-ms | 51 | 38.21 | 50th of 51 | 51 | 38.21 | 50th of 51 |
| ashburn-collocated | 152 | 25.85 | 148th–149th of 152 | 51 | 37.10 | 50th of 51 |
| dulles-area | 149 | 20.77 | 146th–147th of 149 | 50 | 29.50 | 49th–50th of 50 |
The rank columns give the observation each percentile is read from. At 51 days the 98th percentile is the 50th of 51; at 152 days it is the 148th–149th of 152. The statistic carries the same name at every record length and sits at a different position in the distribution at each one.
98th percentile, own record against common window
Show the percentile table, including rank position and smoke-window share
| Site | Days, own record | p98, own record | Rank, own record | Days, common | p98, common | Rank, common | Smoke share of record |
|---|---|---|---|---|---|---|---|
| farmwell-middle (Ashburn) | 120 | 27.20 | 117th–118th of 120 | 50 | 45.40 | 49th–50th of 50 | 3.3% |
| belfort-park (Sterling) | 84 | 30.72 | 82nd–83rd of 84 | 50 | 40.19 | 49th–50th of 50 | 4.8% |
| golf-course (Ashburn) | 122 | 24.88 | 119th–120th of 122 | 51 | 40.12 | 50th of 51 | 3.3% |
| sterling-ms (Sterling) | 51 | 38.21 | 50th of 51 | 51 | 38.21 | 50th of 51 | 7.8% |
| ashburn-collocated (Ashburn) | 152 | 25.85 | 148th–149th of 152 | 51 | 37.10 | 50th of 51 | 2.6% |
| dulles-area (Sterling) | 149 | 20.77 | 146th–147th of 149 | 50 | 29.50 | 49th–50th of 50 | 2.7% |
Three qualifications on the numbers above
Neither DEQ's figures nor these are comparable to the federal standard. That standard is a 98th percentile of daily averages across a full year, averaged over three years. A 51-day percentile is not that statistic, and nothing about attainment or non-attainment follows from either set of numbers.
This corrects a comparison between monitoring sites. It is not a statement that any location is polluted, and it is not a statement about anyone's health.
GENARCH's own-record percentiles differ from DEQ's Table 4 by up to roughly 2.4 µg/m³ in both directions, higher at some sites and lower at others. The most likely explanation is the treatment of exact-zero sensor readings, which this pipeline excludes as a fault mode rather than counting as measurements. That explanation is not established, and the difference is disclosed here rather than resolved.
How closely the sites track each other
Pairwise correlation of hourly PM2.5
| Site | ashburn-collocated | belfort-park | dulles-area | farmwell-middle | golf-course | sterling-ms |
|---|---|---|---|---|---|---|
| ashburn-collocated | — | 0.908n=1,994 | 0.886n=3,495 | 0.930n=2,860 | 0.928n=2,862 | 0.940n=1,186 |
| belfort-park | 0.908n=1,994 | — | 0.899n=1,927 | 0.941n=1,981 | 0.962n=1,994 | 0.963n=1,173 |
| dulles-area | 0.886n=3,495 | 0.899n=1,927 | — | 0.908n=2,776 | 0.929n=2,790 | 0.904n=1,139 |
| farmwell-middle | 0.930n=2,860 | 0.941n=1,981 | 0.908n=2,776 | — | 0.949n=2,847 | 0.957n=1,176 |
| golf-course | 0.928n=2,862 | 0.962n=1,994 | 0.929n=2,790 | 0.949n=2,847 | — | 0.966n=1,186 |
| sterling-ms | 0.940n=1,186 | 0.963n=1,173 | 0.904n=1,139 | 0.957n=1,176 | 0.966n=1,186 | — |
Show every pair as a list, with its hour count
| Site A | Site B | r | Overlapping hours |
|---|---|---|---|
| golf-course | sterling-ms | 0.966 | 1,186 |
| belfort-park | sterling-ms | 0.963 | 1,173 |
| belfort-park | golf-course | 0.962 | 1,994 |
| farmwell-middle | sterling-ms | 0.957 | 1,176 |
| farmwell-middle | golf-course | 0.949 | 2,847 |
| belfort-park | farmwell-middle | 0.941 | 1,981 |
| ashburn-collocated | sterling-ms | 0.940 | 1,186 |
| ashburn-collocated | farmwell-middle | 0.930 | 2,860 |
| dulles-area | golf-course | 0.929 | 2,790 |
| ashburn-collocated | golf-course | 0.928 | 2,862 |
| ashburn-collocated | belfort-park | 0.908 | 1,994 |
| dulles-area | farmwell-middle | 0.908 | 2,776 |
| dulles-area | sterling-ms | 0.904 | 1,139 |
| belfort-park | dulles-area | 0.899 | 1,927 |
| ashburn-collocated | dulles-area | 0.886 | 3,495 |
All 15 pairwise correlations fall between 0.886 and 0.966. This is a description of how the series move together and nothing more. High spatial correlation does not establish that local sources contribute nothing: the deployed sensors may sit largely upwind, and a local increment can be masked by a dominant regional signal.
The ratio between the highest and lowest site reading in a given hour is not a usable discriminator here. It fails below roughly 30 µg/m³, where small absolute differences produce large ratios. Across 3,610 hours the median ratio is 1.72, and low-concentration hours reach ratios above 10 from differences under a microgram per cubic metre.
Limitations
Data and methods
Site identifier crosswalk
This table carries identifiers only. It holds no measurement of any kind, and none may be added to it. It exists so that a reader can map every identifier used on this page onto DEQ's published site labels and check the work against DEQ's report.
| GENARCH identifier | Area | DEQ published label | Kunak dashboard label |
|---|---|---|---|
| ashburn-collocated | Ashburn | Broad Run HS | Broad Run HS |
| belfort-park | Sterling | Belfort Park Dr | Belfort Park Dr |
| dulles-area | Sterling | Dulles Airport | Dulles Airport |
| farmwell-middle | Ashburn | Farmwell Station MS | Farmwell Station MS |
| golf-course | Ashburn | 1757 Golf Club | 1757 Golf Club |
| heritage-farm | Sterling | Heritage Farm Museum | Heritage Farm Museum |
| newberry-condo | Sterling | Newberry Condo Assoc | Newberry Condo Assoc |
| sterling-ms | Sterling | Sterling MS | Sterling MS |
| steuart-weller | Ashburn | Steuart Weller ES | Steuart Weller ES |
Source tables
| File | Retrieval | Date | Licence |
|---|---|---|---|
| deq_data_center_air_monitoring_hourly.csv6.8 MB2026-03-03 to 2026-08-10, six sites, 17147 site-hours, 51441 rows | public Kunak Cloud CSV export, method confirmed by DEQ staff 2026-08-10 | 2026-08-10 | Fully redistributable with credit that the data belong to Virginia DEQ (per DEQ staff, 2026-08-10). Preferred attribution line pending from DEQ Communications. |
| deq_regulatory_monitor_hourly.csv1.4 MB2026-03-03 to 2026-08-10, 11592 rows: ASHBURN PM2.5 (method 638) and NO2 (method 212), AURHILL CO (method 54) | Virginia FOIA request 26-4646, released in full 2026-08-11 | 2026-08-11 | Public records released in full under the Virginia Freedom of Information Act, no redactions, no cost. Credit Virginia DEQ. |
| deq_pm25_daily.csv0.1 MB2026-03-03 to 2026-08-10, six sensor sites and the Ashburn regulatory monitor | derived by the pipeline from deq_data_center_air_monitoring_hourly.csv and deq_regulatory_monitor_hourly.csv; published values from AshburnPM2.5_dailyAvg_030326_081026.xls, released under FOIA 26-4646 | 2026-08-11 | Public records released in full under the Virginia Freedom of Information Act, no redactions, no cost. Credit Virginia DEQ. |
Exclusion rule
A reading is excluded if the value is missing, an AQS Null Code is present, or the Flags field contains a less-than character. No letter code alone excludes a reading. Flags are case-sensitive: the same letter in upper and lower case identifies two different events, and folding the case of that column silently merges them. A 24-hour average is computed only from 18 or more valid hours. The full rule set is recorded in docs/GENARCH_RULES.md section 3.
Licence and attribution
Fully redistributable with credit that the data belong to Virginia DEQ (per DEQ staff, 2026-08-10). A preferred attribution line is pending from DEQ Communications and will be added here when it is received.
Sensor coordinates are not published in machine-readable form. A map of the network will be added here once a citable coordinate source is available from DEQ.
Pipeline source and page source: github.com/ksaraiya388/GENARCH. GENARCH methods: /methods.