Data Center Record.

Reported Built from one source

Markley Group Lowell Data Center

Residents sued and a judge halted the expansion of the Markley Group data center in a dense Lowell neighborhood, citing air quality and community impact concerns. It is reported, as reported April 30, 2026.

How much power it needs, how much water it would use and who would use it have not been disclosed.

Last verified · 27 sources, 0 primary · A skeleton record: built from one source, not yet reviewed in depth by a person. · How to read this page

How to read this page. Every fact links to the source it rests on; a number in brackets is its place in the source list. A figure no source gives reads Not disclosed, and nothing is estimated. Where sources give different figures, each is shown with who gave it, and another source's figure never stands in for the record's own. Entries are added and never overwritten; corrections are listed under What happened.

What is known

Each figure as its source gave it. The number in brackets is its place in the source list.

Land
Not disclosed
Power it would draw
Not disclosed
Water
Not disclosed
Who leads it
Markley Group
as stated by the source
Who would use it
Not disclosed
Jobs once it runs
Not disclosed
Tax each year
Not disclosed
Every field, with who said it and when (Researcher view)

Impact figures

FieldValueWho says soSourceLast verified
How much power it needs Not disclosed
How much water it would use Not disclosed
How loud it would be Not disclosed
Jobs once it runs Not disclosed
Tax it would pay each year Not disclosed

The record's fields

FieldValueWho says soSourceLast verified
Who is building it Markley Group as stated by the source September 17, 2026
Who is constructing it Not disclosed
How much land Not disclosed
Where its power comes from Not disclosed
Grid connection Not disclosed
How it is cooled Not disclosed

The developer's figure is what the company said; what a permit allows is the ceiling a permit sets; measured means observed. Water is in gallons a day or a year, whichever the source stated; a tax claim given as a range shows both ends, each linked to the source that gave it.

Still not public, and where it would show up

The record adds each the day a source gives it. Why these documents.

  • Water useA state water right filing or a water supply agreement.
  • Who would use itA lease announcement or a tenant named in a filing.
  • Power the campus would drawA utility or public service commission docket, an interconnection filing, or an air permit for an on site plant.
  • Jobs and taxAn incentive agreement, a county's economic development filing or a fiscal note.

What happened

  1. (source date; the content gives no date of its own)

    The air permit was originally approved by Mass DEP [1]

  2. (source date; the content gives no date of its own)

    The company has four generators already installed at the facility [1]

  3. (source date; the content gives no date of its own)

    Markley Group owns the property and has invested more than $600 million in the project [1]

  4. (source date; the content gives no date of its own)

    A judge temporarily blocked installation of four new diesel generators [1]

  5. Moratorium (source date; the content gives no date of its own)

    Residents requested a judge to pause a data center expansion in Lowell [10]

  6. · In court (source date; the content gives no date of its own)

    A clinic filed a lawsuit to challenge a data center expansion in Lowell [12]

The full Markley Group Lowell Data Center timeline, in order

40 corrections to this record

