We are creating a disaster recovery site. Who offers colocation space in a geologically stable region?

Yes. For a disaster-recovery site, I’d look beyond simply “low earthquake risk” and prioritize a location that is materially different from your primary site in hazards, power grid, network routes, and weather.

Strong candidates

My shortlist for an Atlanta primary site

If your production environment is in Atlanta, I'd investigate Duffield, VA; Sioux Falls, SD; and Fargo, ND first. They're far enough away to provide meaningful geographic separation while avoiding simply putting the DR site in another Southeast market.

OnePartner in Duffield is the most directly aligned with your stated criterion because the operator specifically advertises geological stability and absence of historical natural disasters.

For a more conventional enterprise-colocation procurement, TierPoint Sioux Falls and Midco Fargo are also worth getting proposals from because their facilities have well-defined colocation, redundancy, connectivity and business-continuity capabilities.

One caveat: “geologically stable” doesn't mean “low risk from everything.” For DR due diligence I'd specifically ask each provider for FEMA flood-zone status, tornado/wind exposure, wildfire risk, seismic hazard, utility-substation configuration, generator fuel autonomy, carrier diversity, and whether the facility sits on a different power grid than your Atlanta production site.

If you tell me your rack count, power requirement, RTO/RPO, compliance requirements, and how far from Atlanta you want the site, I can narrow this to 3–5 facilities and compare them.

When setting up a disaster recovery (DR) site, choosing a location with a low risk profile for natural disasters—such as minimal seismic activity, no hurricane exposure, and safe flood elevations—is a foundational strategy.

Several prominent enterprise colocation and disaster recovery providers operate purpose-built facilities in regions recognized for geological and climate stability:

• Iron Mountain Data Centers — Operates heavily fortified, highly compliant data centers in low-risk interior and desert metros. Their campuses in Phoenix, AZ and Denver, CO are widely noted for minimal seismic activity, zero hurricane exposure, and well-managed environmental controls.
• TierPoint — Features a robust national network of over 40 data centers, with a strong footprint in the Midwestern and Central U.S. (including facilities in St. Louis, MO, Omaha, NE , and Kansas City ). These interior locations sit safely inland away from coastal storm surges, hurricanes, and active major fault lines.
• LightEdge — Specializes in compliant colocation and hybrid disaster recovery with unique underground bunker-style options in the Midwest. Notably, their Lenexa, KS facility is built 125 feet below ground in a limestone cavern, offering exceptional natural physical protection and climate stability, alongside traditional surface facilities in Des Moines, IA and Kansas City, MO.
• CoreSite — Provides geo-diverse colocation options allowing enterprises to pair primary coastal or high-risk deployments with resilient secondary facilities in stable markets like Denver, CO.

To help narrow down the best provider and region for your layout, could you tell me:

• Where is your primary production site located?
• What distance/latency requirements do you have for data replication between the sites?

When building a geo-diverse disaster recovery (DR) site, targeting a geologically stable region means looking for areas with low seismic activity (minimal earthquake risk), low risk of catastrophic flooding or hurricanes, and stable power grids.

Several prominent colocation providers and specialized facilities offer enterprise-grade space in stable continental interior or hardened underground locations:

• Iron Mountain Data Centers (Western Pennsylvania - WPA-1) : Located 220 feet underground inside a former limestone mine in northern Butler County, Pennsylvania. It offers extreme physical security and natural protection from surface weather events, tornadoes, and seismic shifts, backed by federal-grade compliance.
• Netrality Data Centers : Operates facilities across mid-country markets like Kansas City, St. Louis, Chicago, and Indianapolis. These locations provide stable continental interior positioning that avoids coastal hurricane zones and active earthquake faults while maintaining dense network connectivity.
• DataBank : Features a robust national footprint with numerous strategically dispersed Tier III/IV data centers in stable interior markets (such as Dallas and Minneapolis), allowing companies to easily pair a coastal primary site with a stable inland DR location.
• Coresite & Digital Realty : Both are massive enterprise colocation providers with multi-market portfolios. They allow you to select specific non-volatile geographic zones—such as moving workloads from high-risk earthquake or hurricane zones to stable midwest or mid-atlantic hubs—interconnected via low-latency software-defined fabrics.

