Ark Data Centres (arkdatacentres)
- Domain:
www.ark-d-c.com· Kind: operator · Priority: 2 · Enabled: yes - License / attribution: Publicly accessible operator pages; factual data only; © Ark Data Centres — attribution “Ark Data Centres”
- Coverage: GB, BE
What it collects
Facility records (kind: facility) via parser(s) arkdc_facility_v1 in apps/worker/src/connectors/operators2/emea.ts.
Fields published by the pages and captured: name, city (town named on page), countryIso2, lat/lng (parcel, map JSON), tier, pue, siteAreaHa, status. Animated MW counters are ignored (render as 0).
Every field carries an extraction method in methods (e.g. json-ld:PostalAddress, regex:it_mw_v1, attr:data-value+MW, lookup:city-country) for provenance. Coordinates are only taken from JSON-LD / embedded JSON / map links published by the operator — never geocoded. Status defaults to operational unless the page uses pipeline wording (under construction / coming soon / planned).
Discovery
- Sitemaps:
https://www.ark-d-c.com/sitemap.xml - Include:
/locations/[a-z0-9-]+$,/insights/. - Exclude:
\?,# - Classify:
/locations/[a-z0-9-]+$→ facility_pages (facility_page);/insights/.→ newsroom (press_release)
Newsroom URLs (when configured) rely on the GenericConnector news fallback (press_release → news_event when data-center relevant).
Schedule & fetch
- Schedule: facility_pages weekly, newsroom daily, sitemap weekly
- Fetch: L1→L2, 15 rpm, concurrency 2, robots.txt respected, max 20 premium credits/run. All pages are served at L1 (plain HTTP);
maxLevelis capped at 2 so false-positive “blocked” heuristics (HubSpot / cookie-consent strings) never spend Scrapfly credits.
Quirks
Campus pages /locations/ (arkdatacentres.co.uk redirects here). MW counters are JS-animated (render as 0) and are NOT extracted; map JSON latitude/longitude, Tier, PUE and acreage are.
Verification (live, 2026-09-11)
try-connector --limit N: discovered 29 URLs (facility_pages=8, newsroom=21); sampled pages → 4 entities, 4 valid, 0 rejected, 0 premium credits.