Every correction, with its reason

  1. · the summary of a record items row

    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word The old and new text.

  2. · the kind of source of a history entry

    The source was labeled with the Google News search that found it; it now carries its outlet's tier (the record's rules of 2026-09-23). The link did not change. The day's label corrections.

  3. · the kind of source of a history entry

    The source was labeled with the Google News search that found it; it now carries its outlet's tier (the record's rules of 2026-09-23). The link did not change. The day's label corrections.

  4. · the kind of source of a history entry

    The source was labeled with the Google News search that found it; it now carries its outlet's tier (the record's rules of 2026-09-23). The link did not change. The day's label corrections.

  5. · the kind of source of a history entry

    The source was labeled with the Google News search that found it; it now carries its outlet's tier (the record's rules of 2026-09-23). The link did not change. The day's label corrections.

  6. · the kind of source of a history entry

    The source was labeled with the Google News search that found it; it now carries its outlet's tier (the record's rules of 2026-09-23). The link did not change. The day's label corrections.

  7. · the kind of source of a history entry

    The source was labeled with the Google News search that found it; it now carries its outlet's tier (the record's rules of 2026-09-23). The link did not change. The day's label corrections.

  8. · the kind of source of a history entry

    The source was labeled with the Google News search that found it; it now carries its outlet's tier (the record's rules of 2026-09-23). The link did not change. The day's label corrections.

  9. · the kind of source of a history entry

    The source was labeled with the Google News search that found it; it now carries its outlet's tier (the record's rules of 2026-09-23). The link did not change. The day's label corrections.

  10. · the kind of source of a history entry

    The source was labeled with the Google News search that found it; it now carries its outlet's tier (the record's rules of 2026-09-23). The link did not change. The day's label corrections.

  11. · the kind of source of a history entry

    The source was labeled with the Google News search that found it; it now carries its outlet's tier (the record's rules of 2026-09-23). The link did not change. The day's label corrections.

  12. · the kind of source of a history entry

    The source was labeled with the Google News search that found it; it now carries its outlet's tier (the record's rules of 2026-09-23). The link did not change. The day's label corrections.

  13. · the kind of source of a history entry

    The source was labeled with the Google News search that found it; it now carries its outlet's tier (the record's rules of 2026-09-23). The link did not change. The day's label corrections.

  14. · the kind of source of a history entry

    The source was labeled with the Google News search that found it; it now carries its outlet's tier (the record's rules of 2026-09-23). The link did not change. The day's label corrections.

  15. · the kind of source of a history entry

    The source was labeled with the Google News search that found it; it now carries its outlet's tier (the record's rules of 2026-09-23). The link did not change. The day's label corrections.

  16. · the kind of source of a history entry

    The source was labeled with the Google News search that found it; it now carries its outlet's tier (the record's rules of 2026-09-23). The link did not change. The day's label corrections.

  17. · the kind of source of a history entry

    The source was labeled with the Google News search that found it; it now carries its outlet's tier (the record's rules of 2026-09-23). The link did not change. The day's label corrections.

  18. · the kind of source of a history entry

    The source was labeled with the Google News search that found it; it now carries its outlet's tier (the record's rules of 2026-09-23). The link did not change. The day's label corrections.

  19. · the kind of source of a history entry

    The source was labeled with the Google News search that found it; it now carries its outlet's tier (the record's rules of 2026-09-23). The link did not change. The day's label corrections.

  20. · the kind of source of a history entry

    The source was labeled with the Google News search that found it; it now carries its outlet's tier (the record's rules of 2026-09-23). The link did not change. The day's label corrections.

  21. · the kind of source of a history entry

    The source was labeled with the Google News search that found it; it now carries its outlet's tier (the record's rules of 2026-09-23). The link did not change. The day's label corrections.

  22. · the kind of source of a history entry

    The source was labeled with the Google News search that found it; it now carries its outlet's tier (the record's rules of 2026-09-23). The link did not change. The day's label corrections.

  23. · the kind of source of a history entry

    The source was labeled with the Google News search that found it; it now carries its outlet's tier (the record's rules of 2026-09-23). The link did not change. The day's label corrections.

  24. · the kind of source of a history entry

    The source was labeled with the Google News search that found it; it now carries its outlet's tier (the record's rules of 2026-09-23). The link did not change. The day's label corrections.

  25. · the kind of source of a history entry

    The source was labeled with the Google News search that found it; it now carries its outlet's tier (the record's rules of 2026-09-23). The link did not change. The day's label corrections.

  26. · the kind of source of a history entry

    The source was labeled with the Google News search that found it; it now carries its outlet's tier (the record's rules of 2026-09-23). The link did not change. The day's label corrections.

  27. · the kind of source of a history entry

    Tier after resolution (2026-09-21). The source on file is cbsnews.com, the publisher's own page. The item reached the record through Google News: "data center" Massachusetts, which the record carries at tier 1, and the approve copied the feed's tier onto this row. The tier now comes from the outlet, which the record already carries at tier 4 on 3 rows of sources. DECISIONS section 7. The speaker, the claim, the date and the url are unchanged. The day's label corrections.

  28. · the kind of source of a history entry

    Tier after resolution (2026-09-21). The source on file is bostonherald.com, the publisher's own page. The item reached the record through Google News: "data center" Massachusetts, which the record carries at tier 1, and the approve copied the feed's tier onto this row. The tier now comes from the outlet, which the record already carries at tier 4 on 1 row of monitoring_sources. DECISIONS section 7. The speaker, the claim, the date and the url are unchanged. The day's label corrections.

  29. · the kind of source of a history entry

    Tier after resolution (2026-09-21). The source on file is bostonherald.com, the publisher's own page. The item reached the record through Google News: "data center" Massachusetts, which the record carries at tier 1, and the approve copied the feed's tier onto this row. The tier now comes from the outlet, which the record already carries at tier 4 on 1 row of monitoring_sources. DECISIONS section 7. The speaker, the claim, the date and the url are unchanged. The day's label corrections.

  30. · the kind of source of a history entry

    Tier after resolution (2026-09-21). The source on file is cbsnews.com, the publisher's own page. The item reached the record through Google News: "data center" Massachusetts, which the record carries at tier 1, and the approve copied the feed's tier onto this row. The tier now comes from the outlet, which the record already carries at tier 4 on 3 rows of sources. DECISIONS section 7. The speaker, the claim, the date and the url are unchanged. The day's label corrections.

  31. · the draft of a status history row

    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval. The old and new text.

  32. · the draft of a status history row

    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval. The old and new text.

  33. · the draft of a status history row

    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval. The old and new text.

  34. · the draft of a status history row

    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval. The old and new text.

  35. · the draft of a status history row

    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval. The old and new text.

  36. · the draft of a status history row

    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval. The old and new text.

  37. · the draft of a status history row

    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval. The old and new text.

  38. · the draft of a status history row

    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval. The old and new text.

  39. · the draft of a status history row

    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval. The old and new text.

  40. · the draft of a status history row

    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval. The old and new text.

