# Netrality Data Centers (`netrality`)

Domain: netrality.com · Kind: operator · Priority: 2 · Enabled: yes
License / attribution: Publicly accessible operator pages; factual data only; © Netrality Data Centers — attribution “Netrality Data Centers”
Coverage: US

# What it collects

Facility records (kind: facility) via parser(s) netrality_facility_v1 in apps/worker/src/connectors/operators2/americas.ts.

Fields published by the pages and captured: name, address, city, regionName, countryIso2, buildingSqm, facilityType carrier_hotel, certifications.

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://netrality.com/data-center-sitemap.xml, https://netrality.com/post-sitemap.xml
Include: /data-center/[a-z0-9-]+/$, /news/, /press-releases?/
Exclude: \?, #
Classify: /data-center/[a-z0-9-]+/$ → facility_pages (facility_page); /(news|press-releases?)/. → 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); maxLevel is capped at 2 so false-positive “blocked” heuristics (HubSpot / cookie-consent strings) never spend Scrapfly credits.

# Quirks

Facility pages /data-center// ; the H1 encodes 'City, State Data Center ' and the page publishes square footage and carrier-hotel positioning.

# Verification (live, 2026-09-11)

try-connector --limit N: discovered 15 URLs (facility_pages=15); sampled pages → 4 entities, 4 valid, 0 rejected, 0 premium credits.