Colocation & Data Center Scraper
Pricing
from $3.00 / 1,000 results
Colocation & Data Center Scraper
Scrape colocation and data center facilities from datacenters.com. Browse by country, state, city, or provider, or fetch specific facilities by URL. Get address, coordinates, certifications, power/space specs, provider contact info, and media.
Pricing
from $3.00 / 1,000 results
Rating
0.0
(0)
Developer
Crawler Bros
Maintained by CommunityActor stats
0
Bookmarked
0
Total users
0
Monthly active users
19 days ago
Last modified
Categories
Share
Scrape colocation and data center facility listings from datacenters.com — a global directory of 11,000+ data centers across 45+ countries. Browse facilities by country, state/region, city, or provider, or pull full details for specific facilities by URL. No login, API key, or cookies required.
What this actor does
- Five browse modes: by country, by state/region, by city, by provider/operator, or by direct facility URL
- Rich facility details: address, GPS coordinates, provider contact info, certifications, power capacity, colocation space, nearby airport distance, features, images, videos, and brochures
- Provider company profile: founding year, employee-count range, and headquarters address for the facility's operator
- Global coverage: 45+ countries including the United States, Germany, United Kingdom, China, India, Japan, Australia, Brazil, and more
- Filter by facility type, certification, or minimum power capacity
- Empty fields are always omitted — every record only contains data that was actually found
Output per facility
facilityName,facilityId,facilitySlugproviderName,providerSlug,providerLogoUrl,providerPhoneproviderYearFounded,providerEmployeeRange,providerHeadquartersAddress— provider-company profile info (fetched once per provider, not per facility)fullAddress,streetAddress,city,state,country,zip,continentlatitude,longitudesummary,descriptiontotalBuildingSqft,colocationSqft— facility sizepowerDensityKwPerRack,totalPowerMw— power capacitynearestAirportMilescertifications[]/certificationAbbreviations[]— e.g. SOC 2 Type 2, ISO 27001, PCI DSS, HIPAAfacilityTypes[]— e.g. Colocation, IaaS, Internet Exchangefeatures[]— named facility highlights with descriptionsimageUrls[],videoUrls[],brochures[]sourceUrl— canonical facility pagerecordType,scrapedAt
Grid-summary-only records (when fetchFullDetails is disabled) include facilityName, providerName, fullAddress, imageUrl, and sourceUrl.
Input
| Field | Type | Default | Description |
|---|---|---|---|
mode | string | byCountry | byCountry / byState / byCity / byProvider / byFacilityUrl |
country | select | united-states | Country to browse (mode=byCountry/byState/byCity) |
state | string | – | State/region name, e.g. Texas (mode=byState/byCity) |
city | string | – | City name, e.g. Dallas (mode=byCity) |
provider | select | equinix | Well-known provider (mode=byProvider) |
providerOther | string | – | Any provider name not in the dropdown; overrides provider |
facilityUrls | array | – | Direct facility URLs or slugs (mode=byFacilityUrl) |
maxItems | integer | 30 | Hard cap on emitted records (1–500) |
fetchFullDetails | boolean | true | Visit each facility's page for full specs; disable for a faster summary-only run |
facilityType | select | – | Filter by service type (requires fetchFullDetails=true) |
certification | select | – | Filter by certification (requires fetchFullDetails=true) |
minTotalPowerMw | number | – | Minimum total power capacity in MW (requires fetchFullDetails=true) |
Example: all data centers in a US state
{"mode": "byState","country": "united-states","state": "Texas","maxItems": 50}
Example: facilities in a specific city, filtered by certification
{"mode": "byCity","country": "united-states","state": "Virginia","city": "Ashburn","certification": "SOC 2 Type 2","maxItems": 40}
Example: all locations for a provider
{"mode": "byProvider","provider": "digital-realty","maxItems": 100}
Example: specific facilities by URL
{"mode": "byFacilityUrl","facilityUrls": ["https://www.datacenters.com/equinix-da1-dallas","amazon-aws-iad23-ashburn"]}
Use cases
- Site selection — compare colocation facilities across markets by power capacity, certifications, and space
- Market research — map data center density by country, state, or provider
- Sales & lead generation — build prospect lists of facility operators in a target region
- Compliance sourcing — filter facilities by certification (SOC 2, ISO 27001, PCI DSS, HIPAA)
- Competitive intelligence — track a provider's footprint across markets
- Real estate & infrastructure analysis — geolocate facilities for logistics planning
FAQ
Do I need a login, API key, or proxy? No. The actor works out of the box on the free Apify plan.
What countries are covered? 45+ countries are available as a dropdown, including the US, Canada, UK, Germany, France, China, India, Japan, Australia, Brazil, and more. State/city browsing works globally as long as datacenters.com lists facilities there.
Why do some facilities have fewer fields than others? Not every operator discloses power capacity, colocation space, or certifications publicly. The actor only includes fields that datacenters.com actually reports — it never fabricates placeholder values.
What's the difference between facilityType values? Colocation (rentable rack/cage space), IaaS (infrastructure-as-a-service), Internet Exchange, Cloud, Bare Metal, Network, and Wholesale reflect the services a facility offers, as published by the operator.
Can I look up a facility I already have a URL for? Yes — use mode: byFacilityUrl with a list of datacenters.com facility URLs or slugs.
How fast is a run? Summary-only runs (fetchFullDetails: false) are fastest. Full-detail runs visit each facility's page individually for the richer field set, so larger maxItems values take proportionally longer.
Why is a run with facilityType/certification/minTotalPowerMw slow when it finds few or no matches? datacenters.com doesn't expose these as server-side search filters, so the actor must open every candidate facility's detail page to evaluate them. Combining a restrictive filter with a broad scope (a large city, state, or country) can mean visiting hundreds of facility pages before concluding there are no matches. Narrow the scope (a specific city/provider) or allow a generous run timeout when using these filters over a large area.
Does city browsing handle non-English spellings (e.g. München, Köln)? Yes. If the direct city-page guess comes back empty, the actor automatically checks the state's real city list and matches by accent-insensitive name before giving up.
Does state/region browsing handle local naming conventions (e.g. Swedish counties like Skåne)? Yes. If a state/region name doesn't produce a direct match (some countries use administrative suffixes in their URLs that don't match how the name is commonly typed), the actor automatically checks the country's real state list and matches by accent-insensitive, suffix-tolerant name before giving up. This applies to both byState and byCity modes.
How fresh is the data? Facility pages are scraped live on every run, reflecting whatever datacenters.com currently publishes.