Templus: Templus Madrid 02

Templus Madrid 02 is a facility name referenced by Templus on its official website as part of its network of “Templus centers,” where the site navigation/content lists both “Templus Madrid 01” and “Templus Madrid 02.” The operator’s website does not publish a dedicated, publicly accessible facility page for “Madrid 02” with site-specific specifications in the sources captured for this investigation.

No third-party interconnection directory record (e.g., PeeringDB facility page) was identified and confirmed for a facility explicitly named “Templus Madrid 02” during this investigation; therefore, third-party directory fields such as networks present, carriers, and IX/local exchanges are Not publicly disclosed for this facility in this output.

Templus’ recent expansion activity includes acquisitions in Madrid reported by third-party business media (e.g., a deal involving Grupo Aire data centers including one in Madrid), but those reports do not publish a facility mapping that explicitly identifies which acquired asset corresponds to “Templus Madrid 02.”

⚙️ Facility Highlights

1. Official website (operator): Templus operates and markets data center services under the official domain templus.com. (operator-stated, organization-level)
2. Facility name presence (operator website): Templus’ website content/navigation references “Templus Madrid 02” as one of its listed centers. (operator-stated, organization-level)
3. Operator facility page (Madrid 02-specific): Not publicly disclosed (no dedicated “Templus Madrid 02” facility page with specifications was captured in the sources reviewed). (operator-stated, facility-level)
4. Facility address (Madrid 02-specific): Not publicly disclosed.
5. Power capacity (MW) (Madrid 02-specific): Not publicly disclosed.
6. Tier / resiliency classification (Madrid 02-specific): Not publicly disclosed.
7. Acquisition context (third-party news): Forbes Spain reports Templus acquired three Grupo Aire data centers (Madrid, Valencia, Lisbon) and states the transaction adds 6.5MW to installed capacity (deal-level context; Madrid 02 mapping is Not publicly disclosed). (third-party news)
8. Additional portfolio acquisition context (third-party source): AtlasEdge states it agreed to sell nine data centres to Templus, including one in Madrid (portfolio context; Madrid 02 mapping is Not publicly disclosed). (third-party source)

🔐 Security & Compliance

1. Facility-specific security systems (CCTV, mantraps, biometrics, guard force, access policies): Not publicly disclosed for Templus Madrid 02.
2. Compliance certifications (facility-specific ISO/SOC/PCI, certificate IDs, audit scope): Not publicly disclosed for Templus Madrid 02.
3. ENS certification (operator-stated, organization-level): Templus publishes an ENS conformity certificate (referencing systems supporting physical access management and DC inventory/management services); facility-specific applicability to “Madrid 02” is Not publicly disclosed. (operator-stated, organization-level)

🌐 Connectivity & Carrier Access

1. Networks present (third-party directory): Not publicly disclosed (no confirmed PeeringDB facility record for “Templus Madrid 02” identified in this investigation).
2. Carriers on-net (third-party directory): Not publicly disclosed (no confirmed PeeringDB facility record for “Templus Madrid 02” identified in this investigation).
3. Meet-me room / cross-connect products / pricing (facility-specific): Not publicly disclosed.
4. Internet Exchange (IX): Not publicly disclosed (no confirmed directory record captured listing Local Exchanges for “Templus Madrid 02”).
5. Operator-level connectivity positioning: Templus markets “network neutral and hyperconnected” data centers and colocation/connectivity services at the organization level; Madrid 02-specific carrier roster and products are Not publicly disclosed. (operator-stated, organization-level)

💼 Who It Serves

1. Organizations seeking Madrid-region capacity from Templus, where the operator lists Templus Madrid 02 as part of its network (customer roster Not publicly disclosed). (operator-stated, organization-level)
2. Customers looking for colocation and related infrastructure services that Templus markets across its platform (Madrid 02-specific service catalog Not publicly disclosed). (operator-stated, organization-level)
3. Stakeholders tracking Madrid capacity added through acquisitions reported in public media (Madrid facility identity and mapping to “Madrid 02” Not publicly disclosed). (third-party news)