{
  "schema_version": 1,
  "source_compilation_context": {
    "mi": {
      "attribution": {
        "inventory": {
          "name": "Compute Atlas",
          "creator": "Edward Kubiak",
          "url": "https://www.compute-atlas.com/api",
          "license": "CC BY 4.0",
          "license_url": "https://creativecommons.org/licenses/by/4.0/",
          "snapshot_url": "https://www.compute-atlas.com/api/facilities",
          "retrieved": "2026-10-14",
          "sha256": "79ad432dab7c128e428234c9d0dd40933114b415a4a5d697db00095637d50f37",
          "changes": "Added provenance, publication-date distinctions, display-safe wording, quarantine flags and state partitioning. Original source records retained locally."
        },
        "counties": "U.S. Census Bureau county boundaries (public domain)",
        "research": "Field-specific source context. See the linked source and limits on each record."
      },
      "source_data_url": "https://datacentersatlas.com/data/mi.json",
      "updated": "2026-10-24"
    }
  },
  "scope": "Exact retained city label subset. This is not a municipal boundary or complete city inventory. Research records retain their sources, dates and location limits. Counts are not a census of operating buildings. Company name links alone do not establish ownership or operation.",
  "collection": {
    "kind": "cities",
    "key": "mi/lansing",
    "label": "Lansing, Michigan"
  },
  "records": [
    {
      "id": "acd-net-metroix-lansing-mi",
      "state": "mi",
      "kind": "facility",
      "name": "ACD.net MetroIX Lansing Data Center (1800 N. Grand River Ave)",
      "group": "unknown",
      "status": "Status unclear",
      "raw_status": "",
      "status_field": "",
      "crypto": false,
      "type": "Data center (inventory classification)",
      "counties": [
        "Ingham"
      ],
      "city": "Lansing",
      "address": "",
      "who": "",
      "end_user": "",
      "mw": null,
      "power": "",
      "power_note": "",
      "investment": "",
      "jobs": "",
      "acres": null,
      "utility": "",
      "water": "",
      "incentives": "",
      "note": "Manual source context is available for this inherited inventory record. The inventory label and approximate geography are retained for discovery. This is not certification of current operation, ownership, a separate physical building, technical capacity or a precise parcel. Missing fields remain unknown. Named-site context, with limited previews/corridor crosswalks explicitly identified.. Current ACD operator colocation page offers a controlled Lansing facility, UPS/generator/cooling, network-provider choices, racks, cages and on-site Remote Hands. Footer identifies 1800 N Grand River Avenue. This supplies limited operator/location context for the inherited MetroIX row; the MetroIX name is not used. No MW, square footage, certification or exact commissioning date is stated. Company office and service context are not an independently surveyed parcel. Not all fields, current operation, precise parcel or critical IT independently certified.",
      "date": "",
      "events": [],
      "timeline": [],
      "opened": "",
      "tier": "",
      "sources": [
        {
          "url": "https://acd.net/colocation",
          "host": "acd.net",
          "date": "",
          "published": "",
          "checked": "2026-10-15",
          "date_kind": "publication date not established",
          "label": "Reviewed source"
        }
      ],
      "loc": {
        "lat": 42.59709,
        "lng": -84.3736,
        "precision": "county",
        "basis": "Shown at county level only. The dot is placed inside the county for the map and is not the site, its address or a parcel."
      },
      "reviewed_evidence": [
        {
          "overlay": "national-permit-scope-operator-crosswalks-and-work-resumption-round82-2026-10-15.json",
          "scope": "Named-site context, with limited previews/corridor crosswalks explicitly identified.",
          "fields": {},
          "notes": [
            "Current ACD operator colocation page offers a controlled Lansing facility, UPS/generator/cooling, network-provider choices, racks, cages and on-site Remote Hands. Footer identifies 1800 N Grand River Avenue. This supplies limited operator/location context for the inherited MetroIX row; the MetroIX name is not used. No MW, square footage, certification or exact commissioning date is stated. Company office and service context are not an independently surveyed parcel.",
            "Not all fields, current operation, precise parcel or critical IT independently certified."
          ],
          "sources": [
            {
              "url": "https://acd.net/colocation",
              "host": "acd.net",
              "date": "",
              "published": "",
              "checked": "2026-10-15",
              "date_kind": "publication date not established",
              "label": "Reviewed source"
            }
          ],
          "whole_record_certified": false
        },
        {
          "overlay": "Codex 3 research cohort 51",
          "scope": "The current provider page offers Lansing colocation, Remote Hands, racks and cages and lists the inherited street in its footer. It does not explicitly name MetroIX or establish that the footer office and offered computing floor are the same exact physical premise. This is limited provider and service context. Exact component identity and current physical stage remain held; an office footer alone does not establish an operating data center.",
          "fields": {
            "current_stage_evidence": {
              "outcome": "provider_service_and_office_not_exact_metroix_component",
              "scope": "The current provider page offers Lansing colocation, Remote Hands, racks and cages and lists the inherited street in its footer. It does not explicitly name MetroIX or establish that the footer office and offered computing floor are the same exact physical premise. This is limited provider and service context. Exact component identity and current physical stage remain held; an office footer alone does not establish an operating data center."
            }
          },
          "notes": [
            "The current provider page offers Lansing colocation, Remote Hands, racks and cages and lists the inherited street in its footer. It does not explicitly name MetroIX or establish that the footer office and offered computing floor are the same exact physical premise. This is limited provider and service context. Exact component identity and current physical stage remain held; an office footer alone does not establish an operating data center.",
            "Existing location, jurisdiction, provider roles, identities, quantities and physical opening dates remain unchanged. Proposal and administrative evidence do not certify computing operation."
          ],
          "sources": [
            {
              "url": "https://acd.net/colocation",
              "host": "acd.net",
              "published": "",
              "date": "",
              "checked": "2026-10-23",
              "label": "Reviewed operator source"
            }
          ],
          "checked": "2026-10-23",
          "whole_record_certified": false
        }
      ],
      "manual_source_reviewed": true,
      "whole_record_certified": false,
      "field_evidence_present": false,
      "inventory_label_retained": true,
      "precision_label": "Exact site not published; shown at county level",
      "summary": "Lansing · Ingham · Source context reviewed",
      "location_display": {
        "policy": "reviewed-map-references-2026-10-23",
        "decision": "withheld_unreviewed_point",
        "scope": "The available point evidence does not establish a supported site location. No site pin, nearby distance or aerial destination is published. The original coordinate and its provenance remain in research history.",
        "county_display": "26065"
      }
    },
    {
      "id": "deep-green-lansing-mi",
      "state": "mi",
      "kind": "facility",
      "name": "Deep Green Lansing Data Center",
      "group": "unknown",
      "status": "Status unclear",
      "raw_status": "",
      "status_field": "",
      "crypto": false,
      "type": "Data center (inventory classification)",
      "counties": [
        "Ingham"
      ],
      "city": "Lansing",
      "address": "",
      "who": "",
      "end_user": "",
      "mw": null,
      "power": "",
      "power_note": "",
      "investment": "",
      "jobs": "",
      "acres": null,
      "utility": "",
      "water": "",
      "incentives": "",
      "note": "Manual source context is available for this inherited inventory record. The inventory label and approximate geography are retained for discovery. This is not certification of current operation, ownership, a separate physical building, technical capacity or a precise parcel. Missing fields remain unknown. Personally read project-specific public context only; no whole-record certification. Regional, directory, legislative and membership sources do not verify an exact building.. Update date is not everyprojectevent. Oakland 26 MWisplannedundefinedbasisandtrusteesauthorizedduediligence,notfinalconstruction. HarborFarmz 4 acresforsaleaspossibleDCisnotanannounced/permittedcampus. GenHhydroconceptisnotgenerationlicense/IT. Lowellpausedmunicipalnegotiations is not MSwithdrawal or siteclosure. Deedrestrictionclaims, moratoriumdates/exceptions andcourtoutcomesneedoriginalrecords. UP 1000 acreportdoesnotnameTelkite/KSawyer,address,operatororfiledapplication,so noexactTelkitecredit. OthercampusMW/taxes/poll 70 percent/oppositionclaimsmustnotbeassignedacrossthis 10-IDgroup. NoOctober 14 futurevoteorNovemberrecalloutcomeassumed. Later originals and observed outcomes take precedence; future dates have no assumed result. Fields can apply to shared campus, regional or historical context; consult source review before assigning to a building.",
      "date": "",
      "events": [
        [
          "2025-11-05",
          "Deep Green published its Lansing proposal announcement on November 5, 2025. The stated future construction window depended on approvals and is not an accomplished start or current service finding."
        ],
        [
          "2026-04-02",
          "Deep Green published a Lansing proposal analysis on April 2, 2026 and described a later Council vote as expected. This dates developer publication and does not establish the vote outcome or present construction, emissions or computing operation."
        ]
      ],
      "timeline": [],
      "opened": "",
      "tier": "",
      "sources": [
        {
          "url": "https://gandernewsroom.com/2026/03/02/how-many-ai-data-centers-are-planned-in-michigan-we-counted/",
          "host": "gandernewsroom.com",
          "date": "2026-10-08",
          "published": "2026-10-08",
          "checked": "2026-10-14",
          "date_kind": "publication",
          "label": "Reviewed source"
        },
        {
          "url": "https://deepgreen.energy/news/deep-green-proposes-120-million-sustainable-data-center-investment-in-downtown-lansing",
          "host": "deepgreen.energy",
          "published": "2025-11-05",
          "date": "2025-11-05",
          "checked": "2026-10-23",
          "label": "Reviewed operator source"
        },
        {
          "url": "https://deepgreen.energy/blog/analysis-deep-green-data-centre-project-confirmed-to-reduce-overall-lansing-emissions",
          "host": "deepgreen.energy",
          "published": "2026-04-02",
          "date": "2026-04-02",
          "checked": "2026-10-23",
          "label": "Reviewed operator source"
        }
      ],
      "loc": {
        "lat": 42.60906,
        "lng": -84.38667,
        "precision": "county",
        "basis": "Shown at county level only. The dot is placed inside the county for the map and is not the site, its address or a parcel."
      },
      "reviewed_evidence": [
        {
          "overlay": "regional-development-review-round34-2026-10-14.json",
          "scope": "Personally read project-specific public context only; no whole-record certification. Regional, directory, legislative and membership sources do not verify an exact building.",
          "fields": {
            "reported_context": "TheGander’s MarchURLdirectory explicitly updatedOctober 8 reports named Michiganproject stages:DeepGreenLansingAprilwithdrawal;Pavilionrezoningwithdrawal;Morleyunfiledconcept;HarborFarmzpropertymarketing;Lowellutilitytalksstalled;OaklandUniversityduediligence;Yorkwithdrawal;Solonpauseextension;Tonduunfiledconcept.",
            "independently_verified_current_operating_status": null,
            "site_stage_scope": "Reported April application withdrawal; not a denied vote"
          },
          "notes": [
            "Update date is not everyprojectevent. Oakland 26 MWisplannedundefinedbasisandtrusteesauthorizedduediligence,notfinalconstruction. HarborFarmz 4 acresforsaleaspossibleDCisnotanannounced/permittedcampus. GenHhydroconceptisnotgenerationlicense/IT. Lowellpausedmunicipalnegotiations is not MSwithdrawal or siteclosure. Deedrestrictionclaims, moratoriumdates/exceptions andcourtoutcomesneedoriginalrecords. UP 1000 acreportdoesnotnameTelkite/KSawyer,address,operatororfiledapplication,so noexactTelkitecredit. OthercampusMW/taxes/poll 70 percent/oppositionclaimsmustnotbeassignedacrossthis 10-IDgroup. NoOctober 14 futurevoteorNovemberrecalloutcomeassumed.",
            "Later originals and observed outcomes take precedence; future dates have no assumed result.",
            "Fields can apply to shared campus, regional or historical context; consult source review before assigning to a building."
          ],
          "sources": [
            {
              "url": "https://gandernewsroom.com/2026/03/02/how-many-ai-data-centers-are-planned-in-michigan-we-counted/",
              "host": "gandernewsroom.com",
              "date": "2026-10-08",
              "published": "2026-10-08",
              "checked": "2026-10-14",
              "date_kind": "publication",
              "label": "Reviewed source"
            }
          ],
          "whole_record_certified": false
        },
        {
          "overlay": "Codex 3 research cohort 51",
          "scope": "The original November 5, 2025 release announced a Lansing proposal with a conditional spring construction forecast. The April 2, 2026 account still describes a proposal and a future April 6 Council vote. Neither original provides that later vote outcome or exact current physical stage. Fuel cell forecasts and comparative emissions claims are not actual operating computing or measured site emissions. The April account body and table identify different March dates for its cited utility analysis; neither becomes an independently verified utility event.",
          "fields": {
            "current_stage_evidence": {
              "outcome": "dated_proposal_and_forecast_current_physical_stage_held",
              "scope": "The original November 5, 2025 release announced a Lansing proposal with a conditional spring construction forecast. The April 2, 2026 account still describes a proposal and a future April 6 Council vote. Neither original provides that later vote outcome or exact current physical stage. Fuel cell forecasts and comparative emissions claims are not actual operating computing or measured site emissions. The April account body and table identify different March dates for its cited utility analysis; neither becomes an independently verified utility event."
            },
            "source_read_scope": {
              "releases_selected_main_bodies_read": true,
              "internal_utility_analysis_dates_conflict_retained": true,
              "future_vote_not_assumed": true
            }
          },
          "notes": [
            "The original November 5, 2025 release announced a Lansing proposal with a conditional spring construction forecast. The April 2, 2026 account still describes a proposal and a future April 6 Council vote. Neither original provides that later vote outcome or exact current physical stage. Fuel cell forecasts and comparative emissions claims are not actual operating computing or measured site emissions. The April account body and table identify different March dates for its cited utility analysis; neither becomes an independently verified utility event.",
            "Existing location, jurisdiction, provider roles, identities, quantities and physical opening dates remain unchanged. Proposal and administrative evidence do not certify computing operation."
          ],
          "sources": [
            {
              "url": "https://deepgreen.energy/news/deep-green-proposes-120-million-sustainable-data-center-investment-in-downtown-lansing",
              "host": "deepgreen.energy",
              "published": "2025-11-05",
              "date": "2025-11-05",
              "checked": "2026-10-23",
              "label": "Reviewed operator source"
            },
            {
              "url": "https://deepgreen.energy/blog/analysis-deep-green-data-centre-project-confirmed-to-reduce-overall-lansing-emissions",
              "host": "deepgreen.energy",
              "published": "2026-04-02",
              "date": "2026-04-02",
              "checked": "2026-10-23",
              "label": "Reviewed operator source"
            }
          ],
          "checked": "2026-10-23",
          "whole_record_certified": false
        }
      ],
      "manual_source_reviewed": true,
      "whole_record_certified": false,
      "field_evidence_present": true,
      "inventory_label_retained": true,
      "precision_label": "Exact site not published; shown at county level",
      "summary": "Lansing · Ingham · Source context reviewed",
      "event_evidence": [
        {
          "date": "2025-11-05",
          "text": "Deep Green published its Lansing proposal announcement on November 5, 2025. The stated future construction window depended on approvals and is not an accomplished start or current service finding.",
          "kind": "announced",
          "sources": [
            {
              "url": "https://deepgreen.energy/news/deep-green-proposes-120-million-sustainable-data-center-investment-in-downtown-lansing",
              "host": "deepgreen.energy",
              "published": "2025-11-05",
              "date": "2025-11-05",
              "checked": "2026-10-23",
              "label": "Reviewed operator source"
            }
          ]
        },
        {
          "date": "2026-04-02",
          "text": "Deep Green published a Lansing proposal analysis on April 2, 2026 and described a later Council vote as expected. This dates developer publication and does not establish the vote outcome or present construction, emissions or computing operation.",
          "kind": "announced",
          "sources": [
            {
              "url": "https://deepgreen.energy/blog/analysis-deep-green-data-centre-project-confirmed-to-reduce-overall-lansing-emissions",
              "host": "deepgreen.energy",
              "published": "2026-04-02",
              "date": "2026-04-02",
              "checked": "2026-10-23",
              "label": "Reviewed operator source"
            }
          ]
        }
      ],
      "location_display": {
        "policy": "reviewed-map-references-2026-10-23",
        "decision": "withheld_unreviewed_point",
        "scope": "The available point evidence does not establish a supported site location. No site pin, nearby distance or aerial destination is published. The original coordinate and its provenance remain in research history.",
        "county_display": "26065"
      }
    },
    {
      "id": "liquid-web-dc3-lansing-mi",
      "state": "mi",
      "kind": "facility",
      "name": "Liquid Web Lansing DC3 (2703 Ena Drive)",
      "group": "operating",
      "status": "Reported service",
      "raw_status": "operating",
      "status_field": "current_status",
      "crypto": false,
      "type": "Data center (inventory classification)",
      "counties": [
        "Eaton"
      ],
      "city": "Lansing",
      "address": "",
      "who": "",
      "end_user": "",
      "mw": null,
      "power": "",
      "power_note": "",
      "investment": "",
      "jobs": "",
      "acres": null,
      "utility": "",
      "water": "",
      "incentives": "",
      "note": "Manual source context is available for this inherited inventory record. The inventory label and approximate geography are retained for discovery. This is not certification of current operation, ownership, a separate physical building, technical capacity or a precise parcel. Missing fields remain unknown. Liquid Web Lansing two-site scope and apparent power. 13.5MVAutilitynotcriticalITor13.5MWactivepower;scopeacrossfacilitiesunspecified. A/BtoDC3aliasnotproven.1997founding/regionyearnotexactopeningofeachDC. Servercapacitynotcurrentoccupancy. No exactstreetorindependentcertificate;oldSafeHarborclaimnotcurrentlegalcomplianceproof. Fields can apply to shared campus, regional or historical context; consult source review before assigning to a building.",
      "date": "",
      "events": [
        [
          "2026-09-25",
          "Liquid Web original RSS published the Lansing DC3 completed maintenance update September 25, 2026. The feed contains separate scheduled, in progress and completed states. This records the dated company service update, not a data center opening, energization, exact physical work time or completion of all planned capacity expansion."
        ]
      ],
      "timeline": [],
      "opened": "",
      "tier": "",
      "sources": [
        {
          "url": "https://www.liquidweb.com/data-centers/lansing-web-hosting/",
          "host": "liquidweb.com",
          "date": "",
          "published": "",
          "checked": "2026-10-14",
          "date_kind": "publication date not established",
          "label": "Reviewed source"
        },
        {
          "url": "https://status.liquidweb.com/history.rss",
          "host": "status.liquidweb.com",
          "published": "",
          "date": "",
          "checked": "2026-10-23",
          "label": "Reviewed operator source"
        }
      ],
      "loc": {
        "lat": 42.60784,
        "lng": -84.85108,
        "precision": "county",
        "basis": "Shown at county level only. The dot is placed inside the county for the map and is not the site, its address or a parcel."
      },
      "reviewed_evidence": [
        {
          "overlay": "operator-primary-review-round10-2026-10-14.json",
          "scope": "Liquid Web Lansing two-site scope and apparent power",
          "fields": {
            "operator": "Liquid Web",
            "regional_facilities": 2,
            "locality": "Lansing, Michigan",
            "operator_described_ownership": "wholly owned",
            "named_facilities": [
              {
                "label": "A",
                "area_sqft": 32000,
                "server_capacity": 8000
              },
              {
                "label": "B",
                "area_sqft": 90000,
                "server_capacity": 25000
              }
            ],
            "published_expandable_utility_feeds_kva": 13500,
            "company_region_established_year": 1997
          },
          "notes": [
            "13.5MVAutilitynotcriticalITor13.5MWactivepower;scopeacrossfacilitiesunspecified. A/BtoDC3aliasnotproven.1997founding/regionyearnotexactopeningofeachDC. Servercapacitynotcurrentoccupancy. No exactstreetorindependentcertificate;oldSafeHarborclaimnotcurrentlegalcomplianceproof.",
            "Fields can apply to shared campus, regional or historical context; consult source review before assigning to a building."
          ],
          "sources": [
            {
              "url": "https://www.liquidweb.com/data-centers/lansing-web-hosting/",
              "host": "liquidweb.com",
              "date": "",
              "published": "",
              "checked": "2026-10-14",
              "date_kind": "publication date not established",
              "label": "Reviewed source"
            }
          ],
          "whole_record_certified": false
        },
        {
          "overlay": "Codex 3 research cohort 24",
          "scope": "Liquid Web current company page says it operates two Lansing data centers. Its original status RSS explicitly identifies Lansing DC3 and records customer affecting circuit maintenance completed in a September 25, 2026 update, with another completed DC3 network update in August. Operator reported service is based on that named customer service account, not an inference from the generic city listing alone. Scheduled window clocks differ from update clocks and are not used as exact physical work times. Neither maintenance nor the current check supplies a data center opening day, verified address, new capacity or completed expansion.",
          "fields": {
            "current_stage_evidence": {
              "outcome": "current_lansing_service_plus_named_dc3_completed_customer_maintenance",
              "scope": "Liquid Web current company page says it operates two Lansing data centers. Its original status RSS explicitly identifies Lansing DC3 and records customer affecting circuit maintenance completed in a September 25, 2026 update, with another completed DC3 network update in August. Operator reported service is based on that named customer service account, not an inference from the generic city listing alone. Scheduled window clocks differ from update clocks and are not used as exact physical work times. Neither maintenance nor the current check supplies a data center opening day, verified address, new capacity or completed expansion."
            },
            "source_read_scope": {
              "original_rss_xml_parsed_locally": true,
              "retained_excerpt_receipt": "cohort-24-liquidweb-rss-excerpts.json",
              "specific_incident_pointer": "https://status.liquidweb.com/incidents/b21phz2p0yrq",
              "rss_item_publication_on": "2026-09-25",
              "scheduled_and_update_clocks_not_reconciled_as_physical_times": true,
              "separate_august_dc3_completed_update_read": true,
              "current_service_not_exact_opening_or_capacity": true
            }
          },
          "notes": [
            "Liquid Web current company page says it operates two Lansing data centers. Its original status RSS explicitly identifies Lansing DC3 and records customer affecting circuit maintenance completed in a September 25, 2026 update, with another completed DC3 network update in August. Operator reported service is based on that named customer service account, not an inference from the generic city listing alone. Scheduled window clocks differ from update clocks and are not used as exact physical work times. Neither maintenance nor the current check supplies a data center opening day, verified address, new capacity or completed expansion.",
            "The review preserves existing physical identity, locations, roles, quantities and opening fields. Source issue dates, review checks and physical milestones remain distinct."
          ],
          "sources": [
            {
              "url": "https://www.liquidweb.com/data-centers/lansing-web-hosting/",
              "host": "www.liquidweb.com",
              "published": "",
              "date": "",
              "checked": "2026-10-23",
              "label": "Reviewed operator source"
            },
            {
              "url": "https://status.liquidweb.com/history.rss",
              "host": "status.liquidweb.com",
              "published": "",
              "date": "",
              "checked": "2026-10-23",
              "label": "Reviewed operator source"
            }
          ],
          "checked": "2026-10-23",
          "whole_record_certified": false
        }
      ],
      "manual_source_reviewed": true,
      "whole_record_certified": false,
      "field_evidence_present": true,
      "inventory_label_retained": true,
      "precision_label": "Exact site not published; shown at county level",
      "summary": "Lansing · Eaton · Source context reviewed",
      "status_scope": "Liquid Web current company page says it operates two Lansing data centers. Its original status RSS explicitly identifies Lansing DC3 and records customer affecting circuit maintenance completed in a September 25, 2026 update, with another completed DC3 network update in August. Operator reported service is based on that named customer service account, not an inference from the generic city listing alone. Scheduled window clocks differ from update clocks and are not used as exact physical work times. Neither maintenance nor the current check supplies a data center opening day, verified address, new capacity or completed expansion.",
      "event_evidence": [
        {
          "date": "2026-09-25",
          "text": "Liquid Web original RSS published the Lansing DC3 completed maintenance update September 25, 2026. The feed contains separate scheduled, in progress and completed states. This records the dated company service update, not a data center opening, energization, exact physical work time or completion of all planned capacity expansion.",
          "kind": "announced",
          "sources": [
            {
              "url": "https://status.liquidweb.com/history.rss",
              "host": "status.liquidweb.com",
              "published": "",
              "date": "",
              "checked": "2026-10-23",
              "label": "Reviewed operator source"
            }
          ]
        }
      ],
      "location_display": {
        "policy": "reviewed-map-references-2026-10-23",
        "decision": "withheld_unreviewed_point",
        "scope": "The available point evidence does not establish a supported site location. No site pin, nearby distance or aerial destination is published. The original coordinate and its provenance remain in research history.",
        "county_display": "26045"
      }
    }
  ],
  "compilation_license": "withheld_pending_owner_decision"
}