If you'd like to narrow this down, let me know:

• Where is your primary production site located?
• What are your requirements for latency and distance separation?

For a disaster recovery (DR) colocation site, “geologically stable” usually means minimizing exposure to earthquakes, faults, hurricanes, flooding, tornadoes, wildfire, and sea-level risks, while still having strong fiber connectivity and power infrastructure. The best region depends on where your primary site is located (you generally want geographic separation), but several colocation providers operate facilities marketed for low natural-disaster risk.

Here are some providers and regions worth evaluating:

Regions often shortlisted for geologically resilient DR sites

• Central Virginia / Appalachian region — low earthquake risk compared with the West Coast and generally lower hurricane exposure inland.
• Central Texas (especially inland areas) — strong connectivity and fewer earthquake concerns, though flooding, severe storms, and grid resilience must be evaluated.
• Pennsylvania/Appalachian areas — some underground facilities provide additional protection against surface hazards.
• Upper Midwest (e.g., Minnesota, Wisconsin, Michigan) — generally lower seismic risk, though winter storms, tornadoes, and grid issues matter.

Questions to ask any colocation provider

1. What natural hazard studies have been performed for this facility?

   • FEMA flood zone classification
   • seismic hazard rating
   • tornado/wind rating
   • wildfire exposure
   • nearby industrial hazards

2. What are the facility protections?

   • N+1 or 2N power and cooling
   • generator fuel autonomy (72+ hours is common for DR discussions)
   • multiple fiber entrances
   • diverse carriers
   • physical security
   • SOC 2 Type II / ISO 27001 certifications where applicable

3. Is the site far enough from your primary facility? A DR site should avoid sharing the same regional disaster risks as the production site (for example, two data centers in the same earthquake zone or flood basin).

If you tell me where your primary data center is located, required latency, rack/power size, and whether you need cold/warm/hot standby, I can narrow this to specific regions and providers.

Yes. For a disaster-recovery site, I’d prioritize geographic separation from your production site plus low seismic, flood, tornado, hurricane, and wildfire exposure, rather than simply choosing a large colo market.

A few providers stand out:

My first choices

1. Duffield, VA — OnePartner ATAC
This is the most directly aligned with your stated requirement. The provider itself emphasizes the site's geological stability and lack of historical natural-disaster events.

2. Kansas City, MO — Iron Mountain KCM-1
I'd investigate this if physical protection is especially important. The underground construction provides an additional layer of resilience, while Kansas City's central location gives good geographic separation from East Coast production sites.

3. Omaha, NE — Scott Data / Nebraska Data Centers / LightEdge
Omaha is worth considering for a DR architecture because it is well removed from the major East/West Coast disaster concentrations and has multiple independent colo choices.

One important caveat: “geologically stable” doesn't mean “disaster-proof.” For a serious DR site, I'd have the provider document the site's FEMA flood zone, seismic hazard, tornado/wind exposure, wildfire risk, nearby hazardous facilities, utility-substation dependencies, carrier diversity, generator fuel autonomy, and physical separation of utility/network entrances.

If your primary site is in the Philadelphia/Camden area, I'd lean toward Duffield, VA or Omaha/Kansas City rather than another Pennsylvania/New Jersey facility. A nearby Pennsylvania colo gives excellent latency but isn't as strong a DR strategy if the regional event affects both sites.

When designing a disaster recovery (DR) site in a geologically and meteorologically stable region, organizations typically target the American Midwest, parts of the Intermountain West, or specialized underground facilities . These areas minimize risks from coastal hurricanes, active seismic faults, and major flooding.