Every correction on the record is on the corrections page.

What was said

A judge found that Lowell residents may have been denied a meaningful opportunity to challenge the project during the state permitting process
Judge (unnamed) · August 11, 2026 · paraphrased · NBC Boston local outlet

Every statement about data centers in Massachusetts, by speaker

The site

Where in Middlesex County is not in the public record. The pin marks the county seat, not a building, and the outline is the county.

  • This record: Proposed, ringed
  • data center
  • Dashed edge: the exact site is not in the public record
  • Smaller pins: 7 other published records in Massachusetts
Details
  • this record's location, ringed
  • parcel outline, from the county parcel record
  • city limits, U.S. Census Bureau, on a town level record
  • county boundary

The other pins are the published projects in the same state, each in its stage color. The imagery beneath is the USGS national orthoimagery, public domain, shown so the land around the site can be read.

Where
Lowell, Middlesex County, Massachusetts
How exactly it is located
County level, the county seat
The parcel
No parcel outline in the public record
Nearest homes
Not computed for a record placed at a place center
Nearest records
Nearest records are not computed for a record placed at a county seat.

Keep going

The county Middlesex County 2 projects on the record. The state Data centers in Massachusetts Every Massachusetts project, the rules on the record and what comes next.

Questions about this project

4 questions answered from the record

Answered from the rows on this page.

Who is building Markley Group Lowell Data Center?

Markley Group is the developer. No construction contractor is named on the record yet.

How much power and water does Markley Group Lowell Data Center say it needs?

Power: not disclosed by any source on file. Water: not disclosed by any source on file.

Where does Markley Group Lowell Data Center stand today?

It is reported, as reported April 30, 2026. The newest entry, reported August 11, 2026: The air permit was originally approved by Mass DEP [1].

What has Lowell or Middlesex County decided about it?

No decision by Lowell or Middlesex County about data centers is on the record. The Middlesex County page and the Massachusetts scorecard list every rated row the day a person publishes one.

Sources

Primary documents first: filings, minutes, dockets and official pages. Then reporting. The numbers are the ones the entries above cite.

Reporting

  1. Judge blocks installation of additional diesel generators at Lowell data center - NBC Boston, NBC Boston, August 11, 2026, local outlet
  2. Lowell Residents Win Stay Against Data Center - Yale Law School, Yale Law School, August 12, 2026, local outlet
  3. Judge halts data center expansion in Mass. city - masslive.com, masslive.com, August 11, 2026, local outlet
  4. Judge halts expansion of Lowell, Massachusetts data center - CBS News, CBS News, August 11, 2026, local outlet
  5. Judge halts expansion of massive data center in Lowell, Massachusetts neighborhood - CBS News, CBS News, August 11, 2026, local outlet
  6. Court orders Markley Group to pause expansion of data center in Lowell - WCVB, WCVB, August 10, 2026, local outlet
  7. Big tech, residents clash over data centers - Lowell Sun, Lowell Sun, August 8, 2026, local outlet
  8. Massachusetts residents ask judge to halt data center expansion in their backyards - Yahoo, Yahoo, August 2, 2026, local outlet
  9. Lowell residents sue over data center expansion in neighborhood - WCVB, WCVB, July 29, 2026, local outlet
  10. Residents want a judge to pause Lowell data center expansion - WBUR, WBUR, July 29, 2026, local outlet
  11. Lowell residents sue data center, state over air quality permit - CommonWealth Beacon, CommonWealth Beacon, May 1, 2026, local outlet
  12. Clinic Lawsuit Challenges Data Center Expansion in Lowell, Massachusetts - Yale Law School, Yale Law School, April 30, 2026, local outlet
