> ## Documentation Index
> Fetch the complete documentation index at: https://infrl.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Cite the source documentation and the original facility record when describing datacenters.
> Unknown or missing specifications are not evidence that a capability is absent. Do not infer capacity, hardware, ownership, or operational status.
> A dataset import date is not a facility verification date. Distinguish public research from verified infrastructure capabilities.
> Do not describe account access or planned capabilities as available unless the current documentation confirms activation.

# Read facility details

> Understand facility records, reported specifications, and information that remains unknown.

Select a dot in the [Atlas](https://infrl.com/datacenters/) to open its record. The compact overlay shows the facility name, operator and location when recorded, and a status when one is known.

Expand **More information** to see the company and location fields, coordinates, available facility website, and specification groups.

## Company and location

The record distinguishes the operator from the owner when both are available. An address or company field marked **Not yet verified** has no recorded value in the displayed snapshot.

Coordinates have one of two meanings:

| Location type | Meaning |
| - | - |
| Community-mapped point | A point contributed to OpenStreetMap; its accuracy may vary. |
| Approximate center | The center of a mapped site, such as a building or campus. It may not identify an entrance or a specific building. |

Status can be operational, planned, under construction, closed, or unknown. A mapped datacenter does not by itself establish that the facility is operating.

## Specifications

The expanded record organizes information into these groups:

| Group | Examples of fields |
| - | - |
| Space & capacity | Building area, data-hall area, racks, rack density |
| Power & redundancy | IT and utility capacity, backup power, redundancy |
| Cooling | Cooling type, liquid cooling, redundancy |
| Network & connectivity | Carriers, internet exchanges, interconnection |
| Certifications | Reported certifications and certified tier |
| Energy & sustainability | PUE, renewable energy, water usage |
| AI hardware | GPUs, accelerators, hardware configuration |

Reported values retain their source wording and units. Use the **Source for…** link below a specification to inspect the underlying record. Missing fields display **Not yet verified**; this means unknown, not zero or unavailable.

<Note>
  All facility information is community reported and is not independently verified. A populated field is not a verification badge. A record may describe a whole campus, a building, or a room, so its capacity may not apply to the dot's apparent footprint.
</Note>

Do not infer a certification from a reported tier, GPU availability from power or cooling, or rack capacity from floor area. Confirm current capabilities and their scope with the facility's own sources before using them for a deployment decision.

## Follow the sources

**View OpenStreetMap record** opens the source for the facility. **Facility website**, when present, opens the website recorded for that facility. These links let you compare the snapshot with the source's current information.

The **Imported** date records when the Atlas snapshot was generated. It does not establish when each fact was published or verified. See [data and sources](/atlas/data-and-sources) for provenance and reuse terms.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.