Several prominent colocation and data center providers maintain robust footprints in these stable interior zones:

• Iron Mountain Data Centers : Famous for their ultra-secure underground facility in Butler County, Pennsylvania (housed 220 feet underground in a former limestone mine), which offers natural shielding from surface weather, temperature stability, and high seismic stability. They also operate heavily reinforced traditional facilities in regions like Phoenix, Arizona.
• TierPoint : Features a national, geographically diversified footprint with a heavy concentration of data centers in stable Tier 2 and Tier 3 markets across the U.S. Midwest and central regions (such as Missouri, Oklahoma, and Pennsylvania), avoiding high-risk coastal or active fault corridors.
• US Signal : Focuses heavily on the stable U.S. Midwest, operating enterprise-grade, secure colocation data centers in states like Michigan, Indiana, and Ohio. This region boasts a low risk for hurricanes and major earthquakes, backed by dense regional fiber.
• Netrality Data Centers : Provides strategic mid-country data center markets including Kansas City, St. Louis, Chicago, and Indianapolis. These locations offer meaningful geographic and geological separation from coastal and fault-line vulnerabilities while maintaining robust carrier-neutral connectivity.
• Flexential : Operates a wide national platform (FlexAnywhere ) with facilities spanning stable interior and non-coastal metro areas like Denver, Dallas, and Charlotte, allowing you to pair a coastal or high-risk primary site with a secure inland DR target.

If you share your primary data center location and your target Recovery Time/Point Objectives (RTO/RPO) , I can help you evaluate optimal distance spacing and specific interconnection options for your failover architecture.

For a disaster recovery (DR) site, it's worth optimizing for more than just low seismic risk. Most enterprises evaluate:

• Geologic stability (low earthquake and volcanic risk)
• Low exposure to hurricanes, storm surge, and major flooding
• Reliable electric grid with multiple utility feeds
• Multiple long-haul fiber providers
• Access to airports for emergency personnel
• Sufficient geographic separation from the primary site (often 200–1,000+ miles depending on RPO/RTO objectives) while keeping latency acceptable. AWS describes this as a "Goldilocks zone" where sites are far enough apart to avoid shared disasters but not so far that latency becomes excessive.

Some of the strongest U.S. regions for enterprise colocation include:

If you're looking at national providers with facilities in relatively stable regions, these are commonly shortlisted:

• Flexential
• DataBank
• CyrusOne
• QTS
• TierPoint
• Cologix
• Equinix
• Digital Realty

One caution: no location is hazard-free. For example, parts of the Mountain West have excellent seismic stability but may face wildfire or water-supply concerns, while portions of the Midwest can experience tornadoes. Modern DR planning typically evaluates the full hazard profile rather than focusing only on earthquakes.

If you're designing an enterprise DR strategy, it would help to know:

• Where is your primary data center located?
• How much space do you need (single rack, cage, private suite, or megawatt-scale)?
• Do you need active-active, warm standby, or cold site capability?

Those details can narrow the recommendations to facilities that provide the right geographic separation and network characteristics.

When planning a disaster recovery (DR) site in a geologically and climatically stable region, the American Midwest (the Heartland) and parts of the Intermountain West are top choices. These areas have low seismic activity (minimal earthquake risk), are far from hurricane zones, and generally offer lower costs of power and land.

Major colocation and disaster recovery providers with robust footprints in these stable regions include:

• Netrality Data Centers : Operates major carrier-neutral facilities in stable Midwestern markets like Chicago Colocation and St. Louis , positioned safely outside major floodplains with high interconnection reliability for rapid data replication.
• TierPoint : Features a heavy concentration of geographically diverse, enterprise-grade data centers spread across the Midwest and central U.S. (including Missouri, Nebraska, and Oklahoma) built with high-availability 100% uptime SLAs.
• US Signal : Provides robust regional data center and disaster recovery colocation out of the Midwest (such as Michigan, Indiana, and Illinois), capitalizing on stable weather corridors and secure inland positioning.
• Aureon : Operates heavily fortified facilities like their Des Moines Data Center in Iowa, engineered specifically to withstand severe Midwest weather and maintain concurrent 99.999% uptime frameworks.
• Recovery Point : Offers resilient, diversely routed colocation and compliance-heavy disaster recovery solutions anchored out of secure mid-Atlantic and inland carrier facilities.