15 more sources
  1. Lessons From Lowell: How a Data Center’s Expansion Has Choked a Small Town - The Harvard Crimson, The Harvard Crimson, May 4, 2026, local outlet
  2. Clinic Advocates Against Data Center Expansion in Massachusetts City - Yale Law School, Yale Law School, March 16, 2026, local outlet
  3. Massachusetts residents sue data center over 27 diesel generators in dense neighborhood - Yahoo, Yahoo, August 13, 2026, local outlet
  4. Owner of data centers in Boston, Lowell pushes back against opposition - Boston Herald, Boston Herald, September 13, 2026, local outlet
  5. Data Center Air Quality Plan Appeal in Lowell, Massachusetts - law.yale.edu, law.yale.edu, January 27, 2026, local outlet
  6. Lowell residents file Massachusetts’ first lawsuit against a data center - Boston.com, Boston.com, May 7, 2026, local outlet
  7. In one Mass. city, the fight over a data center has hit a crisis point - WGBH, WGBH, July 29, 2026, local outlet
  8. Neighbors are fighting the expansion of an AI data center in Lowell - NBC Boston, NBC Boston, July 16, 2026, local outlet
  9. 14-year-old girl removed by police from public Lowell data center meeting - masslive.com, masslive.com, July 1, 2026, local outlet
  10. Lowell Police remove 14-year-old from data center public forum - Lowell Sun, Lowell Sun, June 30, 2026, local outlet
  11. Take a rare look inside the largest data center in Massachusetts. Neighbors call it "the dungeon." - CBS News, CBS News, June 22, 2026, local outlet
  12. A rare look inside the largest data center in Massachusetts - CBS News, CBS News, June 17, 2026, local outlet
  13. Court orders pause Lowell data center expansion - New England News Collaborative, New England News Collaborative, August 12, 2026, local outlet
  14. Judge halts expansion of massive data center in Lowell, Massachusetts neighborhood - CBS News, CBS News, August 11, 2026, local outlet
  15. Court orders Markley Group to pause expansion of data center in Lowell - WCVB, WCVB, August 10, 2026, local outlet

27 sources on file.

Cite this record

Data Center Record, "Markley Group Lowell Data Center", https://datacenterrecord.org/projects/markley-group-lowell-data-center-ma, last verified September 17, 2026.

Last verified , first recorded . Every correction is logged on the corrections page and under What happened.

Download this record (CSV) JSON Report a correction Send a tip about Markley Group Lowell Data Center
Cite this page

Data Center Record, "Markley Group Lowell Data Center", https://datacenterrecord.org/projects/markley-group-lowell-data-center-ma. Data: Data Center Record, datacenterrecord.org, CC BY 4.0.

The structured rows are CC BY 4.0. Link to this page; that is what turns a reuse into a citation. Prose stays under copyright.

Report a change
For researchers
Slug
markley-group-lowell-data-center-ma
Status value
rumored
Stage
Proposed
Tier
skeleton
Tags
skeleton
Place id
us/ma/middlesex-county/lowell
Coordinates
42.375, -71.10611
Location precision
county
Location source
County seat (Cambridge), Wikidata, placed at county level
Coordinate source
wikidata county seat
Location source number
Not disclosed
Location last verified
September 16, 2026
EPA registry id
Not disclosed
Use type values
not_disclosed
Tenancy value
not_disclosed
Cooling type value
not_disclosed
Capacity basis
not_disclosed
Water basis
not_disclosed, gallons_per_day
Acreage basis
Not disclosed
Interconnection value
not_disclosed
Capacity, if disclosed
Not disclosed
Rating of the county's rows
Not disclosed
Published
2026-09-05
Last verified
2026-09-17