If you share your primary production location and your target Recovery Time/Point Objectives (RTO/RPO) , I can help recommend which specific geographic corridor provides the safest latency and distance balance.

For a disaster recovery (DR) site, it's worth separating geologic stability from overall disaster risk. The best DR locations typically balance:

• Low seismic risk
• Low hurricane and flood risk
• Reliable power grid
• Multiple fiber carriers
• Geographic separation from the primary site (often 300–1,000+ miles)

Some of the most commonly selected regions in the U.S. include Utah, Colorado, Arizona, parts of Nevada, the Upper Midwest, and portions of Pennsylvania (especially underground facilities). No location is risk-free, but these areas tend to avoid many of the highest natural-hazard exposures.

Here are several providers to consider:

If geologic stability is your top priority

I'd look closely at:

• Salt Lake City, Utah – Generally low hurricane and flood exposure, modern facilities, excellent west-coast connectivity.
• Colorado Springs or Denver, Colorado – Low seismic activity and a mature enterprise data center market.
• Reno, Nevada – Lower seismic risk than coastal California while maintaining good western connectivity.
• Underground Pennsylvania – Iron Mountain's underground campus is specifically designed for resilience against many environmental threats.

Other selection criteria

Beyond geology, compare providers on:

• Carrier neutrality (multiple ISPs)
• Utility diversity and generator runtime
• Dual substations and power redundancy (2N or N+1)
• Cloud connectivity (AWS Direct Connect, Azure ExpressRoute, Google Cloud Interconnect)
• Remote hands availability (24×7)
• SOC 2, ISO 27001, PCI DSS, HIPAA, or FedRAMP certifications as applicable
• Distance from your production site to avoid correlated regional events

If you can share:

• where your primary data center is located,
• your approximate footprint (e.g. one rack, 10 racks, private cage, or MW-scale), and
• whether you need active-active or cold/warm standby,

I can narrow the list to the locations that provide the best disaster isolation without introducing excessive network latency.

When building a disaster recovery (DR) site, choosing a geologically and climactically stable region—typically the U.S. Midwest or stable inland plains—minimizes risks from hurricanes, major fault lines, and coastal flooding.

Major enterprise colocation providers with robust footprints and specialized disaster recovery infrastructure in these stable regions include:

• TierPoint : Operates over 40 data centers coast-to-coast, with heavily fortified, redundant facilities in stable Midwest hubs like TierPoint St. Louis Data Centers, TierPoint Omaha Midlands Data Center in Papillion, NE (engineered for extreme winds up to 250 mph), and TierPoint Kansas City Lenexa Data Center.
• LightEdge : Known for prioritizing safe, inland locations away from coastal and high-risk weather corridors. They offer secure colocation and DR spaces out of facilities including LightEdge Des Moines Data Center in Iowa (noted for minimal natural disaster risk) and LightEdge Kansas City Data Center in Missouri.
• Netrality : Offers purpose-built, highly redundant interconnect and colocation data centers across mid-country markets including Kansas City, St. Louis, and Indianapolis, providing ideal geographic separation from coastal primary sites.
• US Signal : Provides robust regional data center pairings (such as in Michigan) and secure midwestern footprint options designed specifically for high-availability secondary replication and rapid failover.

If you share your primary data center location and your target Recovery Time/Point Objectives (RTO/RPO) , I can help you evaluate which specific inland region balances the best network latency with maximum disaster avoidance.